From: Martin Schlemmer <azarah@gentoo.org>
To: "C. Brewer" <cbrewer@stealthaccess.net>
Cc: Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] USE Linux 2.6.x
Date: Tue, 21 Oct 2003 22:53:57 +0200 [thread overview]
Message-ID: <1066769636.11872.172.camel@nosferatu.lan> (raw)
In-Reply-To: <200310211044.48299.cbrewer@stealthaccess.net>
[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]
On Tue, 2003-10-21 at 19:44, C. Brewer wrote:
> The only modules discussion so far, other than what you recently brought up,
> was Mike's example of how the nvidia-modules package determined the running
> kernel. The original question was how does a package(generic) determine the
> running kernel. While I agree that there are some issues with the modules
> packages that should be handled differently, no package that doesn't provide
> modules should care what kernel you're running.
IMHO, the original question was 'asked incorreclty'. Or then out of a
Gentoo point of view.
We generally do not care what kernel is running - sure, we do wonder
what ARCH we running on, but then that we usually set in make.conf :/
For our purpose, we care about the target kernel - ie, what kernel
should we compile this module for, or (and this might be related to
some other comments from you) what kernel should we use for this
broken user-space program that need kernel headers, and not the
generics in /usr/include.
Sure, Linus might not agree with /usr/src/linux, but then it is
known, and as far as I know there is no problems (except your
usual problems which is package specific and would be broken
anyhow if not current headers was there).
Hope I was not too confusing :)
Thanks,
--
Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-21 20:53 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
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 [this message]
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=1066769636.11872.172.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=cbrewer@stealthaccess.net \
--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