linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Wright <timw@splhi.com>
To: Tor Arntsen <tor@spacetec.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Will Mosix go into the standard kernel?
Date: Thu, 1 Mar 2001 11:13:02 -0800	[thread overview]
Message-ID: <20010301111302.A1476@kochanski.internal.splhi.com> (raw)
In-Reply-To: <fa.o4k0c0v.smgv2v@ifi.uio.no> <fa.m9jgfcv.17n8s2n@ifi.uio.no> <200103011502.QAA25429@pallas.spacetec.no>
In-Reply-To: <200103011502.QAA25429@pallas.spacetec.no>; from tor@spacetec.no on Thu, Mar 01, 2001 at 04:02:11PM +0100

On Thu, Mar 01, 2001 at 04:02:11PM +0100, Tor Arntsen wrote:
> Daniel Ridge <newt@scyld.com> writes:
> [...]
> >Compare this total volume to the thousands of lines of patches that
> >RedHat or VA add to their kernel RPMS before shipping. I just don't see 
> [...]
> 
> What's good about that?  The first thing I do is to rip out the RedHat
> kernel and compile and install a pure kernel from ftp.kernel.org. 

What's good is the added value that their customers gain. If you don't feel
there is any, then you're probably running the wrong distribution. The nice
thing with Linux is that you are free to go and grab your own kernel if you
wish to do so.

> It's *bad* that those vendors deliver hacked kernels.  It's not
> something that should be recommended as a *goal*!

No it isn't. You seem to assume that your requirements match everybody elses.
This is highly unlikely. A particular vendor will have a number of requirements
for their distribution (hopefully driven by customer demand). At the time that
they create a distribution, it's quite possible that no current pure kernel
meets those requirements. It's perfectly reasonable for a vendor to make
changes to meet those requirements, provided they abide by the licensing
demands. For instance, one major change in Red Hat 7.0 is that the kernel
supports USB. At the time, 2.4 wasn't ready and 2.2 didn't have support. What
do you suggest they should have done ?
The source code to the kernel that Red Hat ships is readily available, so I
fail to see why shipping a modified kernel is such a big issue.

> When I need a new kernel version I can't sit back and hope with 
> crossed fingers that RedHat (or whatever vendor) comes out with a 
> new, hacked version of Linus' latest.
> 

Commercial customers rarely "require a new kernel version". They may encounter
problems that require fixing the kernel, but otherwise, they frequently couldn't
care less about the kernel. In such cases, they need some form of support.
There's nothing to suggest that a vendor-modified kernel is inherently harder
to support, provided that it doesn't diverge too radically.

Most people buy computers to run applications, not
an operating system. Those of us who do work on OS's are in the distinct
minority. Given that Linus works on the development kernel, wanting to run
on "Linus' latest" implies you're not using Linux in production or that you're
very brave :-)

Regards,

Tim

-- 
Tim Wright - timw@splhi.com or timw@aracnet.com or twright@us.ibm.com
IBM Linux Technology Center, Beaverton, Oregon
Interested in Linux scalability ? Look at http://lse.sourceforge.net/
"Nobody ever said I was charming, they said "Rimmer, you're a git!"" RD VI

  reply	other threads:[~2001-03-01 19:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.o4k0c0v.smgv2v@ifi.uio.no>
     [not found] ` <fa.m9jgfcv.17n8s2n@ifi.uio.no>
2001-03-01 15:02   ` Will Mosix go into the standard kernel? Tor Arntsen
2001-03-01 19:13     ` Tim Wright [this message]
2001-03-02 10:22 Tor Arntsen
  -- strict thread matches above, loose matches on Subject: below --
2001-02-27 17:31 Christopher Chimelis
2001-02-27 17:40 ` Zack Brown
2001-02-27 17:17 Zack Brown
2001-02-27 21:20 ` David L. Nicol
2001-02-27 21:32   ` Rik van Riel
2001-02-28 23:06     ` Daniel Ridge
2001-02-28 23:58       ` Albert D. Cahalan
2001-03-01  0:53         ` Dan Hollis
2001-03-01  1:35         ` Daniel Ridge
2001-03-01  2:37       ` zbrown
2001-03-02  0:52       ` Pavel Machek
2001-02-27 21:37   ` Alexander Viro
2001-02-27 21:56   ` Zack Brown
2001-02-27 22:29     ` zbrown
2001-02-27 22:33     ` J . A . Magallon
2001-02-28 17:59   ` Ric Wheeler

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=20010301111302.A1476@kochanski.internal.splhi.com \
    --to=timw@splhi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tor@spacetec.no \
    /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;
as well as URLs for NNTP newsgroup(s).