http://www.nuxified.org/article/fork_a_kernel_kill_an_os_and_revolutionize_the_desktop
http://cogscanthink.blogsome.com/2005/12/20/split-the-kernel-up/
The Linux kernel has long been designed for server use, with few design implementatioins geared towards desktop users; kernel developers barely communicate with desktop users and continue to design the kernel for server use. Should we fork the kernel? I believe this to be unnecessary; the Linux community is flexible enough to change it's direction and start voicing it's desire for a kernel optimized for everyday technology. What do you think?
-
No... who said there's "few design implementatioins geared towards desktop users"? Take a look at the changelogs of recent kernels... plenty of wireless stuff for one.
What is the difference between desktop and server anyways? Are there even any 'would-be' features in KDE/GNOME that can't be done because of the kernel? All that's needed is a stable kernel to run on, they take care of the rest themselves. -
It's more an issue of performance, with various schedulers. The IO scheduler has improved greatly with the pluggable architecture, but CPU scheduling can be improved greatly. What we really need is someone to take up -ck now that Con Kolivas has retired from kernel development.
Should the Linux kernel be forked?
Discussion in 'Linux Compatibility and Software' started by Bog, Jul 26, 2007.