From: Jerry McBride <mcbrides9@comcast.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] linux symlink?
Date: Sun, 4 Feb 2007 12:39:07 -0500 [thread overview]
Message-ID: <200702041239.08039.mcbrides9@comcast.net> (raw)
In-Reply-To: <200702041451.44536.shrdlu@unlimitedmail.org>
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.
--
--
Jerry McBride
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-02-04 17:44 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 [this message]
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
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=200702041239.08039.mcbrides9@comcast.net \
--to=mcbrides9@comcast.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