Re: [Linux-ia64] Re: [PATCH] head.S fix for unusual load addrs

From: Keith Owens <kaos_at_ocs.com.au>
Date: 2003-05-08 10:24:13
On Wed, 7 May 2003 17:07:42 -0700, 
"Luck, Tony" <tony.luck@intel.com> wrote:
>David wrote
>> How many tools are out there that depend on System.map or similar?  I
>> suppose you could just generate a fresh System.map at boot time (or
>> have something like /proc/System.map).
>
>Apparently a few, but not a vast number ... on RedHat AS2.1:
>
> # grep -rl 'System.map' /bin /usr/bin /usr/sbin /etc /sbin
>   /bin/ps
>   /usr/bin/ksymoops
>   /usr/bin/kpm
>   /usr/sbin/readprofile
>   /etc/rc.d/rc.sysinit
>   /etc/rc.sysinit
>   /sbin/depmod
>   /sbin/insmod.static
>   /sbin/insmod
>   /sbin/modprobe
>   /sbin/ksyms
>   /sbin/kallsyms
>   /sbin/lsmod
>   /sbin/modinfo
>   /sbin/rmmod
>   /sbin/klogd
>   /sbin/installkernel
>   /sbin/new-kernel-pkg

Out of the modutils programs, only depmod actually reads System.map and
only when doing make modules_install.  It does not care about the
addresses, only if a symbol is exported or not.  insmod, modprobe,
ksyms, lsmod, modinfo, rmmod contain a reference to System.map because
of a table that lists files that might appear in /lib/modules/`uname -r`,
they only care about the file name, not its contents.

kallsyms will require run time relocation, its table uses absolute
kernel addresses.

rc.sysinit only looks for the file System.map so it can set up a
symlink, it does not read the contents.

installkernel and new-kernel-pkg just copy System.map so other tools
can find it.

klogd, ps, readprofile and lkcd (not on that list) will need a clean
copy of System.map.  IOW it has to be regenerated for those programs.

Don't know about kpm.
Received on Wed May 07 17:24:33 2003

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:14 EST