On Tue, 05 Oct 1999, Tom Gilbert wrote:
>* Clyne, Paul ([EMAIL PROTECTED]) wrote:
>>
>> Good listers,
>>
>> Firstly apologies if this is not the most correct list to send to.
>> Secondly please explain things simply..I'm a newbie
>>
>> I recently recompiled my Kernel (RH 6.0, 2.2.11) and had some
>> questions I would like to ask.
The biggest open secret when compileing a new kernel is to edit the
topdir Makefile /usr/src/linux/Makefile and define the EXTRAVERSION
EXTRAVERSION = -1 or what ever you choose, could be -first-attemt if
you want, but DONT forget to use the - sign at the beginning.
>> When I rebooted I got message(s) similar to the following :
>> Starting lpd : Warning: /boot/System.map has an incorrect Kernel
>> version.
>>
>> Q1) exactly what does this mean ?
>
>It means the System.map in /boot is the one from your last kernel. Copy the
>one created in /usr/src/linux when you compiled your kernel to /boot.
How about renaming the old one first so thst the old kernel stays
useable, of course /etc/lilo.conf will need to be edited to reflect
the changes, and lilo must be rerun.
>
>> Q2) I thought that when I did a make bzImage (or possibly during the
>> make modules_install ?) that a copy of the new system/map would
>> automatically be put in /boot. I vi'ed the Makefile and noticed that the
>> system.map section had a comment like "uncomment this bit if you want to put
>> the Sysem.map anywhere other than root". Shouldn't the default directory be
>> boot ?. Should I modify the Makefile to always point at /boot ?
>
>This part of the Makefile is only for
>$ make install
Not any more, even if its commented out, make install will still copy
"everything" to /boot yes even System.map.
>Which you are not recommended to do. Make bzImage creates the
kernel, but >doesn't move *anything* out of that directory and onto
the system. >That would be the territory of make install.
>
>Again, don't use make install.
make install is just what he needs, it even copies Sysem.map bzimage
copies the old /boot vmlinux to vmlinux.old System.map.old
and it even makes symbolic links for you, really make install is
the BEST way.
>
>> Q3) I cp'ed the System.map file from /usr/src/linux to the boot
>> directory and that fixed the problem (but has raised a few other questions)
>> was this a wise think to do ?. If not, what should I have done ?.
>
>Cha-ching! This is the correct thing to do!
If he copied the old one to another name first of course, it would
then still be useable.
>
>> Q4) System.map _was_ a link to System.map-2.2.5-22 (the previous
>> kernel) but I also notice that there still is a System.map-2.2.55-22Boot and
>> System.map-2.2.55-22smp. I didn't update these files (do I need to ?,
>> where do I find the 'correct' files ?).
>
>Don't worry. It is a convention (and a useful one) when compiling a
>new kernel to put the new kernel in /boot as vmlinuz_${version}, and
>the same System.map, etc, and then link to the one you just made with
>ln -s vmlinuz_${version} vmlinuz
Use make install it does it for you as explained above.
>
>This way, if your new kernel is crappy, just change the links to point
>back to the previous kernel etc.
Realy there is even no need to d that, the rc.sysinit script will
take care of that at bootime by looking with 'uname-r' to see which
kernel is being booted and the rest is done by that piece of Linux
magic.
>
>> Q5) What does System.map-2.2.55-22Boot and System.map-2.2.55-22smp
>> actually do ?. I read the HOWTO several times and there is no mention of
>> these two files.
>
>Redhat distro comes with a precompiled kernel, *and* another for SMP
>machines (multiple processors), these are not needed once you
>recompile a kernel for yourself.
No but System.map is needed by modprobe to get its kernel symbols,
and is also used for tracing kernel oopsen, something which normally
should not occour.
>
>> Q6) is there a HOWTO or other suggested reading that would answer my
>> questions ?
>
>Dunno.
>
/usr/doc/HOWTO/Kernel-HOWTO
/usr/src/linux/README
>> I'm sure that answering these questions will lead to others so
>> thanks in advance.
>>
>> And I apologies if this mail is not in 'text' format. I have tried
>> to force Windoze to send it text, but being a M$ product, who knows how it
>> will _really_ behave.
>
>Seems ok to me, but then my .procmailrc forces html mail through lynx to
>convert it to plain text :-)
>
>> Lastly, please also send any responses to me ([EMAIL PROTECTED]) as
>> well as the list.
>
>Tom.
>--
> .-------------------------------------------------------.
> .^. | Tom Gilbert, England | [EMAIL PROTECTED] |
> /V\ |----------------------| www.tomgilbert.freeserve.co.uk |
> // \\ | Sites I recommend: `--------------------------------|
> /( )\ | www.freshmeat.net www.enlightenment.org www.gnome.org |
> ^^-^^ `-------------------------------------------------------'
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
