public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas de Grenier de Latour <degrenier@easyconnect.fr>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] USE Linux 2.6.x
Date: Tue, 21 Oct 2003 18:25:33 +0200	[thread overview]
Message-ID: <20031021182533.6a1246fe.degrenier@easyconnect.fr> (raw)
In-Reply-To: <200310210839.55102.cbrewer@stealthaccess.net>

On Tue, 21 Oct 2003 08:39:54 -0700
"C. Brewer" <cbrewer@stealthaccess.net> wrote:

> On Tuesday 21 October 2003 5:58, Mike Frysinger wrote:
> > On Tuesday 21 October 2003 08:48, Dhruba Bandopadhyay wrote:
> > > How must a package determine what kernel is system is using?
> >
> > it uses the /usr/src/linux symlink to determine running kernel ...

Not exactly the _running_ kernel, but the _target_ kernel.
 
> But why do we keep up with the obselete link? 

Because it is useful to be able to compile modules for a target kernel
that may be different than the running kernel, and a symlink is a
good way to point the target of your choice.

> So we still have link climbing even though we have the linux-headers
> package which is supposed to prevent just that...  

I don't see how system headers are related to modules compilation. The
flameable symlink is the /usr/include/linux, but it's a different issue.
It is something that on some other distros points on kernel includes
from kernel sources, but as you said, on Gentoo, we have a linux-headers
package and a real directory, so we do things the right way.


Now, about /usr/src/linux-beta, I don't neither understand its semantics
or usefulness. Obviously, /usr/src/linux is the way to go also for 2.6
kernels, at least that's what is assumed in modules ebuilds, so I
usually just delete linux-beta or ignore it.

-- 
TGL.

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-10-21 16:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21 12:48 [gentoo-dev] USE Linux 2.6.x Dhruba Bandopadhyay
2003-10-21 12:58 ` Mike Frysinger
2003-10-21 15:39   ` C. Brewer
2003-10-21 16:25     ` Thomas de Grenier de Latour [this message]
2003-10-21 17:44       ` C. Brewer
2003-10-21 20:15         ` Grant Goodyear
2003-10-22  3:11           ` C. Brewer
2003-10-21 20:53         ` Martin Schlemmer
2003-10-21 22:25         ` Spider
2003-10-22  3:44           ` C. Brewer
2003-10-22  8:15             ` Chris Smith
2003-10-22  8:17             ` Paul de Vrieze
2003-10-22 18:27               ` C. Brewer
2003-10-22 18:46                 ` Brian Jackson
2003-10-22 19:23                 ` Paul de Vrieze
2003-10-22 19:47                   ` C. Brewer
2003-10-22 20:06                     ` Spider
2003-10-22 10:40             ` Spider
2003-10-22 18:07               ` C. Brewer
2003-10-22 19:01                 ` Spider
2003-10-22 11:20           ` Patrick Lauer

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=20031021182533.6a1246fe.degrenier@easyconnect.fr \
    --to=degrenier@easyconnect.fr \
    --cc=gentoo-dev@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