[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: System.map irritation

On Thu, Jan 11, 2001 at 05:18:38PM +0400, Rino Mardo wrote:
> On Thu, Jan 11, 2001 at 04:30:25PM +0700 or thereabouts, Oki DZ wrote:
> > Hi,
> > 
> > I have the same problem after upgrading my (system's) kernel to 2.4.0.
> > I put the 2.4.0 source to /usr/src2/linux directory, and when top 
> > executed, the System.map looked up is the one in /usr/src/linux (in 
> > which I put the 2.2.13 source).
> why /usr/src2?  you should use /usr/src only and if you want to keep 2.2.13
> and 2.4.0 apart just use /usr/src/linux-2.4.0 and /usr/src/linux-2.2.13 with
> /usr/src/linux having a softlink to your current kernel directory.

indeed the /usr/src/linux `problem' does not exist on debian since it
does not use the broken /usr/include/linux -> /usr/src/linux

> i always copy the System.map to /boot and label it appropriately to dintiguish
> which one is for which kernel.

ps and friends will find /boot/System.map-`uname -r`

Ethan Benson

Attachment: pgpQo5P_4Xaek.pgp
Description: PGP signature

Reply to: