From: "Michal 'vorner' Vaner" <michal.vaner@kdemail.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] linux symlink?
Date: Sun, 4 Feb 2007 21:43:47 +0100 [thread overview]
Message-ID: <20070204204347.GA27998@tarantula> (raw)
In-Reply-To: <20070204134322.1d0d0973@pascal.spore.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 2227 bytes --]
On Sun, Feb 04, 2007 at 01:43:22PM -0600, Dan Farrell wrote:
> On Sun, 4 Feb 2007 12:39:07 -0500
> Jerry McBride <mcbrides9@comcast.net> 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
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-02-04 20:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-04 12:45 [gentoo-user] linux symlink? Jorge Almeida
2007-02-04 13:51 ` Etaoin Shrdlu
2007-02-04 14:47 ` Michal 'vorner' Vaner
2007-02-04 17:39 ` Jerry McBride
2007-02-04 19:43 ` Dan Farrell
2007-02-04 20:14 ` Jorge Almeida
2007-02-05 20:17 ` Mark
2007-02-05 20:32 ` Jorge Almeida
2007-02-04 20:43 ` Michal 'vorner' Vaner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070204204347.GA27998@tarantula \
--to=michal.vaner@kdemail.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox