Benjamin Scott wrote:
>
> > Please tell me I don't need to rebuild my kernel ...
>
> "You don't need to rebuild your kernel."
>
> (Actually, that might be your best bet, but I didn't want to
> disappoint you... ;)
Right, that's what I did, using "make menuconfig" and meticulously
reading the kernel-HOWTO the whiles. Unfortunately, I find that
document lacking in a fairly important aspect: how to install the
newly-built kernel. After "make bzImage" it seems to just assume
you know what to do.
So I built a new kernel, copied the bzImage over to the same
directory lilo was using to find the old kernel, added an
entry to lilo.conf for it, and I can boot with it just fine.
I'm not quite ready to make it my default, though, because
of some niggling questions: like, what *should* I name the
new kernel? The last one is vmlinuz-2.2.12-20; this is the first
time I've rebuilt the kernel, so from whence does the '-20'
come? Should my new one be named '-21'? How about all the
other *-2.2.12-20* files, like the system map and the module-info
file? It seems to me that formally installing a new kernel is
*slightly* more involved than just copying over the compressed
image.. but I don't see the process documented.
I appreciate everyone's patience with my newbie-style questions.
Apache I know, but this aspect/level of Linux I'm still learning..
--
#ken P-)}
Ken Coar <http://Golux.Com/coar/>
Apache Software Foundation <http://www.apache.org/>
"Apache Server for Dummies" <http://Apache-Server.Com/>
"Apache Server Unleashed" <http://ApacheUnleashed.Com/>
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
