Each distribution has a live version to make sure, try and learn how it works and if it's the distro that suits us.
But once you find our distribution, once we have customized with programs that interest us and get rid of the unnecessary programs that we think would be a great thing to be able to re-transform it into a "distro" live.
Obviously the internet is already someone who has thought and has created a series of scripts to transform our installation to a live distro, the site we're talking about is www.linux-live.org
Linux Live is a set of shell scripts that allows you to create your own live distribution, based on what has already been installed on your PC. The live type will be bootable from CD-rom from any USB system.
The following statements taken directly from the site.
How to build a Live distro:
1) Install your favorite distro to disk partition, or into a folder on your existing system.
Slackware is recommended but not required.
2) Build aufs kernel module and squashfs kernel module (optionally patched to support LZMA)
The step above is not required if you use precompiled Linux Kernel from this website
Install kernel modules to the newly installed distro to / lib / modules / `uname-r` / fs /.
Make sure you are running the same kernel you used to compile modules
3) Remove all unnecessary files (for example man pages and all other files you do not need),
Live to make your Linux system as small as possible (this step is optional).
4) Download Linux Live scripts from this website and unpack it in / tmp
Read. / DOC / requirements.txt to find out what linux-live scripts need
Edit the. Config files if you need to modify some variables
5) Finally login as root and run. / Build
Live distribution's 'directory tree' will be created in / tmp/live_data_1234
where 1234 is a random number
6) To make ISO image, run make_iso.sh
To make a bootable (usb) disk, run bootinst.sh
Working example:
If you're just looking for a working Linux Live system, visit www.slax.org
Interesting features of Linux Live scripts
1) Persistent changes
Use 'changes = ...' boot parameter to specify persistent changes directory or file. If a directory is used, eg. changes = / some_dir / and the / some_dir / is found on some partition on your disk, then all the changes made to the root filesystem will be saved to that directory. This works even if / some_dir / is on NTFS or VFAT, thanks to posixovl overlay (an userspace filesystem, already included). Important note: if you plan to save changes on VFAT, make sure to modify your distribution's shutdown scripts. It must not execute killall, posixovl is killed and everything else is wrong. Instead, call the cleanup script from / mnt / live / cleanup. If a file is specified for the boot parameter changes, eg. changes = / path / file.dat, and the file has a valid filesystem inside, then the files will be loop-mounted and changes written to it. You may also use changes = / dev/sda1/path / and changes = / dev/sda1/path/file.dat ... to specify where to look for particular device. Other devices will be skipped (will not be even mounted).
2) adding modules on the fly
In the. / Tools / directory of Linux Live, you will find 'activate' and 'deactivate' scripts. You may use these two to add and remove additional LZM modules to the root filesystem on the fly, while your live OS is running.
3) installable system to disk
As mentioned in the previous section, there exists a script called bootinst.sh (and bootinst.bat) to setup a live linux boot sector to boot from disk. If you combine that with persistent changes, will behave like your live distro installed, all changes are stored transparently to the boot media (even to USB), and you can still use 'activate' and 'deactivate' commands to manipulate the root filesystem.
What do you think? Some of you have already tried to use it?
Posted under Technology
This post was written by admin on October 28, 2008







Well ... .. I think it would be better to try to have it alone really understand what you're doing.
You could start from scratch for a miniLive of which are also cache package, expand the compressed filesystem (cloop or squash) chroot into the directory that houses the fs unpacked and hit the apt-get (.. if Debian derivative. .) customize everything to your liking. I leave for example the man pages and remove the locales that do not interest me, move out of the package cache file system to compress, etc.. ETC.
In this way we could also fill our kernel, update qlcuni important packages from source, fill out a form, etc.. ETC.
Basically I prefer to become part of my script ... at least I understand them!
Max
You are absolutely right! But let's view of a person who knows little, that is not geek, who has a need and do not want to spend time to learn and understand what he's doing. If we view "technology convenient", these scripts are a godsend
> But let's get the perspective of a person who knows little, that is not geek, who has> a need and does not want to spend time to learn and understand what he's doing. If we> put the perspective of "technology convenient", these scripts are a godsend
if one is not 'a geek, takes his knoppix and stands silent.
learn = fatigue, we want to understand or not?
@ Roberto
I do not understand this hatred towards those who need something and, thanks to the Internet, is already done and working.
Would be like saying that to drive the car I need to know all about thermodynamics and the Carnot cycle ...
I need a script ... If one wants to use it then, can learn in detail what do these scripts, but maybe not
Some time ago I wrote a guide http://knoppix.crealabs.it/viewtopic.146.html then the forum closed and has aged there.
The "DIY" which presents the short run would certainly be an increased effort but once you understand the mechanism can become any customization.
Today I made up my live with the 2.6.27.1 kernel 2.6.27.4 because he had problems with some USB devices.
Here http://www.nabble.com/Cloop-and-2.6.27-kernel-to20000679.html there is the possibility of collaborating with the creator of the "mother" of all live!
Greetings and have fun
Max
@ Stirner
Thanks for the info!
If you wish, send me your guide that the "place", so he can be helpful to many people!