Re: System.map irritation
helixfish@gmx.net (Rino Mardo) writes:
> --EeQfGwPcQSOJBaQU
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Thu, Jan 11, 2001 at 04:30:25PM +0700 or thereabouts, Oki DZ wrote:
> > Hi,
> >=20
> > 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=20
> > executed, the System.map looked up is the one in /usr/src/linux (in=20
> > 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.
>
> >=20
> > BTW, I have removed the System.map's in /usr/src/linux and=20
> > /usr/src2/linux; surely enough, when top executed, there's no warning=20
> > reported. The question is, what's the use of the System.map file? (My=20
> > system working properly.)
>
> i always copy the System.map to /boot and label it appropriately to dintigu=
> ish
> which one is for which kernel.
>
>
If you use make-kpkg, it makes a deb file, that when installed,
does this for you.
--
* For God so loved the world that He gave his only begotten Son, *
* that whoever believes in Him should not perish... John 3:16 *
Reply to: