i've been configuring a new suse kernel in order to install the oss (open sound system) sound drivers so i can get 16-bit digitial audio functioning properly... i currently only have 8-bit sound capability... >-< i don't believe the kernel configuration has been a problem... but i think i'm doing something wrong with lilo..?? windows and redhat linux are on /dev/sdba; suse linux is on /dev/sdb... i am trying to get a new suse kernel installed on /dev/sdb... my lilo.conf is on the redhat partition on /dev/sda... i have therefore been trying to do the lilo reconfiguration from redhat with root on /dev/sda, even though the new kernel i want to install is on /dev/sdb... after placing the new kernel in /vmlinuz on the suse partition, i am getting following output from 'uname' after boot: **************************************** <4>Linux version 2.0.32 (root@rjfleck) (gcc version 2.7.2.3) #7 Fri\ Sep 25 00:05:34 PDT 1998 **************************************** now i recompiled the new kernel on november 18, and if the correct /vmlinuz is what's running it should show the date it was compiled, n'est-ce pas...? i was also suspicious because /var/log/boot.messages was exactly the same after installation in spite of the fact that i modified the kernel configuration...??? and previously configured sound drivers are still installing even though i disabled them in the new kernel configuration... *#&*(! i suspect that, in spite of the fact i am modifying /etc/lilo.conf and running /sbin/lilo on it from the redhat partition, the mbr is still finding and running the old kernel... my suspicion was further reinforced by the fact that the first line of suse boot.messages gives a curious message which looks lilo-related: **************************************** Cannot find map file. **************************************** i noticed that my redhat root directory has a /map file dated the date i reconfigured lilo... but there is no /map in my suse root directory with the vmlinuz i am trying to boot...! how does lilo get a map file to more than one root system when there is more than one linux o/s in the boot configuration...? my lilo.conf follows below... i am now pouring over the lilo documentation to try and get an idea of what i'm doing wrong... but i thought it might help to put the question out there... best, ********************************************************************** rj fleck 715 ashbury street san francisco, ca 94117-4013 phone: (415) 661-9067 fax: (415) 661-9271 internet: rjfleck@ccrma.stanford.edu ********************************************************************** boot=/dev/sda map=/map install=/boot/boot.b prompt timeout=100 image=/vmlinuz label=redhat root=/dev/sda5 read-only image=/vmlinuz-old label=redhat-old root=/dev/sda5 read-only image=/boot/vmlinuz-2.0.32 label=linux-original root=/dev/sda5 initrd=/boot/initrd-2.0.32.img read-only other=/dev/sda1 label=dos table=/dev/sda image=/vmlinuz label=suse root=/dev/sdb2 read-only image=/vmlinuz-old label=suse-sound root=/dev/sdb2 read-only #image=/vmlinuz.98.09 # label=suse-original # root=/dev/sdb2 # read-only - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e