From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: 2.6.18 kernel
Date: Thu, 2 Nov 2006 00:42:47 +0000 (UTC) [thread overview]
Message-ID: <eibeu7$6ht$2@sea.gmane.org> (raw)
In-Reply-To: 4548D810.3010103@ercbroadband.org
"Mark Haney" <mhaney@ercbroadband.org> posted
4548D810.3010103@ercbroadband.org, excerpted below, on Wed, 01 Nov 2006
12:23:28 -0500:
> Is it just me or is the .18 kernel slow in getting unmasked? I don't
> recall any other releases taking as long to be marked stable, but then I
> haven't been quite as anxious to test a new kernel as I have been for
> .18. I'm sure people are running it, so I ask, how is it? Has it been
> stable or is it not quite ready for us 'less than hardcore' testers?
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. If a new kernel.org kernel doesn't work, I just keep using
the old one until the next -rc or whatever that /does/ work. I had been
doing it that way long before I switched to Gentoo, so I just kept doing
what I had always done. The only thing I needed to do was add a kernel
entry to package.provided, so various packages in portage with a
dependency on the kernel knew it was there. Here's my package.provided
file. Note that I use ridiculously high versions like 999, or 2.6.999 for
the kernel, so I don't have to worry about dependency version number creep:
~$cat /etc/portage/profile/package.provided
# portage always considers these packages merged,
# and won't attempt to merge them.
################################################################################
# profile related
# in profile as virtual/ssh but unneeded
net-misc/openssh-99
# in profile but unneeded
sys-apps/busybox-99
# don't use Gentoo kernels
sys-kernel/gentoo-sources-2.6.999
################################################################################
# X-related
# xorg-server thinks it needs, but 100dpi better
media-fonts/font-adobe-75dpi-99
# xinit needs for default Xsession, I use kde
x11-apps/xsm-99
# don't need xterm since I use kde/konsole
x11-terms/xterm-999
################################################################################
# proprietaryware related
# imagemagick thinks it needs
media-fonts/corefonts-99
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-11-02 0:44 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 ` Duncan [this message]
2006-11-02 17:30 ` [gentoo-amd64] " Christoph Mende
2006-11-02 16:51 ` Barry.SCHWARTZ
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='eibeu7$6ht$2@sea.gmane.org' \
--to=1i5t5.duncan@cox.net \
--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