Please if you are changing anything inside the cloop, remaster overclockix while booted in the same version of overclockix. Cloop is highly version dependent and kernel version-dependent. You must build it with the same modules that will be used to boot it later on the CD.
As for setting default cheatcodes and making it use a customized configuartion, in /boot/isolinux/isolinux.cfg
Default linux26
APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi vga=791 initrd=minirt26.gz nomce quiet BOOT_IMAGE=knoppix26
home=scan and any other cheatcodes go here
home=scan activates the persistent home feature at boot. You can use this code from the CD as it is when you boot, but editing isolinux.cfg will make it automatic with the default boot options. Generally set this already, but I see browsing v3.79 that it's not there. I think that's because I chose to edit some other things which may have left persistent home broken or partially broken.
Persistent Home- You activate this feature when booted into the live environment. What it does is create an ext3 image of the /home/knoppix directory (which is where
[email protected] lives) onto a permanent writeable medium of your choice such as a hard drive partition or USB key. You will choose the size of this image when you create it. It will need to be on a fs type linux can read and write, so you can't put it on NTFS, but FAT32 is perfectly fine.
It's not merely a snapshot of /home/knoppix either. It is contstantly rsynced as the contents of /home/knoppix (which is a ramdisk) change. By using the cheatcode you're telling Overclockix to ignore the version of /home/knoppix which is on CD and scan all hard drives and usb drives for a previously saved version. The folding scripts are smart enough to realize when a persistent home is being used and will not overwrite the client.cfg or flags file with their defaults.
At least that is ideally how it works. As I said in 3.79 I made a compromise involving how the /home/knoppix default configurations are generated which might have broken persistent home. And the folding services in all currently available versions of Overclockix are radically different from each other.
Summary-
3.7 uses wine and runs 2 clients by deault, no LTSP. As far as I know this will work with persistent home no problem.
LTSP uses wine, creates one or 2 clients, LTSP capable. Should work with persistent home no problem.
3.79 uses wine, LTSP capable, might overwrite client.cfg if persistent home used, persistent home itself might be broken. It does come with an alternate folding service which is persistent home freindly, but would take remastering to switch it out with the default folding service.
In v3.79 it is line 1187 of /etc/init.d/knoppix-autoconfig which overwrites a lot of /home/knoppix with default configurations, whether or not persistent home is being used. Additionally some editing of /etc/X11/Xsession.d/45xsession may also contribute to persistent home not behaving as it was meant to.
These were design compromises because it can be very difficult to remaster Knoppix have have it actually use changes made to the KDE menu, kicker quicklaunch, and other customized desktop settings, because these things exist in multiple places and are called mulitple times by the 45xsession script while the system is booting and creating /home/knoppix.