Messages in this thread | | | From | "Albert D. Cahalan" <> | Subject | Re: [PATCH] 2.2: /proc/config.gz | Date | Thu, 31 Aug 2000 14:32:24 -0400 (EDT) |
| |
Robert Greimel writes:
>> BTW, /boot/System.map-`uname -r` is the first place in which >> procps looks for the the System.map data. Red Hat and Debian > > Yes, but it is no good if you switch between different kernel > versions as you will get error messages about System.map being > the wrong version number (unless you copied it every time you > boot a different kernel, of course).
Huh? The version number is right there. For example: /boot/System.map-2.3.99-pre3
Doing a "make install" should put System.map in the right place. Unless you have scripts to update them at boot, I suggest that you delete /System.map, /boot/System.map, and any other unversioned copies you might have floating around.
You don't get the build number or a unique ID. This is a flaw but see below...
> /lib/modules/<release> is a much more natural place, IMHO. > I would even go so far as to say that procps should look > there first before looking in /boot.
Nope. The "release" is exactly what gets used in /boot. There is no advantage here.
Modules might not exist, and System.map has nothing to do with modules anyway. System.map is derived from the kernel.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |