* Jan-Christoph Westermann <jwester@sgi1.chemie.uni-hamburg.de> [020207 16:21]:
I am intending to compile a new kernel for SuSE 7.3, but want too keep the old one as a fall back option. Obviously /etc/lilo.conf or /etc/elilo.conf don't exist. Instead I found /boot/elilo.conf This File is similar to lilo.conf on 386 like systems, but when I add an entry for the new kernel, do I need to run lilo? /sbin/lilo or /sbin/elilo do not exist. Is this done by the efi-shell automatically?
EFI or rather elilo parses that file directly and reads the kernel from the filesystem using firmware hooks. That is why elilo, it's config and the kernel have to reside on a DOS formatted partition. As long as the kernel name is correct in elilo.conf, you don't have to worry about this rewriting-bootloader relict from times where firmware was not really doing it's job ;) Best regards, Stefan Reinauer -- Ok hex 4666 dup negate do i 4000 dup 2* negate do " *" 0 dup 2dup 1e 0 do 2swap * e >>a 2* 3 pick + -rot - j + dup dup * e >>a rot dup dup * e >>a rot swap 2dup + 10000 > if 3drop 3drop " " 0 dup 2dup leave then loop 2drop 2drop type 266 +loop cr 5de +loop