Live distribution's 'directory tree' will be created in /tmp/live_data_1234 where 1234 is a random number
Additional software for SLAX is provided in the form of compressed modules. The usage is very simple, just add your downloaded module to /modules/ directory on the CD to include it in SLAX permanently, or use "uselivemod" command in SLAX to activate the module on the fly, when the system is running.
Linux Live scripts version 6 are the most innovative scripts available. AuFS provides better stability compared to old unionfs, squashfs with LZMA support provides great compression ratio and amazing decompression speed. What's new compared to old Linux Live scripts v 5?
aufs is used instead of unionfs, brings great stability and features
squashfs is patched with LZMA compression, so compressed filesystems are 30% smaller
no need to patch your distro's startup scripts in order to remove remount of root rw
no need for udev as the devices are created during live startup
CD tree is simplified, you may call your distro whatever you like
better handling of booting from USB device
added a script to create bootable disk (including USB) in Linux and Windows
If you're just looking for a working Linux Live system, visit http://www.slax.org
Install your favourite distro to disk partition, or into a folder on your existing system. Slackware is recommended but not required.
Build aufs kernel module and squashfs kernel module (optionally patched to support LZMA) Make sure you are running the same kernel you used to compile modules
Remove all unnecessary files (for example man pages and all other files you don't need), to make your Live Linux system as small as possible (this step is optional).
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 .config file if you need to modify some variables
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
To make ISO image, run make_iso.sh To make a bootable (usb) disk, run bootinst.sh
Tomas - do you happen to have a complete list of which files in the slackware packages you have modified for slax? For example, I know you've made changes to some of the rc scripts, such as rc.M .
That is the whole build script for Slax. Modified files are in ./system/* directories.
documented on: 2008-03-18, Tomas M
> Where can i find the build script that thomas uses to build slax 6 ?
have a look at http://www.slax.org/forum/viewtopic.php?t=17271
documented on: 2007-06-03, Quax
how do I actually build Slax from the source? When I compiled and upgraded the kernel on Slax 5 I did it all from within Slax itself, recompiling the kernel, making the new souces module and initrd and then rebooting. Reading the readme files that are associated with the src-core directory Tomas has it seems completely different! d'oh!
btw: You are not the only one who waits for Tomas' build scripts Whistle
I've hacked some on my own but as they need heavy manual intervention to get them run it would be senseless to post them.
Perhaps psykx has finished his scripts
documented on: 2007-05-02, Quax
I didn't know you are WAITING for the build scripts. Try this! Smile
It's something between rc2 and rc3
documented on: 2007-05-02, Tomas
Here are a few tips on how to remove packages from modules rather easily and quickly. It might be the method you use, but it seems to me, by what you writ,e that you just remove files you find an not the entire package(s).
Here's how I do it (Wolvix 1.1.0):
Extract the module to a temporary directory:
lzm2dir name_of_module.lzm tempdirectory/
Inside the 'tempdirectory/' look for the var/log/packages/ folder. Inside it is a list of all packages which have been installed to the module. Since the packages have been installed to the modules we can uninstall them with the 'removepkg' command, just like you would on Slackware, but there's a little trick to it. You have to use the 'ROOT=' parameter. Here's an example:
ROOT=tempdirectory/ removepkg name_of_package
The 'ROOT=' parameter tells the system to remove the package from the target directory and not from the system it self.
You can also remove several packages at once:
ROOT=tempdirectory/ removepkg audacious streamtuner mplayer
Once one or more packages have been removed from the module, look in tempdirectory/var/log/removed_packages and tempdirectory/var/log/removeed_scripts. In those dirs you'll see the list of removed packages and scripts. You don't need those files anymore, so you can just delete them if you want. They are just log files.
2007-06-06, wolven