On Mon, 01 May 2000, Dr.-Ing. Edgar Alwers wrote about, Re: Kernel Compilation:
> You wrote on Mon, 01 Mai 2000 :
> > Hi everyone,
> > I recompiled on a RH Linux 6.1 (kernel 2.2.12-20) the sources of 2.2.14
> > kernel. My problem is the System.map file .. how can I get the one for
> > 2.2.14 kernel ? Now it loads the 2.2.12-20 System.map. Could you help me ?
> >
> > Thanks.
>
> The System.map file depends on the actual kernel and is being generated every
> time the kernel is compiled. So you should look for this file ( in SuSE it is
> placed in /usr/src/linux/ , it shouldnt be very different in RH ) and copy it
> to /boot. If you use "make lilo" or "make bzlilo", this script should do the
> job for you. I hope this helps.
Your comments are valid, however not quite correct, let me point out that
the above is not such a good idea for one who has little or next to nothing
experiance in compiling new kernels.
Using 'make zlilo' copy's /usr/src/linux/System/map to "/" automaticly if
the compile was successful. Note the differance, the default is "/" not
/boot
If one wants to have it placed into /boot or any other place defined in
/etc/lilo.conf then one HAS to edit the TOP_DIR (as its called) Makefile
located in /usr/src/linux, the following is text from that file;
# INSTALL_PATH specifies where to place the updated kernel and system map
# images. Uncomment if you want to place them anywhere other than root.
#INSTALL_PATH=/boot
Note, INSTALL_PATH is commented out.
Further to my first comment on "not such a good idea".
If a not so experianced user compiles his/her own kernel and "forgets" to
include an essential option, be it a driver or filesystem, then it could be
fatal upon booting, so now the user has no system AT ALL, he/she is then
forced to use the emergency disk set(s) from his/her distribution, IF THEY
WERE CREATED in the first place, how many times have we seen messages
here about systems not booting and the operators NOT having created rescue
disks.!!
It is a far beter idea to 'manualy' copy;
/usr/src/linux/arch/i386/boot/zImage {bzImage}
and create another entry in /etc/lilo.conf and of course keep the old image
intact.
I even used to do 'make zdisk' to place the new image on a floppy, this has
the advantage of not needing to edit "anything", keeping the old system
intact, if the floopy image fails to boot the system, simply extract the
floppy and reboot in the old normal manner and recompile another kernel
including the corrections.
Of course if one reads;
/usr/doc/HOWTOS/Kernel.HOWTO (Directory differs in different distro's).
/usr/src/linux/README
Then one will have much more insight on howto configure, compile and
install a new kernel.
As i explained before, there is no real need to place System.map in the
same directory as the image.
> Edgar
Thanks anyway for your input.
>
>
> _______________________________
> Dr.-Ing.Edgar Alwers
> Weinheim, Germany
> Mailto: [EMAIL PROTECTED]
>
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
