
New GNU Hurd Kernel Released 419
Anonymous Coward writes "I don't know if there is much interest out there, but GNU Mach Kernel 1.3 was just released a couple days ago. (May 28)." Looking forward to that 2002 release...
If a 6600 used paper tape instead of core memory, it would use up tape at about 30 miles/second. -- Grishman, Assembly Language Programming
Get it right (Score:5, Funny)
Re:Get it right (Score:2, Funny)
Well, since GNU is already recursive, obviously it should be used recursively as well. You should probably add a "GNU/" for each compile since it was compiled with gcc. So by now it's (\Pi_0^{\infty} GNU/)Hurd, that's GNU/GNU/GNU/GNU/[...]/GNU/Hurd...
Of course, you can probably run a (or any number of) virtual hurd(s) on a hurd system, so it would be GNU/GNU/[...]/GNU/GNU/Hurd/Hurd/[...]/Hurd/Hurd.
Oh, and microkernels seem to be out of fashion again...but who really cares about technical details when we can poke fun at RMS instead!
Re:Get it right (Score:2)
Re:Get it right (Score:4, Interesting)
Re:Get it right (Score:2, Funny)
[GNU/]+GNU HURD[/HURD]*
Which is your favorite: additive or multiplicative closure?
Re:Get it right (Score:2)
Re:Get it right (Score:5, Funny)
Ok, I'm dumb. So reply me ^_~
Re:Get it right (Score:5, Funny)
My math skills are far from what they used to be, but something divided by the same thing becomes one. Hence Gnu/Gnu = 1, so it should be 1 Hurd. And who cares about that 1 anyways? So it's should be Hurd.
But if there's only 1, it's hardly a Hurd. It's probably just one Bison. But GNU bison has been around forever, so why is any of this news?
-Rob
Re:Get it right (Score:2)
sPh
Re:Get it right (Score:2, Funny)
True, but as far as I can tell from the posts, Hurd=0.
No GNUs is good GNUs.
This doesn't mean (Score:2, Funny)
Question... (Score:3, Interesting)
Re:Question... (Score:3, Informative)
I'm going going to use any kernel that... (Score:2, Troll)
Quote:
28 May 2002
We are pleased to announce version 1.3 of the GNU distribution of the Mach kernel, featuring advanced boot script support, support for large disks (>= 10GB) and an improved console.
Re:I'm going going to use any kernel that... (Score:4, Insightful)
Re:I'm going going to use any kernel that... (Score:3, Insightful)
Mac OS X (and Darwin) is based on a Mach derivative, and it has always supported large hard disks. It also supports booting off a network or a firewire- or USB-attached hard disk. If GNU's Mach microkernel can't do these things, it leads me to question the viability of GNU Mach (and I don't know if GNU Mach can do these things - it very well might, but I'm willing to bet karma that it can't).
Re:I'm going going to use any kernel that... (Score:2)
Right, I realized this upon further thought after I posted. As for the fool who claimed that I was deliberately spreading FUD: fuck off. I was just trying to figure out what the hell's wrong with GNU Mach/HURD. There have to be some technical reasons (not just political reasons) why this project has been around so long and is only now available as an alpha distribution.
Still, I have to question GNU Mach - the newer versions are going to use OSKit. OSKit is basically a collection of various drivers for PCs. Now I've messed with OSKit superficially for my own little kernel project, and my impression was that OSKit was meant for two groups: (1) students in an OS class or hobbyists playing around with writing an OS (that would be me), and (2) researchers who want to do, for instance, work on VM or scheduling algorithms. Both groups who don't want to deal with the details of peculiar hardware. Anyway, my impression was that OSKit is meant more for experimentation, not a production-level Unix-like kernel. OSKit was very nice, don't get me wrong (nice APIs, you can plug in the drivers into your own kernel fairly easily, as opposed to Linux device drivers, which you have to rewrite from scratch if you want to use them outside of Linux) - but I just don't think it's the right thing for an honest-to-God production system.
Re:I'm going going to use any kernel that... (Score:3, Insightful)
Yes, I've also been to one of his speeches (his speech was kind of boring - it basically rehashed all of the information available on the GNU/FSF websites and I was quite disappointed) and I heard the same story. I don't buy it. Apple managed to debug a multi-threaded multi-processor microkernel-based system. Granted, Apple has the resources to pay a small group of highly-skilled engineers to concentrate on a project, whereas the distributed development model common in most Free/OSS projects may not be well-suited for kernel work. OTOH, Linux employs a very open development model, and the FSF's own projects (like emacs and gcc) generally use very closed development models (eg, you have to be on a certain mailing list to get access to emacs betas - no public CVS). So you see, these arguments can't really explain HURD's problems, so that's why I'm confused.
Linux is pretty much based on "stuff that works"
I think this is closer to the real reason. I think HURD may have a bit of the "Ivory Tower" problem. I recently saw on a HURD mailing list a problem someone was having porting over some network program to HURD. HURD puts no limits on the size of strings returned by the gethost* functions, whereas every other Unix system has a well-specified limit on the length of domain names. This makes it difficult to pre-allocate a buffer for a hostname, which in turn, makes network programming in C more difficult (and I'll pre-emptively tell you HLL folks to bugger off because C is still the de-facto language for network programming). The HURD folks came up with some riduculous artificial example of a hostname that breaks under BIND/glibc/Linux.
Whenever I'm writing some program, I have to make certain decisions. For instance, I have to decide what to abstract into a module and what to hard-code in. If you don't abstract anything, you'll end up with spaghetti code, but if you try to abstract everything, you'll end up nowhere. At one point, you have to sit down and tell yourself "now, you write the code that accomplishes your goal."
Anyway, I'll probably be sticking to Linux and FreeBSD for quite a while. I'd like it if DevFS were more accepted, if user-level filesystems became a standard part of Linux and if capabilities were made useful under Linux, but as it is right now, Linux and FreeBSD are actually usable operating systems, which is something I'm not sure I can say about HURD.
It is Open Firmware. (Score:4, Interesting)
Having the MacOS X kernel perform this task is not only idiotic but impossible, if the OSX kernel is loaded, the machine has already selected a boot disk...
Re:I'm going going to use any kernel that... (Score:3, Informative)
It seems some people thought I was a troll and modded down my original post, while leaving your written diarrhea un-moderated, so I feel obliged to respond. Normally, I don't give you ACs a chance to say "YHBT", but I'll make an exception for Your Emminence.
OS X is indeed based on a mach microkernel. Not the GNU Mach microkernel, but a mach microkernel derivative (Mach was more-or-less a "proof-of-concept" of the microkernel idea written at CMU and GNU mach was written 'cause the MIT boys decided to have a pissing contest with the CMU boys). Have you ever used OS X? No? Well, then perhaps you'll see this when you do in fact use OS X for the first time:
Granted, 2.7 megabytes isn't very "micro" but a microkernel has nothing to do with the size of the kernel binary, and everything to do with the ways the kernel components communicate with each other.
OS X is a port of some of the FreeBSD userland into Apple's mach-based environment. I don't know if they used any of the FreeBSD kernel code, but most everything in the userland (that is, the userland I care about which is the Unix subsystem) is a straight port of the FreeBSD stuff. Even the manpages still have the FreeBSD emblems on them.
So, yes, it is in fact possible to write a successful microkernel-based system. NT is (or, at least, the NT kernel ideas were) microkernel-based, and Apple's OS X is microkernel based. If you think you can simply port over a FreeBSD driver to OS X, you're sorely mistaken.
Re:I'm going going to use any kernel that... (Score:3, Interesting)
Sheesh, and they're on version 1.3? It just looks a little suspect to me when the size difference between version 1.1.3 and 1.2 is over a megabyte of compressed code.
What's that about commercial software being rushed out the door incomplete?
Re:I'm going going to use any kernel that... (Score:2)
1.3 is just a number, a stake in the ground. The idea that 1.0 is the first stable release is a marketeerism, and I'm sure the Hurd kids don't have a bunch of MBAs on their back trying to help decide what the most strategic release number is.
Um, it's a sort of de facto standard that the version 1.0 release of any software (open source, public domain, or commecial) is assumed to be stable and ready for production use. I know that's not the case for a LOT of stuff out there, but that is the expected scenario. The GNU team are of course free to number their versions however they want, but if they're still working on getting basic features into the kernel and naming it 1.3 at the same time, then from my perspective, they are trying to mislead people on the actual status of the code.
If you think Hurd is rushed, you should put down the crackpipe.
Yeah, I'm afraid you're right. That was a really bad way to put it.
I seriously want to try out and play around with Hurd, but the last time I checked, the required hardware didn't even remotely match anything I have laying around.
excellent (Score:3, Funny)
For those still using legacy systems, a little background: the GNU Hurd is the official GNU microkernel. Because it's smaller than Linux, you get faster I/O at the cost of greater instability, a tradeoff most sysadmins are quick to take.
I've used it in a production-level enterprise environment, at home on the desktop, and even on my palmtop. Even my grandmother can do the base install. This is truly the wave of the future.
Clues for the clueless (Score:3, Insightful)
entire server farm from a Linux/BSD/Windows ME
even on my palmtop
faster I/O at the cost of greater instability, a tradeoff most sysadmins are quick to take.
Even my grandmother can do the base install.
Re:excellent (Score:2)
Re:excellent (Score:2)
Trust me if you're looking for a pay rise you want the servers to die at around midnight; then rush in and fix them.
Works every time ... ;)
Also let it be known... (Score:3, Funny)
But seriously, I've tried the Hurd, and while I can appreciate the work that's being done on it and its goals and aims, it's just not stable enough for everyday use. I'll just stick to 2.2.16 for the time being until I am convinced that there is a more stable kernel or until the Hurd matures a bit more.
Re:Also let it be known... (Score:2, Insightful)
Re:Also let it be known... (Score:2)
graspee
Compared to OS X (Score:2, Troll)
How does this compare to the Darwin Mach kernel?
Bitte können sie den Mach kernel OpenSource machen (Score:2, Funny)
I can see this being used in embedded banking systems that process mortgage planning calculations. That's the way of the future!
Hurd: Still not ready after 10 years! (Score:3, Informative)
Re:Hurd: Still not ready after 10 years! (Score:3, Interesting)
The issue here is that they aren't just making another version of a monolithic Uni*xy kernel, they are re-inventing much of the way the applications/kernel/u-kernel/hardware layers interact. It's not as easy a task as reverse engineering what already exists.
Re:Hurd: Still not ready after 10 years! (Score:3, Informative)
Agreed. Also, free software devlopers have a right to think that Steve J. Milloy is an twit whose contribution to free software is less than zero.
to have HURD after 8-10 years of development to be nothing more than a crash test dummy kernel is worth a ton of scorn.
You can thank Linux for that. After Linux came out the GNU project devoted most of their effort to improving the userland tools: GCC, EMACS, the shell utilities (sh, awk, ls, md5sum, etc.), and so on. In addition, they made the HURD a much more ambitous effort than it was. Basically, the GNU project felt it was better to get something out that was right than to release something quickly; people could use Linux in the mean time.
Maybe if RMS would get off his moral hobby horse and spent that time putting down code
OK, Steve, not only are you someone who acts like a twit, you are an ignornat twit to boot.
Go back to critizing idiotic junk science. Yes, that is an elitest thing to do also, but at least it is a useful elitist thing to do.
Finally, I do enjoy your junkscience site. Putting effort in to working on that instead of flaming free software devlopers sounds like a lot more useful way to spend time.
- Sam
Re:Hurd: Still not ready after 10 years! (Score:2)
are you sure this is a requirement for a modern OS?
The real question is (Score:4, Funny)
Re:Naming, co-operation and tight-asses (Score:2)
That actually sounds good!
Re:Naming, co-operation and tight-asses (Score:2)
What do you get when you combine Tux & Hurd? Makes for an interesting mascot, anyway.
Re:Naming, co-operation and tight-asses (Score:2)
Re:Naming, co-operation and tight-asses (Score:2, Troll)
He loves me, and I love GNU.
Hurd makes a fun toy OS (Score:4, Interesting)
Even more fun is rolling your own OSKit-Mach microkernel and then running it on a serial debugger. It is fascinating to be able to single step through a running kernel, set breakpoints, view the source as it executes, look at the CPU registers, etc. I wholeheartedly recommend it to all the compsci students and future kernel hackers out there.
finally! (Score:5, Funny)
Support for the terminal speeds B57600 and B115200 has been added.
Now I can use my new 56k modem! Pretty soon, every ISP will be using this fast new speed of modem, it will be cool! Gopher's gonna FLY on this baby!
Okay just kidding, glad to see HURD is still alive. I remember first reading about it long ago and thinking, hey, finally a modern OS. But here I am still using a monolithic kernel after all these years, and it works just fine. Good luck to the HURD folks, maybe my kids will use it. :-)
Helpful info (I hope) (Score:5, Informative)
As mentioned before, this version of Mach is about to be dropped in favor of OSKit-Mach. I don't know what the H4 CD's have (I haven't installed 'em yet) but the H3's didn't use OSKit-Mach. OSKit Mach has all the drivers that Linux 2.2 has, which is better than Mach 1.3, which iirc only has Linux 2.0's drivers.
In my brief experience with the HURD (you can only have so much fun without network card drivers) I liked it even more than Linux - using servers instead of using the kernel itself makes it more logical to, say, integrate an FTP directory into your filesystem (and indeed, this server has already been set up). settrans is lots of fun.
It's got X. It has pretty much everything you need - I could convert to the Hurd and barely lose productivity. What it's missing mostly are drivers (though OSKit should help with that, I haven't tried it).
Anyway, if you have a weekend to kill, it's a lot of fun.
Linus on the HURD (not whoring) (Score:5, Funny)
Which is a completely idiotic idea, and which is only just another example
of how absolutely and stunningly _stupid_ Hurd is.
Later on...
Trust me. The people who came up with MAP_COPY were stupid. Really. It's
an idiotic concept, and it's not worth implementing.
And this all for what is a administration bug in the first place.
In short: just say NO TO DRUGS, and maybe you won't end up like the Hurd
people.
All by Linus found here lkml [216.239.33.100]
Can RMS be taken seriously? (Score:2, Insightful)
But I guess when you release a kernel that has 8 years of development and it can barely keep a machine running, you are a joke. I am sure Bill Gates is laughing his ass off.
Re:Can RMS be taken seriously? (Score:5, Insightful)
The slash crowd seems to be a bunch of "technical" guys who can't get beyond personalities.
Hey guys, written any good C compilers lately? Come up with any revolutionary social institutions, like the GPL?
On those two grounds alone, you would think that RMS would be revered at least as much as Linus Torvalds, but no... "RMS, he's that nasty guy with a beard who keeps talking about politics. Let's go get him."
Re:Can RMS be taken seriously? (Score:2, Insightful)
But he hasn't done anything except rest on his laurels for a long time now. Perhaps if he stopped scheduling/cancelling talks and getting involved in petty naming disputes, and sat down and actually _wrote some code_ for Hurd, he'd regain some of the respect that most of us have lost for him (perhaps this is why Torvalds is still respected?).
Anyway, I don't think anyone cares about his facial hair or hygiene. I don't think anyone would disrespect him for his advocacy of Free software (no matter how much they may disagree with him). However, his 'GNU/Linux v Linux' crusade is petty and ego driven and is worthy of contempt.
Re:Can RMS be taken seriously? (Score:2)
Then why do the BSD people still use it? It seems instead of being dependent on the GNU project for the compiler, they would have written their own. Or maybe a good optimizing, multi-architecture compiler is a non-trivial thing to write, eh?
Re:Can RMS be taken seriously? (Score:3, Insightful)
There's a certain kind of person who always seems to be putting down activists as just being merely out for ego gratification. What other motive could they possibly have, eh? No one could possibly care about that idealistic stuff, right?
A suggestion: If you think the "GNU/Linux" thing is trivial, symbolic bullshit, then just ignore it. If it's so trivial, what's the point of bringing it up over and over again?
Re:Can RMS be taken seriously? (Score:3, Insightful)
Re:Can RMS be taken seriously? (Score:2)
Sadly, this seems to be true. I'm not sure why; I've never had the sense that he deserves it, and no one's ever been able to explain to me why they think he does.
You've never written a stable kernel, I'll wager. Are you a joke? Or, to put it another way:
"It is not the critic who counts, not the man who points our how the strong man stumbles or where the doer of deeds could have done them better. The credit belongs to the people who are actually in the arena, who's faces are marred by dust and sweat and blood, who strive valiantly, who errs and come up short again and again because there is no effort without error and shortcomings, who know the great devotion, who spend themselves in a worthy cause, who at the best knows in the end the high achievement of triumphant who at worst, if they fail while daring greatly, know their place shall never be with those timid and cold souls who know neither victory nor defeat." -Teddy Roosevelt
Wake me when HURD runs on top of L4 (Score:5, Interesting)
MACH is an old and flawed u-kernel implementation. Until HURD ports itself to a better one, HURD will always be slower than Linux and a more bug ridden OS. u-kernel OS implementations have proven to work with products like QNX, but HURD can only embarrass u-kernel advocates with its current foundation.
Its more annoying when advocates bitch and moan that "Linux is a 40 yr old design". So is about everything that is sucessful on the market. Do these guys really expects us to drop what works to what cannot work well in its current state? As is, HURD is an embarrassment to O/S purists. Its the "portable" O/S that can't even work well on ONE hardware architecture!
Its sad that HURD lacks interested, talented programmers, but its strategic stewardship is its downfall. Or the difference between a Torvalds and an RMS. I don't think HURD announcements deserve to be put on the front page of
Re:Wake me when HURD runs on top of L4 (Score:4, Insightful)
You're a glass-is-half-empty kind of person, aren't you? Here's how it looks from my perspective: HURD runs equally well on many architectures!
MACH is an old and flawed u-kernel implementation? (Score:3, Insightful)
I always thought MACH was THE microkernel. Either elaborate and convince me, or put down the crack pipe
Re:MACH is an old and flawed u-kernel implementati (Score:2)
NeXTStep, OpenStep, MacOS X run on a u-kernel based on MACH. They do not run on the publicly available MACH kernel. And if you haven't noticed, OS X hardly runs like greased lightning either (except to a Mac evangelist).
Re:MACH is an old and flawed u-kernel implementati (Score:2)
Re:Wake me when HURD runs on top of L4 (Score:2)
Let me bum you out some more. Check out the L4 [tu-dresden.de] pages on implementations.
There are 2-4 implementations of L4 that are geared towards the x86 family. The assembler one is implemented by someone who appears to have lost interest in it. The other implementations are in C++!
I can't find it anymore, but there was a page buried there that mentioned that L4 requiring some redesign to better support SMP (I think). I'm guessing part of the reason why HURD doesn't flat out switch to L4 is that L4's interface is still a moving target.
Exactly (Score:3, Informative)
The latest "Hazelnut" L4 kernel (written in C++) finally passed the fastest L4 x86 assembly kernel for interprocess communication performance. This is very important for microkernel performance, since many things traditionally handled by system calls (setting some registers then trapping an interupt in the kernel) are instead handled via IPC with user-space drivers. I'd like to point out that without some crazy high-level macros in your compiler, it still seems like you need a minimum of about 32k of your ring 0 code is written in assembly (on x86) to properly manipulate the hardware. (You could come up with some funky architecture where not all of your ring 0 code is in what you call the kernel. Doesn't NT/2K/XP have some non-bootstrapping ring 0 code outside of kernel32.dll?) (This is from what I remember of L4 and QNX documentation.)
Have no fear, the X.2 API is bein sorted out. People are holding off on porting the HURD to L4 until the L4 X.2 API is finalized. My guess is that porting will begin this Summer.
Re:Exactly (Score:2)
Have no fear, the X.2 API is bein sorted out. People are holding off on porting the HURD to L4 until the L4 X.2 API is finalized. My guess is that porting will begin this Summer.
That is wonderful news! I was under the impression L4 had languished or had been abandoned. (Don't understand the continued MACH development, unless they don't think L4 will be ready for a while.) Wow, this almost makes Hurd viable. We could see a good implementation of Hurd in two years.
As for the u-kernel being written in C++, the comment I made was more of a *wow*, rather than an indictment of L4. In the right hands, C++ can be just as space and performance efficient as C. From a pure performance standpoint, you'd rather have the u-kernel in assembler. But if the performance hit in C++ is as low as 15% compared to an assembler version, I'd have to say it would be well worth it. The IPC/SMP abstractions are such that it would be much more clearly expressed in C++ than assembler. And like you said, routines can always be re-coded in assembler if needed.
But seriously, folks... (Score:2)
What gets me... (Score:4, Insightful)
Back in 94 I started using Linux because the HURD wasn't ready. The HURD still isn't ready. That's OK, things take time. But what's not OK is for RMS to write [linuxworld.com]:
If you can ignore the facts and believe that Linus Torvalds developed the whole system starting in 1991, or if you can ignore your ordinary principles of fairness and believe that Torvalds should get the sole credit even though he didn't do that... Just consider: the GNU Project starts developing an operating system, and years later Linus Torvalds adds one important piece. Now envision the mindset of a person who can look at these events and accuse the GNU Project of egotism.Huh?
Well, no, Richard, I'm sorry. This is like saying 'this is out bridge, because we built the handrails'. Linus did the hard bit, the bit you couldn't do; and he did it brilliantly well. In fact he did three entirely different hard bits, all of which you couldn't do. The first is, he wrote an operating system kernel which worked. Now you're entitled to say that a kernel is not in and of itself an operating system, and that's true. But it is the critical structural element without which a heap of assorted parts don't constitute an operating system. So that's Linus' first achievement: a technical achievement, and a big one.
The second hard bit that Linus did which the Free Software Foundation has clearly failed to do is to evolve a development methodology which allows - encourages - very many people to take part, and which manages to integrate and exploit the fruits of all their labours. That's Linus' second achievement: a social achievement, and a big one.
But Linus third achievement is the key one, and it is key to your project of making Free Software available to ordinary people all over the world. He has brought the system to critical mass, where it's robust enough and stable enough for many people to use it, and in consequence many people are motivated to port many programs to it. This is Linus' third achievement. It's a cultural achievement, and it is an absolutely critical one without which any Free Software movement is ultimately vacuous and solipsistic.
Yes, Richard, my system is a GNU/Linux system. But it is also and equally a KDE [kde.org]/Linux system and an Apache/Linux [apache.org] system. Your contribution - the Free Software Foundation's contribution - is critical; but so is that of the Apache crew and of the KDE crew and the Debian crew and many others. And although I agree that your contributions - especially on the issues of licenses and of the underlying social principles of what we are doing - are critically important, without Linus achievement your achievement would be a footnote on the eccentric fringe of history.
Disparaging Linus not only does you no credit. It actually undermines what you are setting out to achieve. It not only distracts from the important work you are doing on defending the information commons on which we all depend: it undermines your authority to speak on our behalf.
I know that you are a great hacker. I use Emacs every day, and appreciate it greatly; much of what I do depends on things compiled with GCC. But you must realise that your philosophical work is much more important - much more critical - than your software. You were prescient in seeing the assault on the information commons and in making a stand against it, and that will be the contribution for which you will be remembered.
I have no doubt that one day the HURD will be usable. I have no doubt that the HURD, when usable, will be an interesting opererating system kernel. But the critical issue is that you, and your team, could not deliver it when it was needed, and that Linus could. It does you no harm - it diminishes you in no way - to recognise and give honour to that achievement. And it is peurile and childish to pretend that the conrtibution of the Free Software Foundation is any more important to the operating system on my desktop, on my servers, than the contribution of the Apache Foundation and its contributors or of the KDE project and its contributors. It is mean spirited to pretend that without the critical, fundamental contribution of Linus Torvalds, there would be a usable free operating system for ordinary people around the world to use.
Life is not fair. It isn't fair that the Debian KDE/Apache/GNU/Linux operating system on my desk just gets called Linux, when it comprises 796 packages by literally thousands of different authors. After all, forty or so of those packages are GNU softare. Roughly one tenth, or to put it differently, 60% of the KDE project's contribution. But, I say again, the single, critical component that welds the work of the KDE project, and the Apache foundation, and the Free Software Foundation, and hundreds of other contributors contributions into a usable whole is Linus Torvald's contribution and it's only reasonable that he should get top billing.
Grow up. Give credit where it is due, and concentrate on the parts of your work which are really critical - not just to you but to all of us. Concentrate on articulating the principles which allow an information commons in software to exist, and defending that commons from all encroachments. That is your task to do, which you do uniquely well. The honour which Linus has earned does not diminish or detract from the honour which you have earned. It is your carping, your disparagement, your evident jealousy, which detracts and diminishes your honour. Grow up and stop it.
Re:What gets me... (Score:2)
Got that address from his home page [stallman.org], and after reading it, I must say, I do have new respect for him
hear hear! (Score:2)
Anyway. Well fuckin said. I second your oppinion and put forth that my linux box is also comprised similarly.
I call it linux, because the GNU is implied.
Everyone who uses linux probably knows this. Also, if I had a Hurd system, I would likewise call it 'Hurd' and not GNU/Hurd because the GNU is also implied in that case.
I deeply respect RMS and furthermore agree with much of what he says. This is one issue I DISSAGREE with him on. I wish he would listen to what others have to say, especially others who like me agree with 99% of his other stances. It would make him a better representative for the FSF, better liked and would not diminish his philosophical goals one iota. People who never listen to anyone else's oppinions may one day find their oppinions lacking.
Re:hear hear! (Score:2)
Re:What gets me... (Score:5, Informative)
No, it's the bit he didn't do soon enough, because his focus was putting together a widely portable operating system, mainly focusing on tools, that could (and did and still does) run on a variety of kernels, most of which were (at the time), sadly, proprietary.
Another way to view it: from RMS' point of view circa 1989, a "free" kernel was a lot like a "free" device driver, only bigger and more complicated, in that it enabled use of free software on certain hardware (CPUs). Compare that to writing more free OS utilities, which would be portable to all hardware that could support GNU software (regardless of kernel), and you can see why he might have made the choices he did at the time.
Now, did Hurd, once he focused GNU resources on creating it, prove to be an overly ambitious ivory-tower-type project? IMO, yes. In the meantime, Linus and others scratched an itch by evolving (moreso than designing a la Hurd) a kernel for a specific CPU family, which meant that the resources GNU might have used for such a project were used for other, more portable or widely useful, GNU tools -- or, at least, that was a plausible likelihood.
How do I know all this?
Because, in 1988 or 1989, I volunteered my "talents" to RMS for GNU, and specifically asked him if he wanted me to take over the job of writing the OS kernel for GNU, something that was dead-center down my area of expertise. (I'd been doing OS kernel and related work since, oh, about 16 years of age, in a professional sense anyway; since earlier as an "amateur hacker".)
He declined the offer and asked me if I knew anything about Fortran. Since I'd recently learned some things about compilers, specifically Fortran compilers, I said yes, and the upshot was that I wrote GNU Fortran (g77).
RMS's main point at the time was that he believed he'd be able to get some existing portable kernel "freed" for use with GNU, so why throw sparse resources trying to create a free copy out of whole cloth?
Now, you can argue that he should have had me write the kernel instead, and, personally, I would have loved doing that, especially since I'd have been an actual end user of the product (compared to g77, which I don't use). I wouldn't have been nearly as successful at Torvalds when it came to project management though, as can be easily verified from studying g77's history. But my kernel wouldn't have been the ivory-tower-style Hurd, either, and I probably knew more about OS kernel design and implementation as of 1988 than did Linus as of 1991, if technical competency is an important issue. (Not so much a boast as a natural result of having been born so much earlier that I'd had about a two-decade head-start getting into kernel development.)
But, had I undertaken that task, what role might Linus and the others have played? Would they have written g77? I don't think so. They might have scratched some other itch, of course, but, in the end, I think the results are better the way they actually worked out than if I'd been the author of the GNU kernel.
As to your other claims: I agree with most of them, except you do seem to be unaware of the fact that, unlike with Apache, KDE, even BSD components, there is, today, no such thing as a GNU-free Linux kernel, given the kernel's (IMO overly-aggressive) dependency on GNU-specific extensions to the C language.
Linux developed, and remains, much more like a potted plant with GNU as its soil than like a mere partner that happens to use GNU.
Indeed, without that plant, few people would be interested in the "special" soil that is GNU. It's the plant that makes the whole thing worth having, to most people anyway. But GNU soil had been, and continues to be, widely and portably used without a shred of Linux code involved, whereas there is no Linux system without GNU.
(I use "Linux system" to mean a Linux kernel running an OS that provides the means to change the kernel code and recompile the kernel, since that's an important aspect of what makes Linux special. I assume the Linux kernel itself can boot up and run on a given CPU with no GNU code present, but it can't, or at least couldn't, be compiled in the first place without GNU C.)
And, in case anybody's wondering, if it's simply a "small matter of programming" (aka SMOP) to replace the GNU components with some other, thus "demonstrating" that GNU/Linux is really just Linux with a lot of other stuff including GNU, then, by all means, try it.
But, also for the record, there has been, to my knowledge, no shortage of technically competent people who have declared publically that they will write a replacement for GCC that isn't a) GPL-licensed (say, public domain instead) and b) considered a GNU project.
These "threats", as some might view them, go back to maybe 1992 or so -- well before the "GNU/Linux", or "lignux", debacle started by RMS -- yet, last I knew, nobody had actually converted their anger at RMS, the GPL, the GNU project, whatever, into actual code that provides a usable GNU-free Linux.
If and when somebody does write a useful replacement for GNU (for licensing and/or political reasons), that'll be all the more reason to distinguish their Linux variant from the current one, which I have already gotten into the habit of calling GNU/Linux partly in breathless anticipation of that long-awaited event!
Not willing to admit defeat? (Score:2)
Um, yeah. More powerful... hmm. And now that Linux has been ported to everything from Pocket PCs to the Dreamcast... What's the point?
Well, here's to finally supporting 56k modems. You've only got a little further to go till you revolutionize the industry with your superior architecture *g*
Re:Not willing to admit defeat? (Score:4, Informative)
The architecture of the Hurd (not to be confused with the implementation) gives users a lot more freedom than any UNIX-based system. For example, UNIX will not let you mount a loopback encrypted filesystem unless you are root (or without bugging root to frob
Porting, and supporting 56k modems are just implementation details, and have nothing to do with the architecture, which is what RMS is talking about.
Re:Not willing to admit defeat? (Score:2)
>>>>>>>>
Praytell, exactly what architectural features (technical reason, please) does Hurd have that allow it to allow users to mount encrypted filesystems? It seems to me like its a policy decision in UNIX kernels, not a technical one.
Porting, and supporting 56k modems are just implementation details, and have nothing to do with the architecture, which is what RMS is talking about.
Microkernel vs Monolithic (Score:2)
Obviously it's biased towards monolithic, but it's an interesting read nontheless.
Slashdot losers (Score:5, Insightful)
Can slashdot posters quit talking out of their rear-ends for even one article?
A long-running project in the open source world just made an announcement. The
I'm very interested in how the HURD is progressing, and in TECHNICAL OPINIONS on the HURD. Where are the technical opinions among the comments? Damn few and far between. This is the sort of nonsense that makes slashdot look worse than USA Today (hell, slashdot doesn't even have color barcharts on the front page!).
At one time, I learned a lot about computers and socioeconomic factors surrounding computing by reading slashdot comments. Several years ago, comments included information from computer scientists, sysadmins, and knowledgable hobbyists. Eventually there was a problem where you couldn't find those comments in between the 50 copies of "First Post!". Moderation came, and I could usually find the good posts again.
The comments on this article, however, demonstrate just how stupid the slashdot population has become. My theory is that the huge popularity of slashdot in the US has attracted a readership which closely mirrors the average intelligence of the general US population -- you know, the same population that elected GW Bush for president (motto: "What we need is a clear policy in the Middle East"). The moderation system that once worked well is failing miserably because almost all moderators are as stupid as the posters.
As anyone can tell, I'm pretty pissed that a bunch of whiney losers in diapers, who couldn't spell "algorithm" if they had a copy of CLR on their desk, or explain why CISC was a natural choice for microprocessors in the 1960s, have drowned out any hope of interesting discussion on a technical topic. The comments attached to this article provide some sort of slashdot corrolary to the bikeshed axiom [freebsd.org]: Since a moron reading slashdot feels compelled to make authoritative posts on every article (to increase their karma?), they will post about the bikeshed color if they have nothing to say about the bikeshed. God help us when the discussion turns to nuclear power plants.
Beyond technical comments, why does everyone feel a need to deride RMS and the GNU project all the time? It seems natural to have some social discussion of RMS and the GNU project attached to any article about the HURD. I can understand why RMS is unpopular. I can understand why some people dislike RMS' campaign to use the name "GNU/Linux" when discussing operating systems which use the GNU foundation but replace the GNU kernel (I guess my feeling on this is clear). What I can't understand is why people put so damn much energy into making RMS a laughing stock.
At this point, it no longer matters what RMS does or says; the slashdot readership seems hell-bent on destroying RMS just because they heard that he was unpopular in some circles. If I were a conspiracy theorist, I'd suggest that Microsoft had a pool of RMS-trolls trying to change public opinion of RMS, GNU, and Free Software via slashdot comments.
I'd like to encourage everyone reading this to do the following:
1) Think for yourself
2) Listen careefully to what people say, in comments and otherwise
3) If you don't have anything useful to contribute, then keep your mouth closed.
4) Be careful with the "funny" moderation tag -- we all need humor, but there's more (or should be) to slashdot than (rightly or wrongly) smacking people down
If we follow those rules, then maybe we'll be able to learn stuff from slashdot comments again. For instance, comments on this article about a new HURD release might include:
1) discussions of microkernel history, strengths, and weaknesses,
2) which microkernels are still in use
3) how the Darwin kernel design differs from the HURD design
4) a reasonable, well-thought-out debate about whether the long term benefits of the HURD justify the current HURD effort in the Free Software community
5) how changes in hardware might affect the expected future value of the HURD, given the HURD's extremely slow development
6) alternatives to monolithic and microkernel designs in principle and practice (I'm not aware of any, but surely someone has something in-between, if not totally different)
7) whether the Free Software and Open Source communities should really be involved with basic software research, or lower its ambitions and simply copy existing, working software
Maybe this post can at least spawn an intelligent discussion of whether it violates the rules it proposes (it probably does, but I'm not going to fix it because I'm still seeing red).
-Paul Komarek
Re:Slashdot losers (Score:4, Informative)
Seems to me the opposite would be true for embedded systems - all the benefits of microkernels I can think of tend toward more fully featured systems; for example in the NT world, the OS/2 1.x and POSIX subsystems were seperate personalities on the microkernel. Those are neat features when you want to run diverse userlands on a common platform, but it seems like overkill for an embedded system, where the overhead of the microkernel in terms of size and performance may be too high a price.
As for security, I'm not sure how a microkernel would be a plus or a minus. I suppose the fact that splitting various components of the OS into personalities makes it (in theory) harder to subvert all components by subverting one component.
To be honest, what I'm curious to see is an mk based OS that actually meaningfully demonstrates the benefits of being based around a microkernal. NT could have if MS had been more committed to running the alternate personalities on the same microkernel, but their efforts at POSIX/Unix personalities running alongside the Win32 system have always been sporadic. Too many of the other benefits (such as not having your system die when a network driver goes tits up) mostly benefit programmers (after all, if the NIC in my file server keeps crashing, it's nice that I don't have to reboot to restart the NIC, but I still have an unavailable system).
Re:Debian GNU/Hurd (Score:2, Informative)
It's work in progress, and already usable. See http://www.debian.org/ports/hurd/ for installation instructions.
By the way, Mach isn't "the hurd kernel", as Michael implies. The Hurd is userspace servers - therefore then name "Hird of Unix-replacing _Daemons_".
Re:Debian GNU/Hurd (Score:2)
Re:announcement (Score:3, Funny)
Reminds me of a book I used to have, "Programming 68000 Assembler". This excellent book was obviously written by an old cynic, and aged very well. However, it did contain the immortal line:
"Today's powerful Unix systems often contain as much as 256k of memory"
Yes. k. Not Gig. Not even Meg. k.
Aah, for the good old days when programmers were programmers and a complete game of Chess could be fitted into a 1k ZX81. Hmmm, on second thoughts - maybe not.
Cheers,
Ian
Re:announcement (Score:2)
Aah, for the good old days when programmers were programmers and a complete game of Chess could be fitted into a 1k ZX81.
Or even a 4K ROM with 256 bytes of RAM. There were some uber-hackers working on that Atari 2600 chess program. Not that it played chess very well...
Re:announcement (Score:2, Offtopic)
Version: PGPfreeware 5.0i for non-commercial use
[emphasis me]
well thats interesting, they're not using GNUpg [gnupg.org]
Re:Reinventing the wheel? (Score:4, Insightful)
Re:Reinventing the wheel? (Score:2)
Why do you think he continues to insist that it be called GNU/Linux? Calling it linux alone steals his thunder and hijacks 'his' revolution.
And you can bet Bitkeeper won't be allowed near the HURD's source either.
Re:Reinventing the wheel? (Score:3, Insightful)
Fair point, but only really valid in a commerical context. Some people are just writing for the hell of it, and they don't care whether they've created a Windows competitor or not - they're just enjoying their code.
Cheers,
Ian
Re:Reinventing the wheel? (Score:2, Insightful)
Re:Reinventing the wheel? (Score:2)
While I think the goals are noble there is the theoretical and the practical. And the problem with commercial development is that the theoretical are only small pieces of a very larger commerical reality.
While LINUX has had issues regarding memory management, bigger issues are drivers, applications, support, etc, etc.
try this: TUNES (Score:3, Interesting)
TUNES [tunes.org]
Are you looking for fun? It's based on Lisp [tunes.org] - that the real fun!
Features [eleves.ens.fr] of TUNES;
Review of other [tunes.org] systems;
Re:try this: TUNES (Score:2)
I think we're a long way from having a really robust, modular operating system that's easy for anyone to use. It's at least ten years away, probably more.
Re:Reinventing the wheel? (Score:2)
Well, lets see. Hundreds of thousands of available programmers, Thousands of projects. that roughly divides ito hundreds of programmers per project (if they were so lucky).
Most of the time when we hear complaining about fragmentation, what it usually comes from is the speakers desire to have the programmers that are working on projects he doesn't care about to switch to projects he does care about.
Fragmentation is just another word for variety. There are multiple projects covering almost any area of software you can mention. If it were somehow determined that only one project in each area would survive and the rest would go away, then we are setting ourselves up for monopolies. We'll be trying to make one program be all things to all people. That's what we are trying to get away from.
Hurd is different from the Linux Kernel. Some things are worse (stability, speed) and some things are better (configurability, dynamic services). People will choose based on what they need, and different people need different things. you've decided what you want. Now be kind enough to allow the rest of us to choose for ourselves.
Infinite (Score:2)
An infinite amount.
People may say it cracks with every keystroke but it just won't break.
Re:Hurd is like Itanium (Score:2)
Re:Can it play OpenGL games? (Score:3, Funny)
Don't fret. Stallman is very much into modelling [stallman.org]
Re:Can it play OpenGL games? (Score:2)
Re:Can it play OpenGL games? (Score:3, Informative)
But X does work, so it isn't just text. It has X11R6 v 4.2 I believe.
Actually Netcraft says he uses FreeBSD!! (Score:3, Informative)
Netcraft check of www.stallman.org [netcraft.com]
Re:Actually Netcraft says he uses FreeBSD!! (Score:2, Troll)
I think you mean GNU/FreeBSD, don't you?
Quoth RMS:
"Many computer users run a modified version of the GNU system every day, without realizing it. Through a peculiar turn of events, the version of GNU which is widely used today is more often known as ``FreeBSD'', and many users are not aware of the extent of its connection with the GNU Project.
"There really is a FreeBSD; it is a kernel, and these people are using it. But you can't use a kernel by itself; a kernel is useful only as part of a whole operating system. FreeBSD is normally used in a combination with the GNU operating system: the system is basically GNU, with FreeBSD functioning as the kernel.
"Many users are not fully aware of the distinction between the kernel, which is FreeBSD, and the whole system, which they also call ``FreeBSD''. The ambiguous use of the name doesn't promote understanding.
Re:Actually Netcraft says he uses FreeBSD!! (Score:2)
Re:Not BSD! (Score:3, Informative)
Firewire and USB work perfectly on my BSD system. Its called MacOS X.
Re:apple (Score:3, Insightful)
Mac OS X's Mach is a Different Breed (Score:2)
IANAP, but some lackey on Linux Journal dared to write an article declaring the microkernel a dead technology in this article [linuxjournal.com].
A ton of people slammed his lack of research and knowledge of microkernels, Mach, Mac OS X, or Darwin. The article is less than useful, but the responses from the irate readers explaining how Apple implements Mach (and its pretty damn clever--they take the Mach and BSD fusion to a monolithic state).
Re:apple (Score:2)
Kernel isn't the whole story (Score:3, Insightful)
Hurd is not just a microkernel implementation but also a set of servers running on top of that microkernel providing all sorts of clever services through a unique architectural model. Darwin is also running on a Mach-derived microkernel but it is running a single server in a traditionial model.
Trust me - go invest the 5 minutes to read up on hurd, it's goals and how it is going about meeting them. VERY different from the rest of the field and potentially a revolution if it succeeds.
Oh, and the assumption that there are more drivers for Linux then IOKit? That's changing quickly as MacOS X becomes the dominant consumer Unix.
Re:apple (Score:2)
Apple is as proprietary, controlling and greedy as MS on the best of days. Remember, these people will sue you for talking about new features before Steve can tell you how wonderful they are.
Re:apple (Score:2)
Re:This is a _good_ thing (Score:2)