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

Re: System.map irritation

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.

> BTW, I have removed the System.map's in /usr/src/linux and 
> /usr/src2/linux; surely enough, when top executed, there's no warning 
> reported. The question is, what's the use of the System.map file? (My 
> system working properly.)

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


Key fingerprint = 9DE1 5825 77B4 FF45 7485  D3EB DCCF DE48 09B6 4426

"Who's watching the watchmen?"

Attachment: pgpUSSZC7Hw1S.pgp
Description: PGP signature

Reply to: