Skip to contentSkip to conversation

Will Mosix go into the standard kernel?

DISCUSSION Tor Arntsen 2 participants 2 messages Mar 1, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Daniel Ridge <[email protected]> writes:
[...]

Quoted 2 lines

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. It's *bad* that those vendors deliver hacked kernels. It's not something that should be recommended as a *goal*!
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.

-Tor

#2 lore raw
In reply to a message not in the archive
Quoted 8 lines · Tor Arntsen

Daniel Ridge <[email protected]> writes:
[...]

Quoted 2 lines

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.

Quoted 2 lines

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.

Quoted 4 lines

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

Signature · 4 lines
Tim Wright - [email protected] or [email protected] or [email protected]
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