From: "J. Ryan Earl" <heretic@clanhk.org>
To: Timothy Miller <miller@techsource.com>
Cc: Stephen Hemminger <shemminger@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Distributions vs kernel development
Date: Sun, 09 May 2004 13:54:44 -0500 [thread overview]
Message-ID: <409E7E74.9040702@clanhk.org> (raw)
In-Reply-To: <409BC735.2060308@techsource.com>
Timothy Miller wrote:
> Stephen Hemminger wrote:
>
>> After having being burned twice: first by Mandrake and supermount,
>> and second
>> by SuSe and reiserfs attributes; are any of the distributions
>> committed to
>> making sure that their distribution will run the standard kernel?
>> (ie. 2.6.X from
>> kernel.org).
>
>
> I use Gentoo for this.
As do I, I've never had a problem with a Vanilla kernel or one of
Gentoo's maintained kernels. Gentoo actually supports the 2.6 kernel,
at least on AMD64 hardware that's all they support. Though the vanilla
kernels -do- work flawlessly, I still prefer the Gentoo patched kernels:
>>> Unpacking linux-2.6.5.tar.bz2 to
/var/tmp/portage/gentoo-dev-sources-2.6.5-r1/work
* genpatches-2.6-5.29-base.tar.bz2 unpacked
* genpatches-2.6-5.29-extras.tar.bz2 unpacked
* Applying
gentoo-dev-sources-2.6.5.CAN-2004-0109.patch...
[ ok ]
* Applying
1105_CAN-2004-0075-usb-vicam.patch...
[ ok ]
* Applying
1305_x86_64-2.6.5-rc3.patch...
[ ok ]
* Applying
1310_k8_cardbus_io.patch...
[ ok ]
* Applying
1315_alpha-sysctl-uac.patch...
[ ok ]
* Applying
1905_bluetooth-oops.patch...
[ ok ]
* Applying
2110_bcm5700_broadcom_gigabit_drvr_11272003.patch...
[ ok ]
* Applying
2115_fa311-mac-address-fix.patch...
[ ok ]
* Applying
2320_adaptec_dpt_i2o.patch...
[ ok ]
* Applying
2325_3ware-cmds_per_lun.patch...
[ ok ]
* Applying
2705_powernow-k8-acpi.patch...
[ ok ]
* Applying
3110_low-latency-cond_resched.patch...
[ ok ]
* Applying
3305_am9-2.6.4.patch...
[ ok ]
* Applying
3310_cfq-4.patch...
[ ok ]
* Applying
4105_lirc_infrared-2.6.5-rc2.patch...
[ ok ]
* Applying
4505_bootsplash-3.1.4-2.6.5-rc2.patch...
[ ok ]
* Applying
4705_squashfs-1.3r3.patch...
[ ok ]
* Applying
4710_lufs-0.9.7-2.6.0-test9.patch...
[ ok ]
* Applying
4715_supermount-2.0.4-2.6.5_rc1.patch...
[ ok ]
* Applying
4720_gcloop-2.6-20040330.patch...
[ ok ]
* Applying
4905_speakup_accessibility.patch...
[ ok ]
>>> Source unpacked.
The k8/x86_64, broadcom, and bootsplash patches in particular make me
happy. They tend to stay within one or two minor kernel revisions of
the current branch. I've had production 2.6 servers for months.
-ryan
next prev parent reply other threads:[~2004-05-09 18:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 15:53 Distributions vs kernel development Stephen Hemminger
2004-05-07 16:02 ` Arjan van de Ven
2004-05-07 16:03 ` Jeff Garzik
2004-05-07 21:20 ` Florian Weimer
2004-05-07 23:13 ` Paul Jakma
2004-05-09 6:49 ` Rene Rebe
2004-05-09 7:07 ` John Bradford
2004-05-09 8:52 ` Rene Rebe
2004-05-09 8:59 ` Grzegorz Kulewski
2004-05-09 9:13 ` Rene Rebe
2004-05-09 18:40 ` J. Ryan Earl
2004-05-24 19:17 ` Martin Schlemmer
2004-05-25 8:22 ` Rene Rebe
2004-05-25 17:53 ` Martin Schlemmer
2004-05-09 10:53 ` John Bradford
2004-05-12 19:11 ` Rob Landley
2004-05-19 8:49 ` John Bradford
2004-05-20 1:59 ` Rob Landley
2004-05-20 10:40 ` John Bradford
2004-05-24 18:31 ` Jon Portnoy
2004-05-25 10:49 ` John Bradford
2004-05-09 7:33 ` William Lee Irwin III
2004-05-09 21:06 ` Lech Szychowski
2004-05-07 16:05 ` Måns Rullgård
2004-05-07 16:22 ` Martin J. Bligh
2004-05-07 21:08 ` Daniel Egger
2004-05-07 17:09 ` Felipe Alfaro Solana
2004-05-07 17:28 ` Timothy Miller
2004-05-09 18:54 ` J. Ryan Earl [this message]
[not found] <1TfVQ-4T4-21@gated-at.bofh.it>
2004-05-07 18:42 ` Andi Kleen
2004-05-10 15:39 ` James Morris
2004-05-10 16:49 ` Chris Mason
2004-05-07 19:41 ` Pascal Schmidt
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=409E7E74.9040702@clanhk.org \
--to=heretic@clanhk.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
--cc=shemminger@osdl.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