On Sun, Feb 04, 2007 at 01:43:22PM -0600, Dan Farrell wrote: > On Sun, 4 Feb 2007 12:39:07 -0500 > Jerry McBride <[EMAIL PROTECTED]> wrote: > > > On Sunday 04 February 2007 08:51:44 am Etaoin Shrdlu wrote: > > > On Sunday 4 February 2007 13:45, Jorge Almeida wrote: > > > > I was under the impression that it is necessary to install Nvidia > > > > drivers. Is this correct? > > > > > > If the link is not in place, nvidia-drivers will not build. > > > > > > > And what should be done with the System.map file? Copy it to /boot > > > > under which name? (I mean, when booting with a particular kernel, > > > > how does the kernel know the path to the correct System.map?) > > > > > > There used to be a good system.map explanation here: > > > > > > http://dirac.org/linux/system.map/ > > > > > > however, it seems to have some problem at the moment. The google > > > cached copy works (just do a search for linux system.map, it's the > > > first hit). > > > > > > Sorry, cannot comment on whether the symlink should or should not be > > > created, and it's been a lot since I built my last LFS. I have > > > almost always used it, and never had any problem. IIRC the > > > handbook's advice is to create the link. But, as always, YMMV. > > > > The server ar dirac.org need a kick, I emailed the admin there. As > > for the symlink with LFS... LFS is a totally different animal than > > most distributions. For us, the link is required in order to emerge > > anything that touches the kernel sources. > > > I stopped copying System.map very often and it doesn't seem very > useful.. I think copying it to /boot is mostly for recovery purposes, > like .config being copied into /boot. that way you can rebuild the > kernel if you need to.
AFAIK about System.map is it is not for recovery, but for debugging. If kernel crashes, it tries get one to tell where it crashed, give you backtrace and like that. It's easier to find the bug with it, so unless you do not have a kernel that will ever crash, or you do not want to send bug reports, you do not need one. -- BOFH Excuse #452: Somebody ran the operating system through a spelling checker. Michal 'vorner' Vaner
pgplezMpkE8t5.pgp
Description: PGP signature
