From: Patrick Lauer <gentoo@toso-digitals.de>
To: Spider <spider@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] USE Linux 2.6.x
Date: Wed, 22 Oct 2003 13:20:22 +0200 [thread overview]
Message-ID: <1066821622.2029.12.camel@localhost> (raw)
In-Reply-To: <20031022002531.1bfc861b.spider@gentoo.org>
On Wed, 2003-10-22 at 00:25, Spider wrote:
> 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.
Yes, it makes more sense to "precompile" everything beforw a reboot.
> 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.
Even worse:
1) emerge vanilla-sources
2) build kernel
3) emerge -U world a while later
--> Now you're using a kernel that has been compiled from 2.4.19, but
/usr/src/linux either points into the nirvana or to 2.4.22 which you
didn't order, which you do not use at the moment ...
I'd like to have kernels "sticky" so that they don't get updated unless
told to (and please don't tell me that I should put my kernel into
package.mask, that's not intuitive and leads only to errors)
> When you get this set to -automagically- detect the target kernel.,
> build modules and fix. then ok.
Sometimes a newer kernel won't boot with the same config. I'm still
using 2.4.19 because all the newer kernels ignore at least one pci
device (like the ide controller or network card !?)
> 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.
So maybe kernel managment should be user-controllable, i.e. "don't install
kernels and use -->this one for everything" ?
> Yes, this thread invoked a lot of hot emotions from my side.
/me agrees
Patrick
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-10-22 11:20 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
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 [this message]
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=1066821622.2029.12.camel@localhost \
--to=gentoo@toso-digitals.de \
--cc=gentoo-dev@gentoo.org \
--cc=spider@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