Xandros and lilo.conf

How to properly edit Xandros lilo.conf to avoid being overwritten during hardware detection:

Per Jammy in http://forums.xandros.com/viewtopic.php?t=2723

• You should not edit the lilo.conf file as it may get regenerated next time there is a hardware detection change.
• The /etc/devices/devices.inf file is the one you want to edit.
• The sections that match [image.*] are essentially each of the entries that end up in the /etc/lilo.conf.
• If you look at these [image.*] entries, you will notice a priority value. This priority value is what determins the sort order in the lilo.conf file.
• The default value for Xandros is = -100, and the default value for Windows is 0, which is why Xandros is first.
• After modifying the priority value, save the new devices.inf and then run the command:
• detect probe
• This will generate a new lilo.conf.

So, the trick is to poke around in the /etc/devices/devices.inf file, not /etc/lilo.conf

If you are using 3.02 OC or 3.0 Deluxe, then you must edit /etc/devices/cmdappend.inf. This unfortunely will add this line to all 3 boot options at startup.

How to stop Xandros from rebuilding lilo.conf

Running the following command will disable this step during the hardware detection and configuration rebuild phase during the system boot.

chmod -x /sbin/fooze

Note that this means that Xandros 'restore' feature will likely not be able to do so if you create a broken config.

It also means that if you have a custom lilo.conf that fooze simply cannot leave alone, turn it off.

How to load another partition/distribution's lilo.conf into Xandros

/sbin/etcdevset -S -c image.MEPISdevhda2 -t kernel_image -v /disks/mepis/boot/vmlinuz-2.4.22

It reads the other linux's lilo.conf to get the info. Unfortunately in MEPIS case, they seems to be placing their kernel_image value in double quotes. So you will have to manually transfer the configuration to your Xandros lilo.conf.

Back to XandrosKwikis