Salix Forums

Hello.
I installed Salix. And some more softwarepacks like LXDE, KDE, Gnome.

And again - the bootloader. I can't configure lilo or grub2. Lilo is been shown as installed, but i can't find it anywhere in the programpanels. And grub can be configured with the coniguration tool sg2config, but it won't ask for installed os. and often it stops while configuring. "an important step wasn't successful.
Here's the logfile text:

Received unexpected output from the DIALOG command. Received `/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:49: Invalid symbolic color 'bg_color'
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:49: error: invalid identifier `bg_color', expected valid identifier
MBR' instead of `MBR', `Root' or `Advanced'
Probably Xdialog is outputting some unexpected error messages.
Check that, please.

PS
The Grub settings are ok, the PC boots normally.
But i want to have influence in the configuration, the tool works 100% automatically.
How can i configure the bootloader? Lilo AND grub2, i want to learn more about the system-settings.

Thanx to all for helping:-)

newsal wrote: Received unexpected output from the DIALOG command. Received `/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:49: Invalid symbolic color 'bg_color'
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:49: error: invalid identifier `bg_color', expected valid identifier
MBR' instead of `MBR', `Root' or `Advanced'
Probably Xdialog is outputting some unexpected error messages.
Check that, please.

As you can see here on your installation Xdialog is not just outputting MBR, but some other stuff too: `/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:49: Invalid symbolic color 'bg_color'
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:49: error: invalid identifier `bg_color', expected valid identifier
MBR'
This causes the tool to fail. Either fix your gtkrc or use the console (dialog) version of sg2conf, which won't have such problems. Just call sg2conf as root from a terminal.

You can influence the configuration, which is generated for grub2 by editing /etc/default/grub or possibly even the files in /etc/grub.d, run update-grub afterwards which updates the /boot/grub/grub.cfg file accordingly. Nevertheless, for the latter I would recommend to just use the *_custom files for adding custom stuff to your /boot/grub/grub.cfg.
/boot/grub/grub.cfg is the configuration file directly used by the bootloader during boot time and usually generated by update-grub through the settings in /etc/default/grub and /etc/grub.d. The grub.cfg file is the most direct way to change grub's configuration. Be aware that this file is overwritten (/backed up) when running sg2conf or update-grub.

If it's just the default boot entry you want to change, you can use grub-set-default as root for that purpose.

If you use LiloSetup, you can edit the configuration file manually by clicking on the appropriate button.
If you want to learn more about LILO 'manual' configuration consult the man pages for LILO and also for lilo.conf
Also make sure you read the commented instructions in the lilosetup.conf regarding the partitions' paths.