tom brinkman wrote:
>
> On Saturday 06 July 2002 09:22 pm, Damian G wrote:
>
> > so, apparently, that system.map is not mandatory to make
> > a kernel boot....
>
> I don't believe so. When you install a Mandrake pre-compiled
> kernel the rpm (use 'rpm -ivh' ) it creates the proper links in /boot
> for you, besides generating a new initrd and edit/run lilo to add the
> new kernel. When I roll my own, I edit Makefile and change
> EXTRAVERSION = <new_indentifier>, but also I uncomment the line
> # export INSTALL_PATH=/boot (ie, remove the # ). Then a last
In my Mandrake 8.2 the "export INSTALL_PATH=/boot" comes uncommentted.
No need to uncomment it.
> command of 'make install' in the compile proccess also will make the
> proper links in /boot, make initrd, edit/run lilo, etc. for you.
My system does not run lilo during the 'make install' process. I must do
it myself. It does reconfig lilo.conf to add the new kernel.
>
> I use this /etc/bashrc alias to check,
> alias bootlinks='ll /boot/{initrd,vmlinuz,System.map}*'
> Typing 'bootlinks' then, at least initrd and vmlinuz should point to
> the right kernels (the current active links will be color hi-lited).
> My alias doesn't change anything, just displays the current state of
> important links in /boot. Until I boot the new kernel, the important
> links, initrd and vmlinuz point to the correct kernel(s), but
On my system after I do the 'make install', neither 3 of the files
points to the current working kernel. They all point to the new kernel
that has not been rebooted yet. I think I must miss understand what you
are saying!!
> System.map doesn't. After rebooting to the new kernel, all three
> then correctly point to the right kernel for all installed kernels.
On my system I can point System.map to a System.map that is totally
unrelated to the kernel that I boot and the system stills reboots &
operates correctly. I realize if the kernel 'oops' that the symbols in
the kernel will not resolve correctly, but 1.) I never have kernel
'oops': 2.) unless I could repeat the kernel 'oops' I don't care. If I
can repeat the kernel 'oops' then I could point System.map correctly. I
make no claim about knowing anything about how the System.map works.
Just on my system, System.map does not need to point to the correct
kernel for the system to boot.
> --
> Tom Brinkman Corpus Christi, Texas
>
> ------------------------------------------------------------------------
> Want to buy your Pack or Services from MandrakeSoft?
> Go to http://www.mandrakestore.com
I except the fact you have vastly superior knowledge than I about linux.
Therefore I would welcome anymore insight in how to switch 'System.map'
to point to the correct booted kernel when switching among kernels.
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
