Linus Torvalds On Linux 2.6
ceebABC writes "Linus Torvalds talks about the upcoming Linux 2.6 kernel, in an interview with eWEEK. Linus discusses the scalability and memory management in the new kernel. They also have a story about what's supposed to be in Linux 3.0."
I am glad the mid level scsi stuff now works correctly with SAN environments but I wish opengfs and or ocfs had made it into the tree before the feature freeze. I guess for now I have to just resort to running a proprietary clustered file system.
Got Code?
It's good to see the focus on issues that effect business servers with heavy load. As a desktop user it's easy to think otherwise, but...
The kernel can support most things a desktop user needs. It's the programs on top that need to be beefed up (and drivers).
As for winning the desktop war (if that interests you) then corporate is the way to start. I see tons of articles on how to get average middle aged user to install linux. It can do everything in the world, but if they don't use it at work, most people won't switch. ("I have to know windows at work, why learn anything else").
The more high power servers people see running free software (and maybe eventually their desktop) at work, the more likely they are to adopt it.
And especially in the realm of *free* software, user base is important.
-T
http://unmoldable.com W:"No one of consequence" I:"I must know" W:"Get used to disappointment"
Why isn't Sistina's LVM making it into the kernel? SUSE has been including it as standard in their distribution for some time.
I don't track the LKML at all. I'm curious why XFS made it in, but LVM did not.
Amen.
I read the eWeek article about 2.6 and have surfed through the lkml to see what's going in and what's not.
I see Hans Reiser making an impassioned plea to get ReiserFS 4.0 into 2.5, the EVMS team nobly accepting temporary exile in userland, and others griping that LVM won't be in 2.6 and have to wait until 3.0
Given stuff that won't be in 2.6 and will be deferred until 3.0, what I want to know is:
"Provided by the management for your protection."
No, there's plenty more to do. As a very simple example, the driver organization is still very much in flux; devfs is under fire, and alternates are springing up.
On a higher level, the way we handle multiple processors could very well entirely change (if Larry McVoy has his way, and I think he's right). The result might be a kernel which runs very well on a single processor, but is perfectly scalable to thousands of processors.
-Billy