GNU/Hurd Gets POSIX Threads
An anonymous reader writes "Neal Walfield announced the first release of RMGPT, which is (or rather, aspires to one day be) a complete, portable implementation of IEEE Std 1003.1-2001 threads also known as POSIX threads. With this new pthreads library, it will soon be possible to run complex software packages on the Hurd, including the GNOME and KDE desktops, the OpenOffice suite, and the Mozilla web browser. Find more information here, including the humorous meaning behind RMGPT, and insight into a future Hurd release..."
But, I don't see the point. In the beginning Hurd made sense but, it floundered for so long that it has been eclipsed by Linux and the BSDs.
Without being insulting, I'd just like to ask, what's the point of putting further effort into the Hurd, rather than concentrating on advancing Linux and or the BSDs?
ok but it had to be said....who the hell uses the hurd?
"Quoting famous computer scientists out of context is the root of all evil (or at least most of it) in programming." - K
Is it just me or does the GNU/HURD icon bear a startling resemblance to South Park's Mr. Hanky?
yea i stole your sig- whats the big deal, it sucked anyway.
Ten years later and HURD still isn't practical (what's the big deal I wonder) while Linux can drive anything from palm devices to super computers and mainframes.
It's no wonder RMS is so bitter and twisted these days
Development is meant to be fun and Linus clearly put that and pragmatism ahead of the stupid pigheaded politics that the FSF (& RMS) is associated with.
Yeah, and he had to write his own C compiler, C library, assembler, linker and text editor to do it, didn't he?
You see, the only way for non-Windows to beat Windows is for every single person to create their own operating system with slightly different interpretations of the standards. Once this low-level heterogeneity exists, software companies will need to create slightly different versions of each of their products to sell to us (or we could each create our own IRC client, calendar app, webmail frontend, etc). This virtually guarantees our freedom as well as making us immune to virii and girlfriends.
Since Hurd is a GNU package then it should not be GNU/Hurd. Instead we should use GNU Hurd. Since Linux is not a GNU package then it is referred to as GNU/Linux. For more details see the FAQ.
JOhn
Campaign for Liberty
Hi!
Please try to be constructive. It is inevitable that the site become slashdotted as you call it, as more and more people become aware of our project and wish to become involved. It can only be a matter of time before GNU/Linux is abandoned for an operating system that is truly Free.
Cheers,
GNU/Wolfgang
You aren't the first to think that was odd. I've been interested in that question myself for awhile. I'm no authority, but I'll pass on what I've learned. First Matthias' post is fairly accurate with one major exception. He wrote:
Right so far, although I'm sure that Linus, among others, disagrees with the notion that you can't do even nicer design in a monolithic kernel if you pay attention.
BTW, what Apple has done with Mach is basically the same way MS went with NT (yes I know this week they call it XP, but I don't feel any obligation to obey the dictates of their marketing department so I'll keep calling it NT thanks,) starting with a microkernel but then moving certain systems back into kernelspace for performance reasons.
Here's where I think he's wrong. What he's describing here is how it works in Darwin (and NT) yes, but only because they moved those systems back into kernel space. But the way it works on a proper microkernel system (like the HURD) doesn't just run these things in a separate address space but at a different privilege level, so instead of crashing the kernel you simply crash a daemon and have to restart it. This does mean drawing the lines a little differently than they have, of course.
You wrote:
OK, my best guess is that it's simply a historical relic. When Jobs started work on NeXT, it was damn near universal opinion in CS that Microkernels were the way to go, so that's the way he had it done. NeXT, of course, went bankrupt, and was bought at fire-sale prices by Apple, which has now reworked that system into OS X. At no point along the way did it seem clear to the development team that there was any compelling reason to build a new core - the performance problems are minimised by violating the 'microkernel ethic' and moving the personality into kernel space, without actually rewriting the kernel from scratch. So there you go... probably not the way they would write the thing if they had to start over from scratch, but they don't, and it's good enough. Software development is like organic evolution in that way, even though people usually misquote 'survival of the fittest' what Darwin (as in Charles Darwin) actually said was 'survivor of the fit' - it doesn't matter if something's optimal, as long as it's good enough.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Friends don't let friends enable ecmascript.