Syndicated Linux NewsThis forum is for the discussion of Syndicated Linux News stories.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The HURD was meant to be the true kernel at the heart of the GNU operating system. The promise behind the HURD was revolutionary – a set of daemons on top of a microkernel that was intended to surpass the performance of the monolithic kernels of traditional Unix systems and in doing so, give greater security, freedom and flexibility to the users – but it has yet to come down to earth.
HURD was doomed ever since RMS decided to use the Mach microkernel as a starting point, even he admits it. Just let HURD die, and let us never hear of this failure again. Let HURD never be hurd of again !
The line between them is no longer as distinct, newer kernels can have userspace I/O drivers:
Code:
┌───────────────────────── Userspace I/O drivers ─────────────────────────┐
│ CONFIG_UIO: │
│ │
│ Enable this to allow the userspace driver core code to be │
│ built. This code allows userspace programs easy access to │
│ kernel interrupts and memory locations, allowing some drivers │
│ to be written in userspace. Note that a small kernel driver │
│ is also required for interrupt handling to work properly. │
I agree with H_TeX, why are we even still talking about HURD? If people still want microkernel then see Minix. HURD is just too far behind and deprecated to be worth working on. Let it die already.
Well if movies have taught us anything it's that the undead, although slow and stupid, can still be a force to reckon with.
Especially if you're up against a hurd of them. (sorry brianL, couldn't resist it ).
I've read enough about it to know that it's been some kind of effort for years now and the effort hasn't led anywhere yet, but maybe there's a chance of something being made out of it. It seems pretty likely that I'd end up using Linux or something else anyways, though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.