Here is my lilo.conf:
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
image=/boot/vmlinuz
label=linux
root=/dev/sda1
read-only
image=/boot/vmlinuz.old
label=old
root=/dev/sda1
read-only
image=/boot/vmlinuz.good
label=good
root=/dev/sda1
read-only
when I make a new kernel, the old kernel _automatically_ gets moved
to vmlinuz.old by the makefile. And I _always_ have a linux.good image
that I _know_ works in case either of the other two don't...
works like a champ for me... and I _never_ reboot and then discover
I forgot to run lilo, or edit lilo.conf or whatever...
Makes the Makefile work like it was intended also...
Robert Hyatt Computer and Information Sciences
[EMAIL PROTECTED] University of Alabama at Birmingham
(205) 934-2213 115A Campbell Hall, UAB Station
(205) 934-5473 FAX Birmingham, AL 35294-1170
On Sat, 18 Sep 1999, Brian Macy wrote:
> Though this suggestion makes it easier, it also gets rid of the ability
> to go back to previous kernels in case there is a problem. I find it
> easier just to copy the 12 files and copy/edit the 4-5 lines just so I
> can go back to any kernel I've built.
>
> Brian Macy
>
> "Robert M. Hyatt" wrote:
> >
> > if you edit lilo.conf as I have mentioned in the past (redhat has
> > a brain-dead version that specifically has the version number in
> > the image specification) and just point it at vmlinuz, you don't
> > have to copy the executable, nor do you have to do anything other
> > than the make install. We support about 15 linux boxes and do this
> > all the time...
> >
> > Robert Hyatt Computer and Information Sciences
> > [EMAIL PROTECTED] University of Alabama at Birmingham
> > (205) 934-2213 115A Campbell Hall, UAB Station
> > (205) 934-5473 FAX Birmingham, AL 35294-1170
> >
> > On Fri, 17 Sep 1999, John Aldrich wrote:
> >
> > > On Fri, 17 Sep 1999, Robert M. Hyatt wrote:
> > >
> > > > make that make config;make dep; make clean; make install;
> > > > make modules;make modules-install
> > > >
> > > > and you are ready to boot. that does the lilo install and
> > > > everything you need without all the extra steps...
> > > >
> > > I would still manually copy the new kernel from
> > > /usr/src/linux/<kernel> to /boot/vmlinuz as when I compiled it didn't
> > > do that. I would also manually edit the lilo.conf file to show the
> > > new kernel, as MY lilo.conf wasn't automagically edited either. Then,
> > > run /sbin/lilo (obviously as root) and THEN reboot.
> > >
> > > I don't know what Mr Hyatt's experience is, I can only speak from my
> > > one-day of compiling kernels in an unsuccessfull attempt to get SMP
> > > working on my machine. :-(
> > > John
> > >
> >
> > -
> > Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
> > To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
>
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
