Slashdot Mirror

← Back to Stories (view on slashdot.org)

GNU Hurd Begins Supporting Sound, Still Working On 64-bit & USB Support (phoronix.com)

Posted by ryuzaki0 on from the pretty-soon-big-and-fancy-like-gnu dept.

An anonymous reader writes: GNU developer Samuel Thibault presented at this weekend's FOSDEM conference about the current state of GNU Hurd. He shared that over the past year they've started working on experimental sound support as their big new feature. They also have x86 64-bit support to the point that the kernel can boot, but not much beyond that stage yet. USB and other functionality remains a work-in-progress. Those curious about this GNU kernel project can find more details via the presentation media.

2 of 312 comments (clear)

  1. Re:What's the point by dissy · · Score: 5, Insightful

    What's the point of continuing with Hurd?

    For the same reason anyone does something they enjoy for fun and recreation, namely so we don't become hollow and joyless, reserved to asking on forums why other people do things they enjoy :P

    I note you both read slashdot and posted to slashdot today, as well as aren't out working to do something "useful".

    Don't you think it a tad off to spend your free time doing things you enjoy at the same time as questioning other people doing the same?

  2. Re:What's the point by ooloorie · · Score: 4, Insightful

    Thanks to the microkernel architecture you will no longer have to reboot system just to get rid of that stale lock on an accidentally removed USB disk or unmountable

    There is an implicit false dichotomy there, namely "ancient design monolithic kernel" and "ancient-style microkernel". There are many other choices.

    I could transparently restart crashed ntfs.sys emulated under Linux in 2003 while Linux kernel still can't do that with its native filesystems.

    Actually, since NTFS under Linux runs in user space, yes you can. In fact, for many kernel services (USB, file systems, networking, etc.), the kernel can call upon separate servers to handle those services. And that's another problem with microkernels: their design focuses not on what users need and the question of how to best provide that, but rather on a mechanism.