[gentoo-user] linux symlink?

[gentoo-user] linux symlink?

[Jorge Almeida]

According to the LFS documentation
http://www.linuxfromscratch.org/lfs/view/stable/chapter08/kernel.html
the /usr/src/linux symlink pointing to the kernel source directory
should _NOT_ be created. The gentoo practice is different. Can someone
comment on this matter? Is the symlink necessary or is it some
historical leftover? I was under the impression that it is necessary to
install Nvidia drivers. Is this correct?
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?)

-- 
Jorge Almeida
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] linux symlink?

[Etaoin Shrdlu]

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.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] linux symlink?

[Michal 'vorner' Vaner]

[-- Attachment #1: Type: text/plain, Size: 535 bytes --]

On Sun, Feb 04, 2007 at 02:51:44PM +0100, 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.

Quite any ebuild that installs modules needs the symlink, as far as I
know.

-- 

This message has optimized support for formating.
Please choose green font and black background so it looks like it should.

Michal "vorner" Vaner

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] linux symlink?

[Jerry McBride]

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

Re: [gentoo-user] linux symlink?

[Dan Farrell]

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.  
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] linux symlink?

[Jorge Almeida]

On Sun, 4 Feb 2007, Dan Farrell wrote:

> 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.  
> 
I have no idea how I could do that, I just would build the kernel using
.config. I suppose it's not important, but a unhappy message about it
sometimes appear in the boot messages...

Thanks.

-- 
Jorge Almeida
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] linux symlink?

[Michal 'vorner' Vaner]

[-- 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 --]

Re: [gentoo-user] linux symlink?

[Mark]

On 04/02/07, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
> I have no idea how I could do that, I just would build the kernel using
> .config. I suppose it's not important, but a unhappy message about it
> sometimes appear in the boot messages...

My understand is that System.map can be used to regenerate a
modules.dep file, in case the modules directory took to a disaster.

depmod -F /boot/System.map-version

Thus fixing?

Also the LFS comment actually states:
 "must not be created on an LFS system as it can cause problems for packages"

I'll take a swipe at the fact that certain packages under the LFS
method will not install.

Thanks
Mark
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] linux symlink?

[Jorge Almeida]

On Mon, 5 Feb 2007, Mark wrote:

> On 04/02/07, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
> > I have no idea how I could do that, I just would build the kernel using
> > .config. I suppose it's not important, but a unhappy message about it
> > sometimes appear in the boot messages...
> 
> My understand is that System.map can be used to regenerate a
> modules.dep file, in case the modules directory took to a disaster.
> 
> depmod -F /boot/System.map-version
> 
> Thus fixing?
?
> 
> Also the LFS comment actually states:
> "must not be created on an LFS system as it can cause problems for packages"
> 
> I'll take a swipe at the fact that certain packages under the LFS
> method will not install.
I suppose those packages would use the kernel headers (a no-no) instead
of the headers associated with the compilation of glibc.
It would be nice to have more information on this issue...
> 
> Thanks
> Mark
> 
Thank you.

-- 
Jorge 
-- 
gentoo-user@gentoo.org mailing list