VanLUG Email Archive
Ian Morey (bunmorey@home.com)
Tue, 17 Aug 1999 23:13:06 -0700
At 03:21 AM 17/08/99 -0700, you wrote:
> > -- Hmmm, when I do that I also have to move System.map from the
> > /usr/src/linux with a name change.... though it may not be really
> > necessary. Then move the kernel from /usr/src/linux/arch/i386/boot (or
> > something like that) to /boot, usually with a name change so I can have a
> > kernel choice at boot. Then edit /etc/lilo.conf and run lilo.
> > Then my machine can boot into the New kernel... hopefully. :)
>
>Well that's an awful lot of work to go though for nothing. Just make sure
>your lilo.conf contains entries for vmlinuz and vmlinuz.old and make bzlilo
>(as opposed to make bzImage) will take care of the rest. I compile several
>kernels a week, I'd go insane doing that for each, bad enough getting them
>and the modules to the appropriate machines.
>
>--
> Mike Bell
Doh!!
The shame of it all.... :) My eyes saw bzlilo, but my brain read
bzImage.
My apologies!!
I haven't even ever tried out doing a bzlilo - last time a tried a
zlilo(?), (years ago), I didn't know your neat trick with "make zlilo &&",
and used "make zlilo; make modules;" etc. The kernel ended up too big,
failed the build, but did everything else, so I rebooted into limbo.
After a long time figuring out how to do a rescue; never having
need to do one before in 2 years.... not like in Windows where it is about
the first thing you learn... I just started doing kernel builds the hard
way. Actually forgot that there was an easier way.
Sorry for misinterpreting your mail.... I just love making myself
look like an idiot in public. ;)
Cheers,
Ian
This archive was generated by hypermail 2.0b3 on Thu 09 Sep 1999 - 06:40:35