Linked by Thom Holwerda on Mon 21st Apr 2008 21:45 UTC
Permalink for comment 310904
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-24
Don't be such a slave to fashion. ;-)
Counting lines of kernel code vs userspace code is pointless. If it makes sense for functionality to be in the kernel then it should be in the kernel.
One of the major issues here is central control. There needs to be one entity in charge of setting the vid mode. Otherwise you end up with conflicts that can potentially lock up the machine, or at least the console. And you end up with ugly screen flashes and annoying delays during bootup, shutdown, and vt switching. Plus redundant code in kernel and user space which may have different expectations. The alternative would be to move sysvinit (or upstart) and the Linux text consoles all into X, which would be quite absurd.
The piece of functionality that is going into the kernel is actually quite small, and some or all of it is already implemented in the kernel to allow that cute little Tux logo to display on bootup. Mainly, I believe that an API for existing functionality is just being exported to userspace for use by X or the windowing system of your choice. And the result should be enhanced stability. And enhanced security, too, since the kerel API should cover all of the functionality which has thus far required the X server to run as root, allowing X to run as an unprivileged user.
Edited 2008-04-22 19:31 UTC