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."
The article was ok and all, but where is the list of long awaited features???
There is nothing specific about anything. What a useless article. You can say you want a milkshake with your 2.7 kernel and it be just as valid as the things mentioned.
Is just great driver compatability. That seems like the primary hurdle that can really keep people out, as well as a large area that is easily neglected in a more server-oriented mindset (especially in terms of user peripherals).
Built in OpenMosix in the kernel would sound nice, at least it would keep Oracle happy with its push for Grid Computing. Better desktop support would also be great... they can start by making it easy for Linux to autodetect a USB joystick controller!
READY.
PRINT ""+-0
--
No bits were harmed during the production of this mail
That article was amazingly content-free.
I don't see why the two are necessarily contradictory. After all, the bits to support enterprise class hardware can easily be omitted from compiling an embedded or desktop platform: if they can make a kernel with modular scheduler and tunable latency (which was the way it seemed to be heading with Con Kolivas' patch set) then the enterprise boys can increase the latency for minimum kernel CPU usage, the desktop people can knock it down for good responsiveness and the embedded folks can plug in an alternative scheduler to suit their own particular needs.
"'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
- JRR Tolkien.
Centralization breaks the internet.
They mentioned the word in passing, but I think for the kernel to provide this will be a huge benefit on many levels - and immediate benefits could be seen in projects like udev and the HAL stuff that is going on.
Besides, machines are getting to resemble the big iron of yesterday enough that you can (and a large number of people do) run multiple OS's on a single machine. Having an underlying architecture to better support those goals would be a great thing.
To a certain degree, it is like the evolution from a shared memory space to a virtual memory space - one of the greatest features was protection. Virtualize the entire OS (wow!) and you can run your different server apps on the same machine without the risks of one nuking the other.
Emulation has a ton of cool things going on right now. With a swift boost from an OS designed to virtualize the hardware it would make it trivial to have multiple copies of the OS running at very near full speed with complete access to the hardware.
Even if you are using a vendor kernel it doesn't matter because everything is modular, only modules for things you're using are loaded.
Which brings up a good point for the 2.7 kernel. You might have better SATA support if they would actually freeze a kernel driver api.
:)
How about we stop politicizing the kernel and actualy make a stable Driver API? One that doesn't change with every point release of the kernel?
I know that people want open source drivers but it's extremely hypocritical to complain about companies lack of support for linux then do absoultey *nothing* to help them out by changing the api every point release. Listen, besides some fanatics nobody cares about open source drivers. People would rather their stuff just work.
I understand that, fundamentally, open source drivers are technically a better solution but there is no chance in hell of convincing Nvidia or any other company that has substantial IP and reserach in their drivers of publishing them open source. Same thing with Intel's Centrino drivers.
Make a stable api darnit!
Installing and un-installing device drivers would become much easier for users.
Is insmod so difficult?
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.
Since when did we care? Linus has flat out said he doesn't like binary drivers, for pretty good reasons, I think (harder to debug being the main one). Why encourage this?
So, any other good reasons why you'd want userland drivers? Are those reasons good enough to offset the additional overhead that this would incur (additional context switching,etc)? The new layers of indirection that would have to be added?
Frankly, I think you might have been bitten by the microkernel bug. But, sorry, Linux ain't no microkernel. And, so far, it hasn't needed to be. So, why start now?
It may not be true any longer, but some things work better when copiled into the kernel image itself. I think network cards fall into this catagory.
I believe they mean something like this.
In a setup like this you have one big machine running lots of copies of Linux or some other operating system with each in its own virtual machine. To manage all of this you have z/VM running on top. If I understand correctly, what they are talking about is being able to have Linux serve z/VM's role.
Of course, at least half (possibly all) of this goes way over my head since I'm just a math guy who likes to fool around with computers sometimes.
My only political goal is to see to it that no political party achieves its goals.
Unfortunately the truly malicious are seldom stupid.
KISS: keep it simple stupid...
/app/PROGRAM NAME /user/USERNAME /sys/
/app/ with their own sub directory like /app/apache/ .. /user/ subfolder, which would contain a user root directory(like the partitions root directory, but limited to the user... /user/NAME/ sys, doc, app, pub, etc... /sys/ would have standard libraries and other kernel and core system stuff.
macos class(1-9 had a nice directory system, and i think it could be carried over in its simplicity to unix boxen)
/
99% of programs would install to
a user would have a
programs, system, documents. 3 basic categories... with a multi user system, you make documents become the user listing, and you have programs, system, userfiles
3 directories, thats it.
Frankly, that's like saying that we should eradicate every single disease on Earth.
:)
Kernel hackers are human, surprisingly. No kernel is perfect, look at even OpenBSD
Although due to their very strict emphasis on security they haven't had many root exploits in the past. Linux doesn't follow that philosophy too carefully.
"With a new Mozilla released, is the browser war back?
I'm sticking with Internet Explorer
I'm giving Mozilla a second chance
The browser war?"
What a dumb poll, what a dumb site. What should I choose if I am NOT using IE at all?
Maybe there are better sites to put articles about Linux Kernel than that one?