Slashdot Mirror


GNU Hurd 0.5, GNU Mach 1.4, GNU MIG 1.4 Released

jrepin writes "Which day could be better suited for publishing a set of Hurd package releases than the GNU project's 30th birthday? These new releases bundle bug fixes and enhancements done since the last releases more than a decade ago; really too many (both years and improvements) to list them individually, The GNU Hurd is the GNU project's replacement for the Unix kernel. It is a collection of servers that run on the Mach microkernel to implement file systems, network protocols, file access control, and other features that are implemented by the Unix kernel or similar kernels (such as Linux)."

143 of 206 comments (clear)

  1. I might not be here for Hurd 1.0 by Freshly+Exhumed · · Score: 5, Funny

    30 years for Hurd 0.5, so 1.0 will be available in 2043?

    --
    I deny that I have not avoided attaining the opposite of that which I do not want.
    1. Re:I might not be here for Hurd 1.0 by MrEricSir · · Score: 5, Informative

      GNU is 30 years old, but Hurd is "only" 23. It started while the first Bush was still president rather than Reagan.

      --
      There's no -1 for "I don't get it."
    2. Re:I might not be here for Hurd 1.0 by erroneus · · Score: 2

      I was thinking something along those lines myself. To arrive at "1.0" would mean that it would be feature complete and stable according to the "1.0" set defined when "1.0" was created as a target. That already makes me wonder if Hurd is absolete before it has been completed.

    3. Re:I might not be here for Hurd 1.0 by Lunix+Nutcase · · Score: 4, Funny

      And in 2063, Steam for Hurd!!!

    4. Re:I might not be here for Hurd 1.0 by Freshly+Exhumed · · Score: 4, Funny

      So they'll complete Hurd 1.0 just in time for the 2038 bug! That gives them 23 more years to go completely 64-bit by then.

      --
      I deny that I have not avoided attaining the opposite of that which I do not want.
    5. Re:I might not be here for Hurd 1.0 by iggymanz · · Score: 5, Informative

      wrong. the initial failed attempt at HURD started in 1986 with a BSD 4.4 like kernel. The project is thus 27 years old. still not stable, not suitable for any production use, and only runs on i386, it is a failure

    6. Re:I might not be here for Hurd 1.0 by Cinder6 · · Score: 2

      Christ, and we thought Duke Nukem took forever.

      --
      If you can't convince them, convict them.
    7. Re:I might not be here for Hurd 1.0 by krkhan · · Score: 5, Funny

      Just in time for Chrome 2147483647.

    8. Re:I might not be here for Hurd 1.0 by Anonymous Coward · · Score: 1

      You guys need to stop thinking about time so linearly.....

    9. Re:I might not be here for Hurd 1.0 by TheloniousCoward · · Score: 2

      Yes. They plan to speed up its development by rewriting it in Perl 6.

    10. Re: I might not be here for Hurd 1.0 by jmccay · · Score: 1

      Nah. More likely 2103. Don't forget the years it will take to actually take it seriously.

      --
      At the next eco-hypocrisy-meeting, count the private jets used to get to the meeting. Should be interesting to see that
    11. Re:I might not be here for Hurd 1.0 by ArchieBunker · · Score: 3, Insightful

      The people in charge of that are so out of touch they should be committed in a mental hospital. It wasn't that long ago they finally supported partitions bigger than 2GB, yes two GigaBytes. Think about that fact while you also learn that RMS uses an old terminal or some such nonsense along with a script to gather Google searches and email the text to him. He lacks a graphical interface.

      --
      Only the State obtains its revenue by coercion. - Murray Rothbard
    12. Re:I might not be here for Hurd 1.0 by phantomfive · · Score: 5, Insightful

      My understanding is the people who are doing it now are mainly doing it for fun, because they like kernel programming. there is no longer a pressing urgent need for a free kernel. And if they come up with some good ideas, they will be copied into more mainstream kernels.

      --
      "First they came for the slanderers and i said nothing."
    13. Re:I might not be here for Hurd 1.0 by Jeremy+Erwin · · Score: 2

      Any truly long term development project must consider the technological singularity. It is a waste of time and effort not to take advantage of this fabulous opportunity.

    14. Re:I might not be here for Hurd 1.0 by NJRoadfan · · Score: 5, Funny

      Think of "1.0" as an asymptote. It'll approach 1.0 but never actually reach it.

    15. Re:I might not be here for Hurd 1.0 by Pseudonym · · Score: 1

      Just in time for Half-Life 2: Episode 2.2.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    16. Re: I might not be here for Hurd 1.0 by otherniceman · · Score: 1

      You sound like my mom.

    17. Re:I might not be here for Hurd 1.0 by K.+S.+Kyosuke · · Score: 4, Interesting

      Think about that fact while you also learn that RMS uses an old terminal or some such nonsense along with a script to gather Google searches and email the text to him.

      If you think about it, it's a fairly effective way of avoiding getting hacked (or at least minimizing the attack surface).

      --
      Ezekiel 23:20
    18. Re:I might not be here for Hurd 1.0 by aix+tom · · Score: 4, Funny

      Yea. Actually, from a non-linier, non subjective point of view it is more like a big ball of wibbily wobbly timey wimey...stuff

    19. Re:I might not be here for Hurd 1.0 by TheRaven64 · · Score: 5, Interesting

      And they've been using it to explore some quite interesting ideas in kernel design. The fine-grained compartmentalism that a microkernel provides (at the expense of some performance) is starting to look more attractive in a world where computers run in very hostile environments and yet even a 50% slower kernel would have a negligible impact on user-perceived performance (or battery life).

      --
      I am TheRaven on Soylent News
    20. Re:I might not be here for Hurd 1.0 by fatphil · · Score: 3, Informative

      The funny thing is that for some kernels, it's perfectly true. I know the kernel I run on this workstation here gives about 99.5% of the cycles to the userspace programs that I launch. Yet playing very briefly with a windows 8 system a few months back (it survived about 20 minutes between arrival at the office and having linux put on it), the kernel and hundreds of intimately-bound-I-don't-know-what-the-fuck-they-do-or-why-I-would-ever-want-them daemons were taking up between 5% and 10% of the CPU constantly. The former I would happily accept a 50% increase in overhead to, I'm perfectly happy only having 99.25% to myself. But the latter would have ground to a halt if there were any more impediments to interprocess communication.

      --
      Also FatPhil on SoylentNews, id 863
    21. Re:I might not be here for Hurd 1.0 by cascadingstylesheet · · Score: 1

      Though one could be forgiven for getting the timeline mixed up, given all the bizarre declarations, bizarre nomenclature, confusion of theoretical projects with real projects, dogmatic insistence that things are in fact whatever Stallman calls them, etc.

    22. Re:I might not be here for Hurd 1.0 by serviscope_minor · · Score: 3, Insightful

      The people in charge of that are so out of touch they should be committed in a mental hospital.

      Well, aren't you so high and mighty and important shitting on someone else's personal project.

      That's all hurd is: it's a small hobby project by a very small number of programmers.

      It's not for you, it's for them. Being "in touch" with you is not a requirement.

      Oh and by the way, I've no idea what your hobbies are, but I'm sure they suck and you're crap and should be in a mental hospital.

      Think about that fact while you also learn that RMS uses an old terminal or some such nonsense along with a script to gather Google searches and email the text to him. He lacks a graphical interface.

      Firstly, I already knew that.

      Secondly, so what? That's his choice. You know he does that on GNU/Linux, right?

      On a MIPS laptop which doesn't even run hurd? You know that too, right?

      --
      SJW n. One who posts facts.
    23. Re:I might not be here for Hurd 1.0 by c · · Score: 2

      30 years for Hurd 0.5, so 1.0 will be available in 2043?

      Well, no. Being a Unix replacement, I'd expect it sometime around 1975.

      --
      Log in or piss off.
    24. Re:I might not be here for Hurd 1.0 by jones_supa · · Score: 1

      30 years for Hurd 0.5, so 1.0 will be available in 2043?

      I know I'm being a pedantic pangolin here and ruining your joke without any good reason, but we should still remember that version numbers are not floating point numbers. Rather, they contain groups of integer numbers separated with a dot. So after 0.9 there might still be 0.10, 0.11, etc...

    25. Re:I might not be here for Hurd 1.0 by drinkypoo · · Score: 2

      He's protected from the Snow Crash, but the Blight will still own his computer.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    26. Re:I might not be here for Hurd 1.0 by mellon · · Score: 2

      Meh, the blight will just hack the people in the cubicle next to him and send them over to make him sit in front of the programming screen. No need to hack him through an ASCII terminal. Prepare to be assimilated! (Speaking of which, why do Borgs always say stuff like that? How do you prepare to be assimilated?)

    27. Re:I might not be here for Hurd 1.0 by Stewie241 · · Score: 1

      I thought the Borg said things more along the lines of 'You will be assimilated. Resistance is futile'. Not so much a request to prepare, just a statement that it will happen.

    28. Re:I might not be here for Hurd 1.0 by fnj · · Score: 1

      Let me try to understand this.

      0.5% overhead is fine with you. I am absolutely in agreement with this.

      5-10% overhead horrifies you. OK, you're starting to lose me here. 5-10% overhead is canceled out completely by maybe TWO MONTHS of CPU development. It's nothing. Nada.

      Anticipation of an implied rise to perhaps 7.5-15% overhead seems to make you reel in dismay. That seems to you to equate to the system grinding to a halt. Funny, in my world it translates to a system which is 85-92.5% as efficient as a theoretical zero-overhead system. I wouldn't welcome it for no reason, but hypothetically if it gave me significantly better reliability and security I would be inclined to accept it quite happily. Such an overhead is completely imperceptible subjectively. You would never notice it was there if you didn't instrument the system and run some benchmarks.

      OTOH, lengthy UI latencies of one or more seconds at a time (Windows, I'm talking about you) are extremely noticeable and objectionable. In the previous considerations, I'm assuming that the overhead is not necessarily producing lengthy latencies.

    29. Re:I might not be here for Hurd 1.0 by fnj · · Score: 1

      Not to mention 0.9.1, 0.9.1.1, 0.9.1.1.1 ...

    30. Re: I might not be here for Hurd 1.0 by mrchaotica · · Score: 1

      Dangit, you were this close to an "All your base..." meme!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    31. Re:I might not be here for Hurd 1.0 by iggymanz · · Score: 1

      but other projects have done such things *successfully* and could even be used on a real server to provide a real service, for example minix 3

    32. Re:I might not be here for Hurd 1.0 by shaitand · · Score: 2

      "GNU/Linux"

      I didn't know GNU produced a Linux system. Yes, I know the reference it is the result of petty jealousy and attempt at attention grabbing, nothing more.

    33. Re:I might not be here for Hurd 1.0 by phantomfive · · Score: 1

      5-10% overhead is canceled out completely by maybe TWO MONTHS of CPU development.

      I really wish CPUs were increasing speed at that rate

      --
      "First they came for the slanderers and i said nothing."
    34. Re:I might not be here for Hurd 1.0 by drinkypoo · · Score: 1

      Meh, the blight will just hack the people in the cubicle next to him and send them over to make him sit in front of the programming screen.

      Not this far into the slowness.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    35. Re:I might not be here for Hurd 1.0 by Kjella · · Score: 1

      Yet playing very briefly with a windows 8 system a few months back (it survived about 20 minutes between arrival at the office and having linux put on it), the kernel and hundreds of intimately-bound-I-don't-know-what-the-fuck-they-do-or-why-I-would-ever-want-them daemons were taking up between 5% and 10% of the CPU constantly.

      OEM or corporate install full of crapware? Pure Windows (installed yourself from an OEM/retail disc) is a whole different ballgame, Microsoft actually doesn't add much crap like that. I don't have personal experience with a clean Win8 install, but at least on Win7 it's 99-100% idle when I don't do anything.

      --
      Live today, because you never know what tomorrow brings
    36. Re:I might not be here for Hurd 1.0 by Zero__Kelvin · · Score: 2

      Keep in ,mind that with Windows, Internet Explorer is an integral part of the kernel !* ;-)

      *No, I don't believe that, but Bill Gates certainly wanted US Courts to think so back in the day.

      --
      Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
    37. Re:I might not be here for Hurd 1.0 by Zero__Kelvin · · Score: 2

      Your post represents a complete mis-characterization of Moore's Law.

      --
      Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
    38. Re:I might not be here for Hurd 1.0 by TheRaven64 · · Score: 1

      MINIX 3 is a pretty conventional microkernel. Take a look, for example, at some of the virtual memory stuff done in L4/HURD. This can be seen as a continuation of the external pager support in Mach, but with a much simpler and cleaner design and a lot of direct application to current workloads.

      --
      I am TheRaven on Soylent News
    39. Re:I might not be here for Hurd 1.0 by hobarrera · · Score: 1

      cron is userspace, so that's not an issue, he's talking about kernel-used CPU cycles, of stuff tighly integrated into the lower levels of the OS.
      crontab -e will let you edit cron tabs that you distro preconfigured easily, completely unrelated to Linux itself.

      And 20 minutes, you say? The Windows box was probably downloading and processing updates. You know, when booting up a Linux which has never been updated, it would also be prudent to have it updated during the first 20 minutes.

      Not unless I configure it to do so.

    40. Re:I might not be here for Hurd 1.0 by jonbryce · · Score: 1

      It is an integral part of the operating system, not the kernel.

    41. Re: I might not be here for Hurd 1.0 by RyuuzakiTetsuya · · Score: 1

      I don't think that project will ever get off the ground.

      GNU/Hurd time and Valve time intersecting means a catastrophe of epic proportions.

      --
      Non impediti ratione cogitationus.
    42. Re:I might not be here for Hurd 1.0 by Zero__Kelvin · · Score: 1

      It is neither.

      --
      Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
    43. Re:I might not be here for Hurd 1.0 by ultranova · · Score: 1

      How do you prepare to be assimilated?

      Quickly memorize My Immortal so you'll be spit out and humanity classified as "poisonous - don't eat"?

      It works for caterpillars.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    44. Re:I might not be here for Hurd 1.0 by unixisc · · Score: 1

      And they've been using it to explore some quite interesting ideas in kernel design. The fine-grained compartmentalism that a microkernel provides (at the expense of some performance) is starting to look more attractive in a world where computers run in very hostile environments and yet even a 50% slower kernel would have a negligible impact on user-perceived performance (or battery life).

      But are these achievable under Mach? I know that some microkernels seem to be very good - like Chorus, L4 and now Minix 3.x. But has Mach progressed much since 3.0? Only positive thing about it is that it is multi-platform, but w/ just x64 and ARM remaining, that's not saying much.

      HURD had experimented w/ a number of microkernels, but I think they'd have done well to fork Minix 3.x and port the HURD there. Oh, and as some noted above, since they are so late, they might as well go directly to 64-bit, and work on being portable on a variety of architectures. If they do it right, it could even be the basis for Replicant.

    45. Re:I might not be here for Hurd 1.0 by jones_supa · · Score: 1

      Do you happen to be the Product Manager for Adobe Flash? ;)

    46. Re:I might not be here for Hurd 1.0 by raju1kabir · · Score: 1

      I didn't know GNU produced a Linux system.

      They maintain many of the userspace tools that make it actually, you know, usable.

      Linux alone is just the kernel. That's a small part of the actual system that makes the computer do things.

      --
      "Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
    47. Re:I might not be here for Hurd 1.0 by iggymanz · · Score: 1

      MINIX 3 is a properly engineered system, with reality trumping ivory tower theory. HURD has issues that are unsolved to this day.

    48. Re:I might not be here for Hurd 1.0 by shaitand · · Score: 1

      The kernel is the part that actually provides the system. GNU maintains some very handy optional utilities/libraries that one might opt to run on that system and that often are chosen. The kernel can run without those utilities/libraries. The utilities can not run without some flavor of operating system to run them on, Linux being one example of such.

      GNU produces some very valuable stuff. That is worthy of recognition and acclaim. It provides not the slightest bit of credibility to a petty tantrum and rant trying to steal the acclaim of a completely distinct project by asserting everyone should stick your teams name IN FRONT of the name of that project if anyone happens to bundle the two together.

      Or perhaps it is the compiler and c libraries. There are other options for that as well. Why aren't the GNU team trying to assert that every obscure project nobody cares about that is compiled with their compiler be called GNU/x where x is the name of that project? It would make more sense than cherry picking a project that is popular... at least it would if it weren't about simply being jealous about that project getting more mainstream attention than theirs.

    49. Re:I might not be here for Hurd 1.0 by raju1kabir · · Score: 1

      The kernel can run without those utilities/libraries. The utilities can not run without some flavor of operating system to run them on, Linux being one example of such.

      The kernel can't do anything useful without the userspace stuff, the GNU tools can't do anything without a kernel. They're both dependent on the other, and the "other" is fungible but they are most commonly found in this pairing. It's a fairly equal relationship.

      --
      "Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
    50. Re:I might not be here for Hurd 1.0 by shaitand · · Score: 1

      "The kernel can't do anything useful without the userspace stuff"

      False. The kernel can do exactly what it is supposed to do, provide a managed and unified system for applications to target. You can write a program to run on top of the Linux kernel/OS that doesn't require a shell, or any GNU tools. There are alternatives that provide similar functionality to the GNU tools as well. The kernel is no way dependent on the GNU tools they are merely a popular choice to combine with the kernel. Similarly, the GNU tools are not dependent on the Linux OS but they are dependent on there being an OS to run them on.

      It is quite likely there are several Linux systems in your home that do not include GNU tools at all. You may not even be aware they are running Linux.

    51. Re:I might not be here for Hurd 1.0 by raju1kabir · · Score: 2

      Yeah, none of this addresses my argument.

      There are also several systems in my home with large bases of installed GNU tools, that don't run Linux at all.

      Linux doesn't need GNU tools. Nobody's arguing with you there.

      GNU tools don't need Linux.

      But the vast majority of the time, you find them together. Specifically, in all the distributions that some (admittedly persnickety) people like to call GNU/Linux.

      --
      "Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
    52. Re:I might not be here for Hurd 1.0 by Urkki · · Score: 1

      cron is userspace, so that's not an issue, he's talking about kernel-used CPU cycles, of stuff tighly integrated into the lower levels of the OS.
      crontab -e will let you edit cron tabs that you distro preconfigured easily, completely unrelated to Linux itself.

      And 20 minutes, you say? The Windows box was probably downloading and processing updates. You know, when booting up a Linux which has never been updated, it would also be prudent to have it updated during the first 20 minutes.

      Not unless I configure it to do so.

      The mentioned Windows services are also userspace, and would not be hit by kernel getting more overhead, which was the whole point.

      Also, it seems this Windows was pre-installed, and anybody shipping pre-installed Windows without turning automatic updates on should be shot for malicious negligence. If you install it yourself, IIRC you will be prompted how you want to handle updates (may depend on version).

    53. Re:I might not be here for Hurd 1.0 by shaitand · · Score: 1

      "Linux doesn't need GNU tools. Nobody's arguing with you there.

      GNU tools don't need Linux."

      "Specifically, in all the distributions that some (admittedly persnickety) people like to call GNU/Linux."

      You do know that the debate is about whether or not the GNU demand that everyone refer to Linux as GNU/Linux is reasonable? At least, that's what I thought we were debating. If you agree to the above then I'm just plain confused.

    54. Re:I might not be here for Hurd 1.0 by Urkki · · Score: 1

      And 20 minutes, you say? The Windows box was probably downloading and processing updates.

      No, just kernel + system services.

      You know, when booting up a Linux which has never been updated, it would also be prudent to have it updated during the first 20 minutes.

      In your assumed on-line scenario, it installs up-to-date, thank you.

      Uh... The assumed scenario is, a new computer arrives with who-knows-how-old pre-installed Windows image... It's irrelevant wether it was installed up-to-date or not whenever the image was created, if it has not been updated since then.

      Also, this was about changing kernel to be microkernel, with more overhead. Services are not kernel, so any number which includes them is irrelevant in the context presented in the post I replied to.

      Either the computer was doing something related to being turned on for the first time, or there was some serious crapware installed. This Windows f'ing Vista running on this low-end laptop from 2009, with single core Celeron, and which has never been reinstalled, uses 0..1% CPU when I check Task Manager performance graph. If a new computer shows 10%, then it's not the kernel.

    55. Re:I might not be here for Hurd 1.0 by Urkki · · Score: 1

      "Have you ever looked at how much CPU a Linux OS takes, when certain cron jobs kick in? Just horrible!"

      Certain cron jobs? Do you even know what cron is or how it works? Presumably you have a cron entry that runs "Eat-All-My-CPU-So-I-Can-Make-Absurd-Statements-On-Slashdot.sh".

      "And 20 minutes, you say? The Windows box was probably downloading and processing updates. "

      Since when does Windows automatically apply updates at power on without the new user telling it to do so? More likely it was still completing the boot process after doing the initial desktop paint "fake-out" that is done to make it appear that it boots much more quickly than it actually does. ;-)

      "My point is, even though Windows may suck in many exquisite ways, your post is way off the mark."

      Where is it off the mark? While yours is clearly absurd, I see nowhere where the GPs was off the mark.

      Indeed, there was probably something equal to cron job "Eat-All-My-CPU-So-I-Can-Make-Absurd-Statements-On-Slashdot.sh" on that PC, because now that I could check, normal CPU usage of idle Windows box seems to be 0..1%. The point is, that is not kernel, that's userspace... Read the post I replied to again, it talks about increasing kernel overhead. The overhead is exactly same for system services and other userspace programs.

      Anyway, your guess about "completing boot process" may well be spot on, though it probably was "first boot process" then, because slowest I've seen Windows finishing startup for real, on a laptop with encrypted slow HD and a ton of corporate crapware, is around 10 minutes.

      But GP was off the mark by considering the 10% figure (whatever the reason for it) including system services in the 50% microkernel overhead thought experiment. If system services suffer the overhead, then so would any userspace programs.

    56. Re:I might not be here for Hurd 1.0 by srobert · · Score: 1

      So will 2043 be the year of the GNU/Hurd Desktop?

    57. Re:I might not be here for Hurd 1.0 by raju1kabir · · Score: 1

      My understanding has always been that RMS wants people to refer to distributions that contain the Linux kernel and GNU userspace tools to refer to it as GNU/Linux... not that he wants the Linux kernel itself to be referred to as GNU/Linux.

      --
      "Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
    58. Re:I might not be here for Hurd 1.0 by shaitand · · Score: 1

      "My understanding has always been that RMS wants people to refer to distributions that contain the Linux kernel and GNU userspace tools to refer to it as GNU/Linux... not that he wants the Linux kernel itself to be referred to as GNU/Linux."

      Which you apparently think is ridiculous as well:

      "Specifically, in all the distributions that some (admittedly persnickety) people like to call GNU/Linux."

      Right, so again. It is difficult to argue with someone who agrees with you.

    59. Re:I might not be here for Hurd 1.0 by raju1kabir · · Score: 1

      I think they are overly sensitive about it, but I do see where they're coming from. It is in fact possible to see both sides of an issue, if you open your mind a little.

      And, importantly, the straw man that you're arguing against (that RMS wants people to call the kernel GNU/Linux) is way out in left field. If you are confused about GNU's position, it's clearly laid out here: http://www.gnu.org/gnu/linux-and-gnu.html

      --
      "Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
    60. Re:I might not be here for Hurd 1.0 by twocows · · Score: 1

      The "kernel" is not an operating system, and without GNU, you do not have a functional system. See: http://www.gnu.org/gnu/gnu-linux-faq.html#tools

    61. Re:I might not be here for Hurd 1.0 by shaitand · · Score: 1

      The GNU faq does not set the definitions. A monolithic kernel is a fully functional system once booted and without GNU you have a perfectly functional system. Ask millions of embedded devices that don't utilize anything GNU or perhaps simply look at Android, a distribution built on the Linux OS that doesn't use GNU.

    62. Re:I might not be here for Hurd 1.0 by Specter · · Score: 1

      "Resistance is futile"

      I thought that was the Vogons.

  2. Understatement of the year by tmark · · Score: 2

    "Development of the Hurd has proceeded slowly." (http://en.wikipedia.org/wiki/GNU_Hurd)

    As per http://www.gnu.org/software/hurd/hurd/status.html: " It may not be ready for production use, as there are still some bugs and missing features".

    Exactly how long has it been like this ? I tracked this project for about a decade until I concluded it would never be ready for production - over a decade ago.

    1. Re:Understatement of the year by NJRoadfan · · Score: 5, Insightful

      You knew it was bad when Duke Nukem Forever actually made it to stores.

    2. Re:Understatement of the year by fnj · · Score: 1

      It makes glaciation, erosion of canyons, and rise and fall of mountains appear to be blindingly rapid.

    3. Re:Understatement of the year by jones_supa · · Score: 1

      In retrospective, the production has taken so long that the Hurd project should not have been started at all.

  3. a better day? by Bill,+Shooter+of+Bul · · Score: 1

    Oh, I don't know maybe some day in the early 90's. Back when it would have been useful to me. /kidding only a little.

    --
    Well.. maybe. Or Maybe not. But Definitely not sort of.
  4. Time in unpredictable. by wjcofkc · · Score: 1

    I've heard it said that time moves on and that maybe even Linux won't last forever. Wether or not that is true I Believe *nix in general will be around for a long long time yet. Fast forward a decade or two - despite Hurd and it's sllloowww.... development being a bit of a joke, wouldn't it be something if we are all actually using Hurd in the future? Stranger things have happened.

    --
    Brought to you by Carl's Junior.
    1. Re:Time in unpredictable. by icebike · · Score: 1

      Still, I'm not sure there was ever a 10 year gap between Linux releases.

      --
      Sig Battery depleted. Reverting to safe mode.
    2. Re:Time in unpredictable. by aix+tom · · Score: 1

      In software there is always the chance of a "Dang, we have to re-write this thing from scratch" moment, when something becomes to cluttered an unmanageable.

      In such a moment ever happens to Linux (or another FOSS OS) they can always pick up things like HURD and go from there, if it fits their goals better than the thing that became to "wrong direction". With FOSS the chance of having someone or something "gone the first steps for fun" and getting picked up later by someone else is always there.

  5. Proposal: by pseudofrog · · Score: 4, Funny

    Fork a BSD variant, license it under the GPL, package it with GNU stuff, call it Hurd 1.0.

    1. Re:Proposal: by Anonymous Coward · · Score: 1, Insightful

      Who would want free BSD software relicensed under a shittier unfree license?

    2. Re:Proposal: by Boronx · · Score: 5, Insightful

      Mac users?

    3. Re:Proposal: by Anonymous Coward · · Score: 3, Informative

      Fork a BSD variant, license it under the GPL, package it with GNU stuff, call it Hurd 1.0.

      Just in case you (or anyone else who reads this) is really so ignorant of copyright law, it should be said that forking code that isn't your own does not suddenly turn you from a licensee into a licensor. You can't take a BSD operating system, remove the BSD license, and attach the GPL for at least two reasons: 1) the BSD license forbids distributing sources (or binaries) without a copy of the license (which is the BSD license itself), and 2) you are not the copyright owner of any part of the BSD operating system you took, so you simply have no authority to (re)license it. You are automatically the copyright owner of whatever you create, including any patches or additions to the BSD operating system, and you can license your own stuff however you wish -- you can even distribute your own stuff alongside the BSD operating system using whatever terms you like for your own stuff which isn't necessarily allowed by the GPL because liberal licenses are awesome like that -- but you certainly never have any right to relicense anything that isn't yours.

    4. Re:Proposal: by kwerle · · Score: 2

      Oh SNAP! Nice one.

      (written from OSX...)

    5. Re: Proposal: by Anonymous Coward · · Score: 2, Insightful

      I license my code under a BSD license, maybe my thought process can help elucidate why someone would do this:

      My code does what it says it does. If someone relicenses it, people can always get my source instead. If someone improves it beyond what I did and people want that persons software instead, he's obviously added value to it and I feel he's within his moral rights to license that code anyway he wishes. He did something with it that I was unable, unwilling or too obtuse to do myself and I'm more then happy to see that because it means better software on the long run.

      If you're familiar with RMS's essay on 'open source' people versus 'free software' people, I'm firmly in the open source camp. Its a development model that produces better software, not a moral crusade.

    6. Re:Proposal: by smash · · Score: 1

      The core is still open source. The non-free proprietary bits of OS X have never been open source and were developed in house at NeXT / Apple.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    7. Re: Proposal: by Bert64 · · Score: 1

      At what percentage of "added value" does this thinking kick in?
      That is, if someone takes your code and adds improvements that make up say 5% of the codebase, then thats still predominantly your code and yet that person could be profiting from the entire package.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    8. Re: Proposal: by Anonymous Coward · · Score: 1

      If someone takes my code changes 5% and makes money off it while my -5% version is free for anyone to download and peruse, then he has obviously got some nice skills to deserve it even if just at marketing. Why should I profit from his original work if he doesn't want to share it? If I wanted/were able to profit from my 95% don't you think I would have done it already?

    9. Re: Proposal: by MikeBabcock · · Score: 1

      More importantly, as a user of person B's package, I have no ability to see those changes or how they achieved those upgrades and am stuck with the original source instead which lacks all those new features to work on my own improvements from.

      --
      - Michael T. Babcock (Yes, I blog)
    10. Re:Proposal: by Urkki · · Score: 1

      Who would want free BSD software relicensed under a shittier unfree license?

      Users of a fork or otherwise copied code, who would like to see the source.

      Developers, who see a bugfix or improvement of their code in a fork, and would like to merge that back to their codebase.

    11. Re:Proposal: by unixisc · · Score: 1

      Fork a BSD variant, license it under the GPL, package it with GNU stuff, call it Hurd 1.0.

      I suggested that for the microkernel - just take Minix 3, which is BSDL, fork it, license that under GPL3, package it w/ the HURD services and Emacs, and then call it HURD 1.0

    12. Re:Proposal: by caseih · · Score: 1

      It's a fine line here, though. I definitely can legally take your code that you released as BSD, extend or modify it, and release my version as GPL in its entirety. You still retain the copyright on your code, and of course someone could extract your code from my project and use it under the original BSD license. But I as a developer need not make much distinction.

      As for your claim the BSD requires the license to be distributed with the code, it doesn't actually say that (never uses the word, "license"). It says you must keep the copyright notice and "this list of conditions and the following disclaimer." The GPL actually satisfies all three of the conditions in the BSD. Copyright notice is maintained, the disclaimer of warranty is maintained, and the terms and conditions of the GPL are supersets of the BSD.

      So my reading, and the reading of the lawyers at the FSF is that yes, you may in fact relicense BSD code under the GPL (subject of course to what I said in the first paragraph).

    13. Re:Proposal: by drfreak · · Score: 1

      If you mean free as in the users can freely access the source code and it will always remain in such a state, then the GPL is freer..

      Is that "freer" as in "beer"?

    14. Re:Proposal: by drfreak · · Score: 1

      You must be new here. You forgot to add "Profit!"

  6. Relevance? by dreamchaser · · Score: 2, Insightful

    What exactly is relevant about Hurd now? The OS landscape has changed and people have moved on. This is really a non-story, aside from the humor value.

    1. Re:Relevance? by Anonymous Coward · · Score: 2, Interesting

      If that's how you think, you've chosen the wrong name. Maybe 'dreambasher' would be more appropriate.

      A small handful of technical people have a dream to make a viable microkernel operating system, and they're chasing their dream. Good for them.

    2. Re:Relevance? by jayrulez · · Score: 1

      XNU is not a microkernel.

    3. Re:Relevance? by hobarrera · · Score: 1

      "Moved on"? You make is sound as if Hurd was relevat once!

    4. Re:Relevance? by dreamchaser · · Score: 1

      It could have been relevant, once. That was a long time ago thought.

    5. Re:Relevance? by dreamchaser · · Score: 1

      Except it's been done already. It's cool that they are still chasing their dream, but it's hardly newsworthy now and not stuff that matters.

    6. Re:Relevance? by Guy+Harris · · Score: 1

      It's a hybrid, calling it a microkernel isn't entirely wrong since the microkernel structure is there, it operates as a microkernel with the message passing and protected memory, only it is not invulnerable to faulty device drivers, that's the key part that makes is a hybrid and why it retains a similar speed to pure monolithic kernels.

      I.e., it's a microkernel except for the "privileged OS services are provided by user-mode server processes rather than by code running in kernel mode" part, which makes it not much more interestingly a microkernel than, say, any of the monolithic-kernel UN*Xes that, in some cases, send messages to a userland process for some services (e.g., automounter daemons).

  7. I really hope it will run... by Nova+Express · · Score: 1

    ...on my PowerPC 620...

    --
    Lawrence Person (lawrencepersonh@gmailh.com (remove all "h"s to mail)

    http://www.lawrenceperson.com/

    1. Re:I really hope it will run... by Blaskowicz · · Score: 1

      Nope, the current plan is to support it on 68060.

  8. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  9. Re:The longest kernel development history... by deviated_prevert · · Score: 5, Funny

    ...of a kernel that doesn't actually work. Except on Stallman's PC.

    Stallman does not possess such devices he runs and developed emacs on a unix VM inside his brain! After realizing that all unix passwords and attempts to hide source code in a binary were useless. The concept of a conceptual computer without passwords and accessed only by obscure command macros written in C exploded from his mind and POOF we had emacs. This was then enhanced by interpreting the commands in binary form but it only worked for those who spoke with a lisp. Then all this went out the Windows when a stiff DOSe of source code was obscured by means of non standard compilers and suddenly word and data processing binaries could easily be obfuscated by hiding the source.

    Others tried to change this situation by judiciously applying rubber to source code and the resulting LateXT could be stretched into a usable FLEXable shape, at least until a Bison shat on the source. Stallman HURD about this change in how binaries were now being used and created and GNU for certain that he would have to come out of his brain and actually become the Kernel in charge of parsing things at the source. Because he still insists upon compiling source only in his brain before creating binaries the resulting OS kernel has been extremely slow to take shape because debugging it has given him nightmares whenever he actually sleeps in fact the that the sleep command causes instant dreams that bring him back to the Bill Gates rants he witnessed at computer club meetings in the 1970's.

    --
    This message was not sent from an iPhone because Peter Sellers really was a deviated prevert without a dime for the call
  10. From the NEWS file... by hpa · · Score: 1

    IPv6 support in pfinet, based on Linux 2.2.14.

    1. Re:From the NEWS file... by smash · · Score: 1

      Oh cool, I'll try and source an old 3c509 or NE2000 (and a motherboard with ISA or PCI slots) for network support.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    2. Re:From the NEWS file... by Anomalyst · · Score: 1

      Remeber, most 3c509b drivers will NOT work with the 3c509c,something about removing the way most drivers pulled the data from the card.

      --
      There is no right to feel safe thru security vaudeville at the expense of everyone's freedom, privacy and tax money.
    3. Re:From the NEWS file... by smash · · Score: 1

      Cool story bro. I prefer to buy hardware with a warranty and support for important things. And yes, friends don't let friends buy realtek NICs.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  11. I'm not a fan of Agile, but by Anonymous Coward · · Score: 1

    30 years to get to v0.5? Time to adopt Scrum.

  12. Re:GNU Hurd mobile? by Anonymous Coward · · Score: 1

    You have to admit with the recent news of Cyanogenmod selling out, there is an opening in the phone market for a truly free OS not controlled by some mega-corp.

  13. Stalling... by Anonymous Coward · · Score: 1

    I love the idea of GNU Hurd but it's just not progressing like it should.

    Does anyone know why this project is stalling so much?

    1. Re:Stalling... by aardvarkjoe · · Score: 1

      Does anyone know why this project is stalling so much?

      Because there's no strong need for it to be completed. It's progressing the same way as any number of hobbyist open source projects.

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    2. Re:Stalling... by jandrese · · Score: 1

      Because it has basically only a single developer (Stallman himself), and he has a bad case of Carpel Tunnel so to write it he has to dictate every character to some poor intern that then quits because that's an impossible way to develop a project.

      --

      I read the internet for the articles.
    3. Re:Stalling... by Bitmanhome · · Score: 3, Funny

      Does anyone know why this project is stalling so much?

      Cuz it's run by a Stall-man?

      --
      Not that this wasn't entirely predictable.
    4. Re:Stalling... by smash · · Score: 1

      Because both Linux and xBSD already exist, are stable, and have far better performance, hardware compatibility and real world testing.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    5. Re:Stalling... by dbIII · · Score: 1

      Management style. If you want to contribute it's as if they'll ask you where you got your doctorate in CS in, and even if it's the same place as somebody already involved they'll then ask what year then reject you.
      IMHO that's why linux took off and hurd didn't. Linus would take any code that looked like it would fit from anyone that wanted to send it in, then sorted out the rough edges with the help of what became a huge number of people.

    6. Re:Stalling... by otuz · · Score: 1

      Because there's already an awesome open-source Mach kernel out there: XNU, and it ships with most Apple devices.

    7. Re:Stalling... by iggymanz · · Score: 1

      no, show me a hobbyist open source project that went 27 years with nothing usable.

      Even Perl 6 hasn't yet sunk to those depths, though it is passing downward to the ocean floor much like a broken Titanic

    8. Re:Stalling... by aardvarkjoe · · Score: 1

      no, show me a hobbyist open source project that went 27 years with nothing usable.

      Head over to sourceforge and start clicking on random projects. Half-finished projects with minimal practical use are common. The only real difference is that the Hurd gets lots of press despite its state.

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    9. Re:Stalling... by unixisc · · Score: 1

      Not only that, RMS no longer endorses HURD - he switched to trying to rebrand Linux as GNU/Linux a long time ago

    10. Re:Stalling... by mr_mischief · · Score: 2

      Perl 6 makes progress. It's slow, but it's fairly steady. There has never been a one-year gap in packages, let alone ten years. One of the compilers, Rakudo, is nearly feature complete and then just needs to be optimized. It has monthly releases.

  14. Re:Not a replacement for Unix kernel by Jeremy+Erwin · · Score: 5, Funny

    I'm looking forward to the Alpha port, though I'm also hearing good things about Itanium.

  15. Have you HURD? by skaralic · · Score: 1

    It was my understanding that everyone had HURD...

    1. Re:Have you HURD? by smallfries · · Score: 1

      Are you referring to the recent news of an avian variety?

      --
      Slashdot: where don knuth is an idiot because he cant grasp the awesome power of php
    2. Re:Have you HURD? by 3dr · · Score: 1

      Oh, perhaps of a certain ornithological topic.

  16. Re:Microkernel by Anonymous Coward · · Score: 2, Insightful

    What does GNU Hurd have that Minix 3 does not? They are both microkernels except Minix 3 looks more mature.

    GNU Hurd uses a sane license. Minix 3 uses a BSD license, which is unfree.

    That's hilarious. (I don't mean just the bit where, like so many FSF fanboys, but not RMS, you can't grasp the difference between "Free" and "Copyleft"; I mean the argument as a whole.)

    So HURD's only benefit (that you can think of) is that if some evil company wants to take a microkernel-based UNIX-like, make their changes, and distribute the result without source... they'll be forced to go with Minix 3 (the one that GP says "looks more mature", which you don't seem to dispute) instead of HURD (which you can't or won't explain any technical benefit of)? Yeah, I think they'll just go with Minix 3, same as they would no matter how you licensed HURD.

  17. Re:When you do this as a hobby by Guy+Harris · · Score: 4, Insightful

    things tend to go slow. Real slow. If you want things now, now, now, pay the man/men. It is free, as in someone-else-will-do-it, so you get what you, that's right, didn't pay for.

    Fortunately, eventually people found this hobby project worth paying for, although I think it proved its worth before the big money started pouring in.

    There are, of course, some other hobby projects that also manage to support a little more hardware than the Hurd does without huge amounts of money poured into them.

  18. You're kinda right... by Anonymous Coward · · Score: 1

    You have to include the original copyright notice and the terms that pertain to that code. But you can certainly distribute BSD code within/alongside your own code under your own license. That's kinda the point of the BSD license.

    Just sprinkle few patches throughout the codebase that are difficult to strip out, and your new project becomes de facto GPL.

  19. Re:Microkernel by Anonymous Coward · · Score: 1

    It's the other way around.

    Minix3 is a Pure Microkernel Multiserver system, using a custom microkernel. The kernel is small and everything else runs contained in userspace processes.

    HURD is a hybrid system, which means drivers run in kernelspace, negating most of the benefits of using a microkernel in the first place. This is a consequence of using Mach, which has severe performance issues which pretty much exclude its use on a pure microkernel architecture system.

    Other Mach-based systems such as Darwin (used on OSX and IOS) are also hybrids, for the same reasons.

    But Mach is pretty much an ancient, archaic microkernel. L4 showed the world that the whole microkernel thing can be done in a reasonably efficient manner.

  20. i wonder which will be production ready first by Chrisq · · Score: 1

    Gnu Hurd or Minix 3

    1. Re:i wonder which will be production ready first by unixisc · · Score: 1

      I thought Minix 3.4 is already ready. It has Minix at the bottom, and NetBSD userland.

    2. Re:i wonder which will be production ready first by Chrisq · · Score: 1

      I thought Minix 3.4 is already ready. It has Minix at the bottom, and NetBSD userland.

      you must have jumped ahead, they are at 3.2.1 and it has very limited software and hardware support

  21. Because the Mach approach still doesn't work well by Anonymous Coward · · Score: 1

    And never has. Apple got a Mach *based* kernel working by having complete hardware control and not having to develop drivers for alternative hardware. The Linux, kernel, and BSD kernels that are atually in use on broad sets of kernels, accepted the risk of having the drivers inside the kernel so that they could get them to actually *work*.

  22. Hurd may have been a failure by nurb432 · · Score: 1

    As a 'product' it may be a dismal failure, but the work getting to it has clearly been not and we every day enjoy the 'collateral successes'.

    For all his faults, RMS did help the 'movement' in incalculable ways.

    --
    ---- Booth was a patriot ----
  23. Release early, release often by benjfowler · · Score: 1

    That's how we roll.

  24. Re:GNU Hurd mobile? by MikeBabcock · · Score: 1

    Says who? Cyanogenmod taking money from the public is fantastic and means more time working on the project we love.

    --
    - Michael T. Babcock (Yes, I blog)
  25. Re:Microkernel by fnj · · Score: 1

    BSD license, which is unfree

    Bullshit. It's as free as it gets. It's the definition of free. You can do anything with BSD material, including proprietize derived works. That conflicts with some people's concept of subsuming derivative work and making it as open as the original free bits, but that doesn't allow redefining "free" as "free, and forcing yours to be free, too".

  26. Re:Microkernel by fnj · · Score: 1

    And if Mach's architecture entailed a high overhead on a 16 MHz single core 16020, it would be utterly negligible on today's 3 GHz four core CPU.

  27. Re:Because the Mach approach still doesn't work we by fnj · · Score: 1

    And never has. Apple got a Mach *based* kernel working by having complete hardware control and not having to develop drivers for alternative hardware. The Linux, kernel, and BSD kernels that are atually in use on broad sets of kernels, accepted the risk of having the drivers inside the kernel so that they could get them to actually *work*.

    And why, pray tell, is developing reliable drivers for a microkernel more difficult than for a monolithic kernel? Logic would dictate entirely the reverse.

  28. Re:Not a replacement for Unix kernel by iggymanz · · Score: 1

    and don't forget about the PPC port on that site, with posts all the way into 2003, that project is on fire by HURD standards. We'll finally be able to run HURD on our Macs........*!* oh wait.......

  29. He has the source right? by ArchieBunker · · Score: 1

    Why should he be worried since he has the source code? Another bombshell for you guys. His systems did not even have passwords until an untrustworthy worker started fucking around.

    --
    Only the State obtains its revenue by coercion. - Murray Rothbard
  30. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  31. Re:Not a replacement for Unix kernel by unixisc · · Score: 1

    I once noted that the best CPU for pure FSF/GNU stuff would be a VLIW CPU. Since all the dynamic analysis is done by the compiler, every time a CPU undergoes changes, backwards compatibility should be broken. Bigger register set? Recompile. More branch units? Recompile. More ALUs? Recompile. With all that recompiling that is needed, the FSF goals of software being completely liberated in terms of the source code being always available would be more successfully enforced.

    Not that that would apply to the Itanium, since that CPU has become more RISC in Itanium 3 than it initially was.

  32. Re:The longest kernel development history... by unixisc · · Score: 1

    His PC doesn't run HURD - it runs gNewSense, a distro of what he calls 'Libre-Linux'

  33. Re:In a seperate announcement by unixisc · · Score: 1

    Actually, the perfect pure GNU system - HURD on an Itanium (or a real VLIW CPU), w/ Emacs on top of it as well as GNOME 3. Only impurity here - X11, which isn't GPL3. Maybe they can try and do a GPL variation of either X11 or Wayland or Mir, whichever they prefer.

  34. Re:GNU Hurd mobile? by mr_mischief · · Score: 1

    I'm curious. How much time and money would using the goo.im updater save for work on other things?

  35. Re:Not a replacement for Unix kernel by Jeremy+Erwin · · Score: 1

    Yes. It would be the perfect cpu for a gentoo style OS. But from what I heard, Itanium failed to live up to its promise because the compilers, particularly gcc. weren't that good at optimization.

  36. Re:unix desktop by Nick · · Score: 1

    not sure why this got modded down. Has anyone ever tried to setting up three monitors? I recently converted my workstation from Windows which worked quite well for gaming and multi-monitor support. On-board nvidia gpu had one monitor and the amd/ati pci card connected the other two. Can't do that under X. So now I'll have to buy another PCI card. But wait, commercial drivers are buggy and Xscreensaver is a mess, I can't use text virtual consoles, but I use open source drivers which fixes that, steam wont run. Running Ubuntu? Having the fear of god every time a system update or reboot is not ideal, but about half the time something bad will happen. BSD? nothing is written for it. I've been running X in some form on some machine since the early 90s on a 386. For a while, the unix desktop was the way to go, but for years Windows or OS X is vastly superior in a desktop environment - you know, actual drivers exist. Thank god for virtualbox at least.

    --
    Fuck Ajit Pai
  37. Re:Because the Mach approach still doesn't work we by Guy+Harris · · Score: 1

    And never has. Apple got a Mach *based* kernel working by having complete hardware control and not having to develop drivers for alternative hardware.

    ...and by running drivers for network and storage devices, and the network protocol and file system code that uses them, in kernel mode.

  38. Re:The longest kernel development history... by unixisc · · Score: 1

    Actually, one good way of slowing down GNOME would be to ask that team to port it directly to HURD, w/o going through X or Wayland or anything else. In fact, build a display server directly into either HURD or GNOME. Preferably GNOME, since that would be quicker.