1 |
On Sun, 4 Feb 2007 12:39:07 -0500 |
2 |
Jerry McBride <mcbrides9@×××××××.net> wrote: |
3 |
|
4 |
> On Sunday 04 February 2007 08:51:44 am Etaoin Shrdlu wrote: |
5 |
> > On Sunday 4 February 2007 13:45, Jorge Almeida wrote: |
6 |
> > > I was under the impression that it is necessary to install Nvidia |
7 |
> > > drivers. Is this correct? |
8 |
> > |
9 |
> > If the link is not in place, nvidia-drivers will not build. |
10 |
> > |
11 |
> > > And what should be done with the System.map file? Copy it to /boot |
12 |
> > > under which name? (I mean, when booting with a particular kernel, |
13 |
> > > how does the kernel know the path to the correct System.map?) |
14 |
> > |
15 |
> > There used to be a good system.map explanation here: |
16 |
> > |
17 |
> > http://dirac.org/linux/system.map/ |
18 |
> > |
19 |
> > however, it seems to have some problem at the moment. The google |
20 |
> > cached copy works (just do a search for linux system.map, it's the |
21 |
> > first hit). |
22 |
> > |
23 |
> > Sorry, cannot comment on whether the symlink should or should not be |
24 |
> > created, and it's been a lot since I built my last LFS. I have |
25 |
> > almost always used it, and never had any problem. IIRC the |
26 |
> > handbook's advice is to create the link. But, as always, YMMV. |
27 |
> |
28 |
> The server ar dirac.org need a kick, I emailed the admin there. As |
29 |
> for the symlink with LFS... LFS is a totally different animal than |
30 |
> most distributions. For us, the link is required in order to emerge |
31 |
> anything that touches the kernel sources. |
32 |
> |
33 |
I stopped copying System.map very often and it doesn't seem very |
34 |
useful.. I think copying it to /boot is mostly for recovery purposes, |
35 |
like .config being copied into /boot. that way you can rebuild the |
36 |
kernel if you need to. |
37 |
-- |
38 |
gentoo-user@g.o mailing list |