From: Spider <spider@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] USE Linux 2.6.x
Date: Wed, 22 Oct 2003 00:25:31 +0200 [thread overview]
Message-ID: <20031022002531.1bfc861b.spider@gentoo.org> (raw)
In-Reply-To: <200310211044.48299.cbrewer@stealthaccess.net>
[-- Attachment #1: Type: text/plain, Size: 2171 bytes --]
begin quote
On Tue, 21 Oct 2003 10:44:36 -0700
"C. Brewer" <cbrewer@stealthaccess.net> wrote:
> On Tuesday 21 October 2003 9:25, Thomas de Grenier de Latour wrote:
>
> > 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.
>
> Sure, that's an excellent point, but since the target kernel and the
> running kernel are likely on the same machine, and the current state
> of modules in portage IIRC isn't allowing the duplication of external
> modules packages, why not just be booted into the one you're making
> modules for? You're gonna end up rebooting either way eventually...
Then fix pcmcia-cs and alsa-driver before you suggest anything. as it
is, my machine won't boot properly without pcmcia-cs -and- alsa, as they
IRQ conflict unless loaded in a certain order.
They are both dependant on the target module, and theres no way in a
gnomes purple hell you are going to get me into a state where I can
reboot first, and then rebuild the modules, only to reboot again so I
have a working boot session. uh-oh- NO.
And no, you won't get me to emerge it with SLOT="purple-gnomes-2.4.44"
either, Just because I sat down and got my own kerneltree installed into
usr/src/testkernelwithextraJFSpatches , and then loose my existing ,
working, tried kernelset.
When you get this set to -automagically- detect the target kernel.,
build modules and fix. then ok.
if you want it to depend on the running kernel, erm... No. theres a few
things already that do so, and that is -BROKEN- behaviour. I don't even
-HAVE- the sources for my running kernel at most times. What? No I
don't need them. I shouldn't need to have my sources for the hard
compiled and working copy of 2.4.18-saviour with extra everything that I
know boots all my machines and I have in a .tar stored away for working
order.
Yes, this thread invoked a lot of hot emotions from my side.
// Spider
--
begin .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-21 22: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
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 [this message]
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=20031022002531.1bfc861b.spider@gentoo.org \
--to=spider@gentoo.org \
--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