From: Barry.SCHWARTZ@chemoelectric.org
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: 2.6.18 kernel
Date: Thu, 2 Nov 2006 10:51:14 -0600 [thread overview]
Message-ID: <20061102165114.GA10600@crud.crud.mn.org> (raw)
In-Reply-To: <1162488602.8082.3.camel@odin>
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
Christoph Mende <ch.mende@googlemail.com> skribis:
> On Thu, 2006-11-02 at 00:42 +0000, Duncan wrote:
> > FWIW, I handle my kernel stuff directly, downloading from kernel.org, not
> > thru portage. Thus, I care not one whit about Gentoo's kernel
> > stabilizing.
>
> echo "sys-kernel/vanilla-sources ~arch" >> /etc/portage/package.keywords
> emerge vanilla-sources
>
> does exactly the same, difference is that you don't have to check
> kernel.org for new released, emerge -u world does it.
I’ve found vanilla kernels to be much more reliable on my system than
Gentoo kernels (why I don’t know), and use sys-kernel/vanilla-sources
mainly for the above reason of not having to check kernel.org. Which
makes it slightly funny that, at the moment, I’m using 2.6.18.1 that I
downloaded myself from kernel.org. :)
--
Barry.SCHWARTZ at chemoelectric.org http://chemoelectric.org
Free stuff / Senpagaj varoj: http://crudfactory.com (PDF)
'Democracies don't war; democracies are peaceful countries.' - Bush
(http://www.whitehouse.gov/news/releases/2005/12/20051219-2.html)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-11-02 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 17:23 [gentoo-amd64] 2.6.18 kernel Mark Haney
2006-11-01 17:52 ` Andrei Slavoiu
2006-11-01 17:53 ` Hemmann, Volker Armin
2006-11-03 9:20 ` Peter Humphrey
2006-11-02 0:42 ` [gentoo-amd64] " Duncan
2006-11-02 17:30 ` Christoph Mende
2006-11-02 16:51 ` Barry.SCHWARTZ [this message]
2006-11-03 4:33 ` Vladimir G. Ivanovic
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=20061102165114.GA10600@crud.crud.mn.org \
--to=barry.schwartz@chemoelectric.org \
--cc=gentoo-amd64@lists.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