Please create an account to participate in the Slashdot moderation system


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Moving the Linux Kernel Console To User-Space 311

Posted by Soulskill
from the cuddly-console-seeks-loving-home dept.
jones_supa sends this quote from Phoronix: "David Herrmann has provided an update on his ambitious initiative to kill off the Linux kernel console. Herrmann has long been working on making the Linux kernel CONFIG_VT option unnecessary for providing a Linux console by punting it off to user-space. The Linux kernel VT console hasn't been changed much in the past two decades and Herrmann is hoping to see it replaced with a user-space solution he's been developing that would allow for multi-seat support, a hardware-accelerated console, full internalization, and other features."
This discussion has been archived. No new comments can be posted.

Moving the Linux Kernel Console To User-Space

Comments Filter:
  • by PRMan (959735) on Friday February 08, 2013 @12:10PM (#42833021)
    Seriously. What's with this new generation that has to force their way or the highway on the world? Every new piece of software that comes out forces you to do things you don't want. Now they're trying to turn Linux into Windows 8.
  • Re:why? (Score:4, Interesting)

    by tibit (1762298) on Friday February 08, 2013 @03:37PM (#42835997)

    What's wrong with it being in the userspace? At least if it crashes, it doesn't bring the whole kernel down. The process is relaunched by the kernel, and off you go. It's the Erlang mantra of reliable software: fail fast, in limited scope. I love it. That's why I'm a big fan of userspace drivers for all devices that are application-specific. Suppose you have a USB-based toy that has a vendor-specific functionality and isn't one of the standard USB device classes. You have an application for. It should only have a userspace driver bundled with the application. You start the app, it claims any USB devices it can handle, and goes from there. That's often how it's done on OS X, it's quite onpopular on Windows, unfortunately.

Real Users find the one combination of bizarre input values that shuts down the system for days.