From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19606 invoked by uid 1002); 22 Oct 2003 11:20:46 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 7752 invoked from network); 22 Oct 2003 11:20:46 -0000 From: Patrick Lauer To: Spider Cc: gentoo-dev@gentoo.org In-Reply-To: <20031022002531.1bfc861b.spider@gentoo.org> References: <4866.146.176.63.67.1066740482.squirrel@mail.codewordt.co.uk> <200310210839.55102.cbrewer@stealthaccess.net> <20031021182533.6a1246fe.degrenier@easyconnect.fr> <200310211044.48299.cbrewer@stealthaccess.net> <20031022002531.1bfc861b.spider@gentoo.org> Content-Type: text/plain Message-Id: <1066821622.2029.12.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Wed, 22 Oct 2003 13:20:22 +0200 Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-dev] USE Linux 2.6.x X-Archives-Salt: 41d3f666-b09e-4fd4-bcf7-49d7aae428b5 X-Archives-Hash: 98d021b451071328e6f4974ac071910c 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