Hi all,
I cc'ed also the kde-devel and the debian-qt-kde because I am not sure if this is a bug
related to the debian/ubuntu distribution ( which leave the variable ROOT set ) or the kdm
system ( which doesn't clean the environment before to call lilo ) . So I thought that it is
useful to inform all the communities.
On my system ( Ubuntu breezy 5.10 ) I use lilo as boot manager and I set the option
BootManager to Lilo in the /etc/kde3/kdm/kdmrc file.
Before the start of kdm, the ROOT environment variable is set yet to /dev/root.
When kdm calls lilo to get the list of the available
kernel to re-boot, they also passes this environment variable. But lilo
interpreters that as a directory ( even tough it is a device ) when they
should do a chroot !!!. The results is that lilo returns an incorrect information.
A possible solution is to unset this variable at /etc/init.d/kdm level as the patch below:
--- kdebase-3.5.0/debian/kdm.init.old 2006-01-08 23:10:48.000000000 +0100
+++ kdebase-3.5.0/debian/kdm.init 2006-01-10 20:08:22.000000000 +0100
@@ -54,6 +54,8 @@
[ "$(cat $DEFAULT_DISPLAY_MANAGER_FILE)" != "$DAEMON" ]; then
echo "Not starting K Display Manager (kdm); it is not the default display manager."
else
+ # remove the ROOT environment variable, in order to avoid problem with lilo
+ unset ROOT
echo -n "Starting K Display Manager: kdm"
start-stop-daemon --start --quiet $SSD_ARGS -- $ARG || echo -n " already running"
echo "."
I don't know if it is the case to unset other variables that can confuse lilo as: RAMDISK,
READ-ONLY, READ-WRITE...
I am not in the mailing list, so if you reply, please CC: me.
Grazie
Goffredo
--
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack_AT_inwind.it>
Key fingerprint = CE3C 7E01 6782 30A3 5B87 87C0 BB86 505C 6B2A CFF9
Attachment:
pgpqt4dVHVJGp.pgp
Description: PGP signature