[NTLUG:Discuss] 2 kernels in Lilo

[MadHat]

At 10:49 AM 2/2/2001 -0600, you wrote:
>The lilo.conf tweaking is usually because Make Install doesn't set the
>default to be the new kernel  (which may be by design... I don't
>know).  You're right though... I should have mentioned running lilo again
>after the tweaking.

make install just runs lilo, it doesn't touch the config.  And the way make 
install works is that it creates a generic name of /boot/vmlinuz, but the 
default lilo.conf points to /boot/vmlinux-VERSION so it won't ever see the 
new kernel until you make some sort of updates.
I usually do something like

boot=/dev/...
map=/boot/map
prompt
timeout=10
default=linux

image=/boot/vmlinuz
   label=linux
   root=/dev...

image=/boot/vmlinuz-ORIG-VER
   label=safe
   root=/dev/...

that way the new kernels that I build will always be the default, and the 
orig version of the kernel will be available by typing safe at the LILO: 
prompt...  I know, a little too "Windows" for some, but it works quite well 
for my needs...

>Michael
>
>--
>Michael Patrick
>michael at techiesplace.com
>"Bester:  It is nice to know they are continuing the practice of hiring
>from the shallow end of the gene pool."
>
>On Fri, 2 Feb 2001, MadHat wrote:
>
> >
> > I would recomend editing lilo.conf before doing a make install, because the
> > last step in a make install is to run lilo.
> >
> > At 11:08 PM 2/1/2001 -0600, you wrote:
> > >Here is my lilo.conf file, which contains entries for 3 kernels
> > >(RH7.0 system)
> > >
> > >My build sequence has always been:
> > >
> > >./configure
> > >make dep
> > >make bzImage
> > >make modules
> > >make modules_install
> > >make install
> > >
> > >then I have to check the lilo.conf and reboot
>
>_______________________________________________
>http://ntlug.org/mailman/listinfo/discuss

--
MadHat at unspecific.com