Slashdot Mirror


GNU Hurd 0.6 Released

jrepin writes It has been roughly a year and a half since the last release of the GNU Hurd operating system, so it may be of interest to some readers that GNU Hurd 0.6 has been released along with GNU Mach 1.5 (the microkernel that Hurd runs on) and GNU MIG 1.5 (the Mach Interface Generator, which generates code to handle remote procedure calls). New features include procfs and random translators; cleanups and stylistic fixes, some of which came from static analysis; message dispatching improvements; integer hashing performance improvements; a split of the init server into a startup server and an init program based on System V init; and more.

39 of 229 comments (clear)

  1. Mandatory xkcd by NotInHere · · Score: 5, Funny
    1. Re:Mandatory xkcd by ClickOnThis · · Score: 2

      2060: the year of the GNU Hurd desktop?

      --
      If it weren't for deadlines, nothing would be late.
    2. Re:Mandatory xkcd by Shillo · · Score: 4, Funny

      Well, re-read the summary. They introduced a real SysV init.

      Systemd integration is the obvious next step for HURD.

      --
      I refuse to use .sig
    3. Re:Mandatory xkcd by sethradio · · Score: 3, Funny

      Why do people dislike systemd so much?

      --
      "Nationalism is an infantile sickness. It is the measles of the human race." -Albert Einstein
    4. Re:Mandatory xkcd by Anonymous Coward · · Score: 2, Informative

      Because learning new software is haaaaarrrd! Much easier just to complain about it.

    5. Re:Mandatory xkcd by Anonymous Coward · · Score: 5, Informative

      Actually I was pretty happy with the systemd learning curve. What I wasn't happy about was not being able to figure out why my network interface insisted on getting a DHCP address despite the fact I had explicitly disabled DHCP and assigned a static IP address to it via the unit files, because *there was no log of what unit/configuration files were being executed/read and when*, and - as far as I'm aware - there is no way to enable logging or figure out exactly what is going on.

      And just think, with System V Init or RC scripts I could have just added a few "echo" statements to figure out what was going on instead of Googling for several hours until I found what the actual problem was.

      THAT is what is stupid about systemd.

    6. Re:Mandatory xkcd by TWX · · Score: 3, Interesting

      Well, I dislike it because it makes it much harder to administer a box as a UNIX-type machine with a simple text editor. Now it seems like I'm stuck with meta-scripts invoking meta-scripts invoked by other scripts to do something as simple as changing my DNS servers. A whole lot of stuff just got a lot harder because of an abstraction layer.

      --
      Do not look into laser with remaining eye.
    7. Re:Mandatory xkcd by Anonymous Coward · · Score: 2, Informative

      And...it's obvious you've never administered a systemd box....or tried...or even read about systemd or unit files/services.

      It's so ridiculously easy to make nice clean dependencies so that my service starts up when it should only when it should, without needing anything more than VIM to write them in maybe 10 lines per unit file.

      For example, I have a service that just runs a binary (an rpc type server). There's a single line, in the *text* file (because that's all there is), telling it that when the binary exits, then the service has closed. There's also a single flag that I have set that restarts the service if the binary ever exits. (yay, automatic restart and logging)

      Then there's a list of different types of dependencies at the top. My script should not start without networking, it also shouldn't start before some helper services, and it depends on a kernel module device, so all of those are listed *one line each, maybe 15 characters*.

      I also have a simple unit for that device driver, so that whenever I load or unload the device driver, it fires up fire up or kills the service, and all of the dependencies, automatically.

      Not a "make sure it has time" type sleep needed anywhere because *that would mean my startup was fundamentally broken* (and it's rare to *not* see them in old boot scripts).

      When I'm debugging new builds, I just do "systemctl --failed" and it gives me a nice list of what services failed and why. Then "systemctl status " for more details, with a bit of log message.

      You can stay in the stone age and grep your text log file (which systemd also dumps its messages to by default on most distributions), or you could just do "journalctl -u --this-boot" and see exactly what happened in a nice clean live and navigatable format.

    8. Re:Mandatory xkcd by Anonymous Coward · · Score: 2, Insightful

      Why is the above post marked troll?

      Maybe because people are getting tired of systemd posts on every single story, regardless of whether it is a story about the latest news from the LHC or an update on the new Star Wars movie. They are not simply off-topic posts, but are like are the racist or anti-feminist rant posts that are also made trying to get people arguing about off-topic BS, i.e. trying to troll for a reaction.

      why not state you should have fill in the blank here and make him look like an idiot versus marking him as a troll?

      The post seems to follow a common pattern of people claiming it can't log stuff that it can log. For the first couple months you could find detailed replies telling people how to enable things that they perpetually claimed were not possible, but after a while I think the helpful sorts realized a significant fraction of such posts had to be trolls. After all, off-topic threads on Slashdot is not the place to come to fix your system configuration.

      Seems like someone advocating systemd is marking anyone they disagree with troll.

      Seems like someone is marking both pro and anti systemd posts as trolls.

    9. Re:Mandatory xkcd by sjames · · Score: 4, Insightful

      There are many reasons:

      It doesn't play well with others. It works well enough with a use case that exactly matches the expectations of the developers, but put a toe outside that and you're in for some genuine hell. It takes a nice modular system and turns it into an all or nothing hairball of dependencies.

      People keep claiming it's simple, but they never seem to notice the big pile of crap in /lib/systemd, /var/lib/systemd, etc etc.

      It takes a joke like the "COME FROM" statement and actually implements it!

      It won't quit metastasizing.

      There is nothing it does that couldn't be implemented in a truly modular and far less invasive way.

      It's a solution looking for a problem.

    10. Re:Mandatory xkcd by CronoCloud · · Score: 4, Informative

      Well, I dislike it because it makes it much harder to administer a box as a UNIX-type machine with a simple text editor. Now it seems like I'm stuck with meta-scripts invoking meta-scripts invoked by other scripts to do something as simple as changing my DNS servers.

      I run Fedora 21, a systemd distro. You want to change your dns servers on Fedora 21?

      You can use the Network GUI thing nm-connection-editor or whatever equivalent your desktop uses.

      Or if you prefer the terminal or console you can use nmtui which is the same thing in a terminal/console

      Or you can
      vim /etc/resolv.conf That still works. You might still need to reset the connection after the change.

      Or you can:
      nmcli con mod connection-name ipv4.dns "8.8.8.8 8.8.4.4"

    11. Re:Mandatory xkcd by devent · · Score: 4, Insightful

      That's why people want systemd. If I look at sysvinit scripts, there are a ton of magic stuff going on that I don't know, and maybe nobody knows. On Ubuntu 12.04 the sysvinit script for Apache is over 7000 bytes long, and it includes bad stuff like "# wait until really stopped" with a loop of kill and sleep. The ClamAV init script is even bigger, over 9000 byes long. Is there any maintainer who really knows what it does?

      --
      http://www.mueller-public.de - My site http://www.anr-institute.com/ - Advanced Natural Research Institute
    12. Re:Mandatory xkcd by Eunuchswear · · Score: 2

      This is about GNU Hurd -- everything is a userspace process.

      (And, of course systemd is a userspace process on Linux anyway).

      --
      Watch this Heartland Institute video
    13. Re:Mandatory xkcd by muirhead · · Score: 3, Insightful

      Why do people dislike systemd so much?

      It is largely down to terrible marketing and poor public relations. We all need to have someone to hate.

    14. Re:Mandatory xkcd by pla · · Score: 2

      Nothing wrong with learning new software. When new software brings great features to the table or when it fixes long-standing and hard to squash bugs - Great!

      Learning new software because OMGSHINYNEWPONIES, however? Fuck that. Particularly when the new ponies merely usurp preexisting functionality into a more fragile, unrecoverable environment. When the new ponies mean relatively minor configuration tweaks mean a reboot. When the new ponies speak a language only they can understand, and to hell with all of you who see any benefit in human-readable. When the new ponies have uncontrollable Tourrette's syndrome and like to spew random unintelligible obscenities at the user for no obvious reason and with no warning. When the new ponies don't actually do anything we couldn't do before. When the only reason we even have this discussion on the table involves NIH syndrome at RedHat.

      An init system should do as little as possible, and do it well. Systemd ain't that.

    15. Re:Mandatory xkcd by Rob+Riggs · · Score: 2

      It's a GNU project. Eventually it will morph into "self-hosting Emacs" because that's the only thing that Stallman understands.

      --
      the growth in cynicism and rebellion has not been without cause
  2. Both users by Anonymous Coward · · Score: 5, Funny

    It was rumored that both users could be hurd rejoicing.

    1. Re:Both users by Lunix+Nutcase · · Score: 4, Funny

      So its user base has doubled? Amazing!

  3. Microkernal Boner by Greyfox · · Score: 2, Funny
    Aah, I remember back in the late 80's and early 90's everyone had a boner for microkernels. IBM even gave it a try, attempting to port OS/2 over to a microkernel so they could run it on Intel and PowerPC platforms. At one point, IBM's strategy was that they were going to build OS/2 around a microkernal and then just run THAT on all their hardware, with multi-user and security features added or removed as needed. Well, very long story, very long, they never could get it to work.

    These days you don't see the same hype around microkernals that you did back then. So we should probably warn the HURD team: If your boner for microkernals lasts more than 25 years, you should probably consult a physician.

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

    1. Re:Microkernal Boner by AchilleTalon · · Score: 2

      Obviously you got the story from a third hand. That is not what happened at all and certainly not due to deficiencies in the microkernel technology.

      --
      Achille Talon
      Hop!
    2. Re:Microkernal Boner by qpqp · · Score: 4, Informative

      If your boner for microkernals lasts more than 25 years, you should probably consult a physician.

      I recommend a look at Andrew S Tannenbaum's baby:

      MINIX 3 is a free, open-source, operating system designed to be highly reliable, flexible, and secure. It is based on a tiny microkernel running in kernel mode with the rest of the operating system running as a number of isolated, protected, processes in user mode. It runs on x86 and ARM CPUs, is compatible with NetBSD, and runs thousands of NetBSD packages.

      Minix

    3. Re:Microkernal Boner by Guy+Harris · · Score: 2

      That explains why Windows NT and OS X never got anywhere, considering that one was based on Mach and the other actually uses Mach.

      Now, in Windows NT and OS X all the modules ran in the same address space. But they didn't call each other directly. They used the same generic messaging API that modules would from user space, there's just wasn't less overhead in passing the messages. But those examples are ancient history.

      Not sure what "modules" you're referring to, but if you're referring to "modules" such as network protocols and file systems in OS X, they most definitely are called directly from the system call layer. Go take a look at the kern , net , and vfs directories of XNU, as well as the netinet directory of XNU and the source to the FAT file system kernel module for examples of code that plugs into the BSD-flavored socket layer and VFS mechanism.

      As for the drivers they sit atop, those are called by Boring Old Procedure Calls (and method calls, given that IOKit uses a restricted flavor of C++), not by Mach message passing.

      As far as I know, network protocols, file systems, and network and storage device drivers work similarly in NT.

  4. 0.6? Are you serious? by msobkow · · Score: 5, Insightful

    They announced work on Hurd when I was still in university. I've worked a career, ended up disabled, retired, and spent years on a pet project since then, producing 13 point releases. Over 30 years have gone by.

    Yet they've still only reached release 0.6? So one decimal point release every FIVE YEARS?

    Jesus.

    Stick a fork in this project.

    It's done -- as in dead. Pushing up daisies. Pining for the fjords. Defunct. Deceased. Non functional.

    It's not even worthy of being called a pipe dream any more. Even "Duke Nukem' Forever" beat them to the punch, and everyone gave up on that project long before it was released.

    --
    I do not fail; I succeed at finding out what does not work.
  5. Too bad... by TsuruchiBrian · · Score: 5, Funny

    It's too bad Linus wasted all this time making a temporary kernel that was just going to be surpassed a mere 24+? years later by the official GNU kernel. Nothing stings more than when the code you write isn't being used.

  6. Re:I want to try it by Lunix+Nutcase · · Score: 3, Interesting

    Well Hurd did not get the developer attention that Linux got. Obviously, this means that progress in Hurd is going to be slower than Linux.

    MenuetOS has less than a handful of developers and yet has had USB support for at least 7 years now.

  7. Re:I want to try it by ThePhilips · · Score: 2

    Writing drivers isn't hard.

    But for the broader acceptance of an OS, one needs a whole shitload of them.

    In the past, a computer with a half dozen devices was "packed". Today? A cheap tiny ARM SoC easily runs up to 30+ built-in devices.

    --
    All hope abandon ye who enter here.
  8. Re:systemd by ClickOnThis · · Score: 3, Informative

    From the GNU Hurd Wiki page:

    It's time [to] explain the meaning of "Hurd". "Hurd" stands for "Hird of Unix-Replacing Daemons". And, then, "Hird" stands for "Hurd of Interfaces Representing Depth". We have here, to my knowledge, the first software to be named by a pair of mutually recursive acronyms.

    —Thomas (then Michael) Bushnell

    --
    If it weren't for deadlines, nothing would be late.
  9. Re:For me, there are two questions. by ckatko · · Score: 4, Insightful

    Who the hell works on the 99% of open source software that isn't popular, and why do they care? Because they do.

  10. Re:0.6? Are you serious? by Anonymous Coward · · Score: 5, Funny

    He hasn't finished his answer yet. Check back in a few years.

  11. Re:Why do people dislike systemd so much? by Foresto · · Score: 3, Informative

    The reasons for disliking it vary, but there is at least one common thread among those who are upset about it: Systemd is being shoved down their throats, in that several of the most widely used, widely loved, deeply entrenched linux distributions have announced that they are adopting it. Many people who use those distributions do so for very good reasons, and since there are no equivalent alternatives, these people are being forced to either accept systemd (which will cause them unwanted trouble) or migrate to an inferior distribution (which will also cause them unwanted trouble). That kind of thing is enough to piss anyone off.

  12. Not good enough. by westlake · · Score: 2

    Who the hell works on the 99% of open source software that isn't popular, and why do they care? Because they do.

    Show me some proof that anyone cares enough to drive GNU/Hurd to a 1.0 release.

    Richard Stallman founded the GNU project in September 1983 with an aim to create a free GNU operating system. Initially the components required for kernel and development were written: editors, shell, compiler and all the others. By 1989, GPL came into being and the only major component missing was the kernel.

    In 2010, after twenty years under development, Stallman said that he was ''not very optimistic about the GNU Hurd. It makes some progress, but to be really superior it would require solving a lot of deep problems'', but added that ''finishing it is not crucial'' for the GNU system because a free kernel already existed (Linux), and completing Hurd would not address the main remaining problem for a free operating system: device support.

    GNU Hurd

  13. Re:Why do people dislike systemd so much? by devman · · Score: 4, Interesting

    The problem is when you fork your own distro you quickly discover that using systemd is the easiest way to maintain it. It isn't a coincidence that medium and small distros like Arch Linux picked it up in addition to the big boys. Unit-files save package maintainers boatloads of time they used to spend having to writing and maintaining initscripts a lot of which is copypasta boilerplate anyway but its usually distro specific copypasta.

    This is the source of a lot of the strife in my opinion. The people who actually do work to maintain distros like systemd, the users not so much.

  14. Interesting discussion by peppepz · · Score: 5, Insightful

    101 posts and not a single one with technical content. Somebody should create a slashdot post generator, with modules producing output of these kinds:
    - internet meme repeater ("year of Linux on the desktop", "stallman eats his own toes", "thou shalt not compare to nazi");
    - xkcd repeater (its output is prefixed by the string "obligatory" and displays a strong prevalence of this one);
    - project deprecator ("this software is so stupid, I could write a better one with one arm tied behind my back, except I'm too smart to actually do it");
    - Google/Apple/Microsoft PR ("it's not Google who kills kittens! It's their subcontractors!");
    and, last but not least,
    - Slashdot deprecator ("slashdot is no longer a nice site to read these days").

  15. Re: Why do people dislike systemd so much? by Hognoxious · · Score: 2

    Maintaining init spaghetti scripts is no fun, not easy either.

    Been a while since I had to do it, but I don't recall it being that hard. I did have to look at a book.

    But that's not the point. If systemd was just an init system and nothing but an init system, so help it God, people could either take it or leave it. They'd have the choice, one way or the other.

    The problem is that when it has dependencies on your window manager, microwave & healthcare plan you can't simply unplug it and replace it with something else.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  16. Re:I want to try it by serviscope_minor · · Score: 3, Interesting

    Ah, it's turned into a "let'smake our selves feel important by shitting on someone't hobby" day.

    Yeah USB only a few years ago. Their goal is to write a microkernel OS and figure out how to make it work well for a UNIX like system with far more felxibility. The feature list and malleability of the system is impressive.

    If they spent all their times on drivers and none on the base OS, they'd have yet another OS which is quite similar to all the others out there in terms of features. Their goal is not to get acceptance from random bitter blowhards like yourself on the internet.

    End result: they've contributed more to the world than you ever will.

    --
    SJW n. One who posts facts.
  17. Re:0.6? Are you serious? by ledow · · Score: 2

    If the problem is solved, then move the development focus elsewhere. And I thought that FSF didn't actually like the idea of GPL2-only things?

    However, the FSF development focuses are odd and abandoned.

    For years a Skype-replacement was asked for. Apart from game-server-oriented once like Mumble, I can't see a viable OS alternative that works cross-platform, with video, etc. We could say that Jabber's use by Google Chat was the replacement but - again - why are we then continuing on the others?

    For years, a Flash replacement was asked for. Last I checked, Gnash could do some things but nowhere near all.

    Coreboot was asked for, but it's a REALLY niche project and whether that supports UEFI etc. I don't know.

    Google Earth replacements, Matlab replacements, OpenDWG library (odd choice, I think), Oracle Forms replacements, all suffer the same problems.

    And "automatic transcribing" is just silly and shouldn't be a priority at all.

    The FSF's priorities are basically ignored and people work on what they enjoy working on. That's great and all, but HURD has been a long-time coming and can just barely run something approaching a Linux distribution. Given that it's replacing a kernel only - and userspace can be things like Debian software etc. - that seems an awful long time. Don't even get me started on filesystem or hardware support for Hurd.

    Sometimes you just have to say "Oh well", and cut off the project. The people working on it would be much more useful on other projects that may well end up on machines worldwide rather than niche toy projects that have taken decades to get close to fruition. Not all of them would move, of course, but at least some of that talent could re-focus to other projects that are of greater utility.

  18. Re:For me, there are two questions. by DrXym · · Score: 4, Insightful
    The debate about micro or monolithic kernels was just a backdrop. The real reason HURD failed had more to do with the mindset of the people involved.

    Linus (impatient with the pace of HURD) developed a quick and dirty kernel that a Unix user land could be built on top of. He took a lot of shortcuts, he didn't think too much about portability and basically just made a beeline for the end line - to get a shell and hence other stuff running over a kernel. The kernel filled out and became portable as the project gained momentum and volunteers.

    Whereas HURD got stuck up its own ass for correctness and politics. And that's even before Linux existed as a thing. It's hardly a surprise that when Linux did appear that people jumped ship.

    It's true there was a debate about micro kernel designs but that alone doesn't explain HURD's failure.

  19. Does it now support HDDs larger than 2 GB? by Qbertino · · Score: 4, Insightful

    Does it now support HDDs larger than 2 GB? I'm not even joking here.

    Last time I heard (like 10 years ago or so) it was a theorists wet dream but basically unusable.

    What's the state of things with Hurd nwo? Is it usefull already?
    What are big steps Hurd still needs to take to be ready for prime time?
    What are the plans? When are we there?

    Please note: I have no problem replacing Unix with something better, like ome coolDMI thing where everything isn't a file but an object and the system is cleanly designed from top to bottom and back. Top notch but everything modifiable. But it has to be real-world usable and useful. Until then I'm sticking with *nix derivates such as OS X on Apple hardware or some x86 Linux like Debian or Ubuntu on ThinkPads.

    Could someone give some enlightenment on this issue?

    --
    We suffer more in our imagination than in reality. - Seneca
  20. Re: Why do people dislike systemd so much? by devent · · Score: 2

    No, it does not. The Window Manager have dependency on systemd, not the other way around. If the Gnome developers deciding that they need systemd, it's not systemd fault. You are free to open a bug ticket, but in the end it's the decision of the Gnome developers to use a particular technology.

    --
    http://www.mueller-public.de - My site http://www.anr-institute.com/ - Advanced Natural Research Institute