[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: splitting up kernel-image into two pieces

>>"Nick" == Nick Cabatoff <ncc@cs.mcgill.ca> writes:

 Nick> It's not that it does anything 'wrong' per se, it's that I don't agree
 Nick> that installing a kernel image on a machine should make it the only
 Nick> operative one.  Put another way, I want to have multiple kernel images
 Nick> available sometimes; I don't want the order in which they're installed
 Nick> to matter, and I don't want putting the kernel on disk to potentially
 Nick> make the machine unbootable.  (These issues are particularly important
 Nick> to me because on our system packages are mostly installed 
 Nick> noninteractively.)

 	Well, I think you need a better designed lilo.conf. I have
 other entries in my lilo.conf than /vmlinuz and /vmlinuz.old; I have
 stable, unstable, and the initrd stuff from boot floppies in there;
 you perhaps need to have something like that too. 

 Nick> The immediate motivation for me was that I was irritated that when
 Nick> installing different kernel-images on a machine I had to boot off a
 Nick> floppy.  Scenario:

 Nick> - install image A on machine - now the old kernel I had gets moved to
 Nick>   vmlinuz.old
 Nick> - discover image A doesn't boot, so try image B - now A is
 Nick>   vmlinuz.old, and my old working kernel isn't listed in lilo.conf
 Nick> - reboot, curse, and go find a boot floppy

 	And fix lilo.conf to not let you back into this position
 again. I have posted a lilo.conf that should be an example.

 I really hate this damned machine I wish that they would sell it. It
 never does quite what I want But only what I tell it.
Manoj Srivastava   <srivasta@debian.org>  <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Reply to: