Slashdot Mirror
The 2.7 Kernel: Back To The Future For Linux
Anonymous Coward writes "Now that the Linux 2.6 kernel has been released and is being worked into distributions, many in the open-source community are turning their attention to the next development and test kernel, known as the 2.7 tree. To get an early glimpse at some of the thinking going into the next kernel, key vendors that aid in shaping the Linux kernel helped eWEEK last week put together a long-range wish list for 2.7."
After a frustrating weekend trying to get a High Point SATA card working in my Linux server, I'm putting better SATA support on the top my my wish list!
"We have nothing in common, your attitude annoys me, and your political views are appalling."
With so many people with their own agendas pushing and pulling at the kernel, and Linus being the steadfast leader he is, I can't help but think Linux may be headed for a fork in the not so distant future. Unless there is a way to make the kernel truly enterprise class as well as a responsive, low latency desktop system and a near real time embedded platform all at the same time.
I'm amazed (in the good way) the kernel devs have made it as versatile as they have to this point. Hats off to them and here's to hoping they can keep it up.
"Watch your cornhole, bud."
That was quoted from an Oracle Exec. let's not get ahead of ourselves. I'm not sure how 2.6 is considered a "server" release. The Kernel is the kernel. 2.6 will be the default kernel on desktop installs in a few months I'm sure.
A lot of the patches in 2.6 benefit both the server and desktop camps equally. The scheduler and VM improvments and XFS. I believe RedHat backports those patches to the 2.4 kernel for the ES/AS/WS versions.
If you haven't tried 2.6 yet, you really should. I noticed a considerable increase in X response time with it.
I would like to see less things in the 2.7 kernel than in the 2.6 kernel. Getting device drivers, network drivers, etc, out of the kernel core and into modules was a step forward, but I think the next step forward would be to get these things out of the kernel entirely, and into userland. That would give Linux a huge advantage over Microsoft Windows. Installing and un-installing device drivers would become much easier for users. Manufacturers would like this too because then there would be less concern about GPL and device drivers. It would be easier to release binary-only drivers.
how is it possible to change a user on x without logging out?!
There are many ways, depending on exactly what you want to accomplish. I suspect the one you're talking about is "Start New Session" -- on KDE 3.2*, just click the "K" menu and pick "Start New Session".
Using that plus vnc you can even make your X session relocatable -- again supported in point-and-click fashion out of the box by KDE 3.2 (called Desktop sharing). Wife is using the computer in the den? Just pull up your still-running desktop on the machine in the kitchen. Do that with XP!
The coolest way, though, is this one. This guy dropped two video cards into his machine, hooked up two keyboards and mice and set things up so that both he and his girlfriend could use the machine at the same time. Granted, this isn't something that can be done out of the box (it requires running two different X servers, one patched), but it's a very cool hack.
* I'm sure GNOME has similar features, since KDE isn't actually doing any of the multi-session heavy lifting, that's part of XFree86. KDE just puts a pretty interface on it.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.