mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rene Rebe <rene@rocklinux-consulting.de>
To: shemminger@osdl.org, linux-kernel@vger.kernel.org
Cc: rock-user@rocklinux.org
Subject: Re: Distributions vs kernel development
Date: Sun, 09 May 2004 08:49:23 +0200 (CEST)	[thread overview]
Message-ID: <20040509.084923.558886277.rene@rocklinux-consulting.de> (raw)
In-Reply-To: <409BB334.7080305@pobox.com>

Hi,

On: Fri, 07 May 2004 12:03:00 -0400,
    Jeff Garzik <jgarzik@pobox.com> 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). When running a non-vendor kernel, I need to reasonably expect that the system
> > will boot and all the filesystems and standard devices are available.  I don't
> > expect every startup script to run clean, or every device that has a driver
> > only in the vendor kernel to work. 
> 
> Fedora Core runs stock 2.4 and 2.6 kernels just fine...   :)
> 
> 	Jeff

Since other use this chance to propose already well known
distributions I just want to add that ROCK Linux is also designed to
run vanilla kernels - and in fact we only patch vitally important
changes (such as compile fixes / header fixes) into the -rock kernel.

  http://www.rocklinux.org

Sincerely yours,
  René Rebe
    - ROCK Linux stable release maintainer

--  
René Rebe - Europe/Germany/Berlin
  rene@rocklinux.org rene@rocklinux-consulting.de
http://www.rocklinux.org http://www.rocklinux-consulting.de


  parent reply	other threads:[~2004-05-09  6:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-07 15:53 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 [this message]
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
     [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=20040509.084923.558886277.rene@rocklinux-consulting.de \
    --to=rene@rocklinux-consulting.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rock-user@rocklinux.org \
    --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

all inboxes | Powered by JetHome®