Slashdot Mirror


GNU/Hurd Delayed To Fix Disk Size, Serial I/O Limitations

gregger writes "This Infoworld article indicates that the GNU/Hurd is still waiting to stampede. Evidently they have to switch from the GNU Mach implementation they're using now to OSKit's Mach which will help them support faster serial I/O and larger hard discs. Currently GNU/Hurd will only support somewhere between 1 to 2 GB partitions."

253 of 552 comments (clear)

  1. Re:GNU/Hurd by Anonymous Coward · · Score: 5, Funny

    GNU *is* GNU/Linux. Except for this tiny itty-bitty kernel that some guy wrote, which we only took 19 years to get around to doing.

    -RMS

  2. Hurd delayed? by Anonymous Coward · · Score: 5, Funny

    I'm shocked! SHOCKED!

  3. Delayed??? by Servo · · Score: 2

    HURD has been in the works for over 20 years. This is starting to sound like "delays" on the Big Dig.

    --
    A slip of the foot you may soon recover, but a slip of the tongue you may never get over. -Benjamin Franklin
    1. Re:Delayed??? by 1010011010 · · Score: 2


      And after "20 years," they switch to someone elses' microkernel...

      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    2. Re:Delayed??? by gmack · · Score: 5, Interesting

      I actually watched Stallman speak in Montreal recently. One interesting tidbit was that he still seems dumbfounded about the fact that the Linux kernel beat them into production even though one of the advantages of microkernel is supposed to be ease of design and the fact that mach had half of the work done already.

    3. Re:Delayed??? by Servo · · Score: 5, Insightful

      The biggest issue is that Stallman is an idealist. Torvalds just wanted a working Unix-line OS.

      --
      A slip of the foot you may soon recover, but a slip of the tongue you may never get over. -Benjamin Franklin
    4. Re:Delayed??? by Zeinfeld · · Score: 3, Interesting
      I actually watched Stallman speak in Montreal recently. One interesting tidbit was that he still seems dumbfounded about the fact that the Linux kernel beat them into production even though one of the advantages of microkernel is supposed to be ease of design and the fact that mach had half of the work done already.

      I have to think that the Hurd is a case of following the fashion rather than evaluating the microkernel technology on its merits.

      There are lots of folk out there who will blather on at great length about the merits of kernel design for absolutely no other reason than they think it makes them look clever.

      I have not done anything at the O/S level since writing one ten years ago (unless you count the Web as an O/S). At that time Mach was flavor of the month because OSF and Next had used it as the basis of their operating system and Cutler had used a lot of the concepts of Mach to design his follow on operating system to VMS. Then Rashid joined Cutler at Microsoft in a very high profile move.

      So yes microkernels were flavor of the month ten years ago. However the reason why they were flavor of the month had more to do with the politics and problems at the time.

      OSF was trying to build a kernel quickly to compete with System V. Microsoft was building Windows NT to get to market as fast as possible. Microkernels were touted as the equivalent of RISC in CPUs, a design that allowed for shorter development time and hence faster to market.

      Microsoft had another issue, they wanted to be able to emulate other O/S. In particular Posix so they could sell in the federal market. They also wanted to be able to migrate VMS to run on WNT at a later date as a subsystem. This is actually in the works now and will take place when HP transitions from Alpha to Itanium on the high end server line. One of the reasons Microsoft was keen to do this is that Cutler and his principal staff had left Dec after Dec cancelled the Prism project, Cutler's objective stated at the time was to make Dec have to pay for the O/S they could have had for free. At the time Dec was bigger than Microsoft.

      There are advantages to microkernels, but the NT design has not been pure microkernel for some time. In order to get acceptable performance on early hardware they had to allow the display drivers to run in kernel mode.

      The problem that I think will prevent HURD ever working is that to build a real O/S you have to really understand the reasons behind the principles you follow and break them when necessary. RMS is unfortunately a prisoner of many dogmatic beliefs which once fixed he simply will not abandon regardless of the evidence.

      Linus may or may not have known what he was doing when he had the argument with Andy Tannenbaum, but he made the right decision. Andy has written a lot of good books that are widely used as text books, I don't know if people like Cutler, Rashid, Hoare and Co would rate him as being in the front rank. It is the same situation in most fields, everyone has heard of Bruce Schneier, fewer have heard of Ron Rivest and only people in the field tend to know names like Paul Kocher (SSL 3.0, the one that works), Butler Lampson (ACLS, lotsa stuff), Clark (end to end principle), Bellovin (firewalls), Schiller (IETF Security Area director).

      Oftopic: Mark Goldston, CEO of United Online (Juno/blue light) is a clueless dweeb, he just tried to tell Mark Haynes on CNBC that cable modem router boxes are not a threat to his business as few people can afford them... Not only are WiFi cable routers $100 at frys they will be built into the cable modems soon. So either he is uninformed (unlikely) or another lying CEO.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    5. Re:Delayed??? by abigor · · Score: 2

      I had no idea about the VMS emulation plans in the NT kernel. Excellent post, thanks.

    6. Re:Delayed??? by Zeinfeld · · Score: 2
      I had no idea about the VMS emulation plans in the NT kernel. Excellent post, thanks.

      It isn't emulation, the next version of VMS is Windows NT. Basically VMS will become a WNT service in the same way POSIX and Windows are currently layered.

      No idea how much this will cost, most likely quite a bit more than WNT. However VMS is available for non commercial use effectively for free. You just have to join DECUS user group - the US version is expensive but there are foreign chapters that are free.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    7. Re:Delayed??? by Archfeld · · Score: 2

      port VMS to run on NT ? Didn't they just announce the END of the support cycle and the dropping of if as a product. Checking with our DEC^H^H^H COMPAQ^H^H^H^H^H, HP rep he seems to follow the same line of thought. I can find several references to your point on the web but we've been told VMS is dead. According to M$ life cyclepage http://www.microsoft.com/windows/lifecycle.mspx NT is entering extended only support as of June 30, 2003, and end of life cycle is 1 year later. Hardly the kind of project to commit lots of resources to.

      --
      errr....umm...*whooosh* *whoosh* Is this thing on ?
  4. Re:GNU/Hurd by myowntrueself · · Score: 2, Insightful

    presumably theres
    GNU/Linux
    and
    GNU/Hurd

    Thing that bugs me about this is that the pace of hardware technology obsolescence is such that if it takes more than 2 months to develop a new OS, you can't go out and buy new (as opposed to second hand) hardware to run it on... because all the new hardware thats available is incompatible with what you were developing for.

    I reckon PC hardware should follow the model of Soviet military technology, which is to say;
    Refine existing technologies, don't introduce new, untested, technologies every freakin month!!!

    --
    In the free world the media isn't government run; the government is media run.
  5. cool! by Anonymous Coward · · Score: 5, Funny

    I hope it will be able to run the new Mosaic software. Have you guys seen that? It's like Gopher but with you can add pictures, change the font size, etc.

    1. Re:cool! by paladin_tom · · Score: 5, Insightful

      This isn't the right way to measure the "goodness" of a system. The Hurd has concepts that are actually innovative.

      If you're going to say that the Hurd sucks because it doesn't support some piece of hardware or software, then *damn*, Linux really sucks... and it did even more so at version 0.2. Gee, what am I doing... where's a Windows box? Win 98 must obviously be superior to all these Free/Open Source systems, with all the hardware and software it supports.

      --
      #define sig "Every social system runs on the people's belief in it."
    2. Re:cool! by Anonymous Coward · · Score: 3, Funny

      Well, the PROPER way to measure the goodness of a system is by a simple qualitative measure know as...

      wait for it..

      *B*F*I* the BEARD FULLNESS INDEX

      Let's compare the major players in our discussion:

      HURD - Richard Stallman has a rich full beard. So.. BFI_stallman = BFI_hurd = 10

      WINDOWS - ever seen a picture of that Paul Allen dude when he was younger? BEARD! What about Bill Gates? Well, he always looked like a faggot or an old ugly woman, no facial hair. So...
      BFI_allen = 7,
      BFI_gates = -1, and therefore it follows that
      BFI_windows = (7 - 1)/2 = 3.

      LINUX - Linus is beardless (but nowhere near as faggly as Gates) .. Alan Cox on the other hand .. whew. He gets an 5.6 on the beard-o-meter, due to straggliness. Therefore:
      BFI_torvalds = 0,
      BFI_cox = 5.6, and therefore,
      BFI_linux = 2.8

      Now, clearly, beards indicate intellectuals who want to hide their faces from society. everybody knows that. that's why all professors have them.

      So it logically follows that the LOWEST BFI will yield the most POPULAR and USABLE operating system. To recap our examples:

      BFI_hurd = 10
      BFI_windows = 3
      BFI_linux = 2.8

      Therefore, clearly the winner is Linux, with WIndows a close second. Unfortunately, Stallman pushes the HURD's BFI off the chart and out of the public eye. Sorry, Dicky!

    3. Re:cool! by AftanGustur · · Score: 2
      This isn't the right way to measure the "goodness" of a system. The Hurd has concepts that are actually innovative.

      It's not that I think you don't belive your statement yourself, it's just that companies have been claiming the same thing since I remember.

      So, please name a few examples of what's innovative in Hurd.

      --
      echo '[q]sa[ln0=aln80~Psnlbx]16isb572CCB9AE9DB03273snlbxq' |dc
    4. Re:cool! by SerpentMage · · Score: 2

      Actually Windows is a monolithic kernel. It used to be non-monolithic. But once Windows NT 3.51 hit graphics, etc moved back into the kernel. The problem was performance and MS simply bit the bullet and said, screw it lets go back to what works....

      --

      "You can't make a race horse of a pig"
      "No," said Samuel, "but you can make very fast pig"
    5. Re:cool! by R.Caley · · Score: 2
      The Hurd has concepts that are actually innovative.

      Actually, now I come to think of it, thinking of the Hurd as a piece of conceptual art rather than an operating system does improve my feelings about it. Over her a pcikled shark, over there a toy operating system.

      Concepts butter no parsnips.

      --
      _O_
      .|<
      The named which can be named is not the true named
    6. Re:cool! by Gleef · · Score: 2
      AftanGustur asks:

      So, please name a few examples of what's innovative in Hurd.

      Let's see:
      • Translators: userspace programs programs to act as a file or a hierarchical directory. Device drivers, filesystems, etc are implemented as translators in Hurd.
      • A security structure to allow arbitrary users to install arbitrary translators as needed to the system without compromising security or system integrity.
      • Multiple authentication servers, allowing different parts of the system to have completely different security models.
      • A very flexible interprocess communication model.
      • Many other, more subtle, innovations I don't have time to list.
      Basically, the Hurd offers a much more flexible operating environment, one that can move beyond most of the restrictions of *nix, while still looking like Unix to the users and developers.

      Much more detailed information can be found at http://www.gnu.org/software/hurd/docs.html.
      --

      ----
      Open mind, insert foot.
    7. Re:cool! by Ayende+Rahien · · Score: 2

      No, still micro-kernel, even if the GUI run in kernel space.

      --

      --
      Two witches watched two watches.
      Which witch watched which watch?
  6. Will they have to change the name? by TheConfusedOne · · Score: 4, Funny

    OSKit/HURD?

    --
    --- I wish I could hear the soundtrack to my life. That way I'd know when to duck.
    1. Re:Will they have to change the name? by paladin_tom · · Score: 5, Informative

      Actually, when distinguishing between implementations of the Hurd on different microkernels, we ususally say Hurd/Mach versus Hurd/L4. This is consistent with GNU/Linux and GNU/Hurd, ie. HigherLayer/LowerLayer.

      OSKit-Mach is just a superior implementation of Mach, so we'd still call it Hurd/Mach if we needed to make a distinction.

      Real improvements to the Hurd will come with the eventual port to the microkernel which is much superior to Mach (and the answer to current anti-microkernel FUD).

      --
      #define sig "Every social system runs on the people's belief in it."
    2. Re:Will they have to change the name? by Arandir · · Score: 4, Funny

      So in other words, when the GNU project finally produces a complete operating system with all the operating environment trimmings, the correct name will be "The GNOME/GNU/Hurd/Mach System"?

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    3. Re:Will they have to change the name? by photon317 · · Score: 2


      Why eventual port? They're switching Machs right now, why not switch to l4ka right away?

      --
      11*43+456^2
    4. Re:Will they have to change the name? by Leimy · · Score: 2

      Here here!

      No doubt a good microkernel is a nontrivial thing to write but it can be done, has been done and as far as I can tell Mach isn't it :)

      Even Mac OS X seem to have some fairly major latency issues and it isn't even a micorkernel [though it does have Mach inside]. I think mach tries to do too many things and has too many of its own system calls to be easily done well.

      L4 compliant microkernels [L4 is a spec and there are implementations of that spec... like Fiasco,/A>] conentrate on doing only a few things very well.

      If indeed the port of the Hurd servers ever happens to go to L4... I will be sure to try it out but as it stands now GNU/Hurd seems to have the same basic problems it did back 1998 when I last dared to run it.

    5. Re:Will they have to change the name? by Leimy · · Score: 2

      Type-o's suck ass don't they? :)

    6. Re:Will they have to change the name? by paladin_tom · · Score: 2

      GNOME and Hurd are both part of the GNU system. That would be like calling Mac OSX "Aqua/MacOSX/FreeBSD/Mach".

      (Betcha' weren't expecting a serious answer, eh?) ;-)

      --
      #define sig "Every social system runs on the people's belief in it."
    7. Re:Will they have to change the name? by paladin_tom · · Score: 2

      GNOME is part of the GNU Project, KDE isn't. If you look at the GNU coding standards, they'd like any GUI interface to a GNU app to be GTK.

      Nothing against KDE, it's very good and I don't like it when people flame it, but GNOME is the "GNU-Brand" desktop.

      --
      #define sig "Every social system runs on the people's belief in it."
  7. whoops by seanw · · Score: 5, Interesting

    The release of a production version of the free GNU operating system (OS) has been delayed beyond the end of the year, as the current development version of the system does not support large disk partitions and high speed serial I/O (input-output), according to Richard Stallman

    is it just me, or does it sound like they had it all ready to ship, date planned and everything, and then someone pointed out that it was lacking some major I/O features/performance, and the developers collectively slapped their foreheads and went "oh shit, yeah, we kinda forgot about that one."

    like, all this took them by surprise? sucks to forget to implement a couple crucial features, eh?

    1. Re:whoops by paladin_tom · · Score: 3, Insightful

      This has nothing to do with the Hurd, and everything to do with the microkernel it's sitting on. At present, that microkernel is obsolete and slow.

      --
      #define sig "Every social system runs on the people's belief in it."
    2. Re:whoops by Leimy · · Score: 2

      This shouldn't be a surprise... its the same situation they had in 1998.

    3. Re:whoops by scrytch · · Score: 2

      What would Nietzsche say about Open Source?

      He rather liked the idea of people exploring their creativity without societally imposed limits, and in general expressing their desires and drives to their utmost. It's been used to justify tyranny, except that he figured that if enough good people also expressed their will to power, that controlling evil could not stand.

      I rather think he'd like Bill Gates and Linus both. I imagine he'd have liked RMS when he was coding, but not as he is now. "In every party there is one who through his all too credulous avowal of the party's principles incites the others to apostasy."

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
    4. Re:whoops by Beliskner · · Score: 2
      News: Stallman delays Hurd
      Slashdot: NOOOO!

      News: Micro$oft forces a buggy trashy piece of software out on time
      Slashdot: NOOOO!

      Conclusion: If Micro$oft is obliterated it won't be a happy era like the '60s, because everybody'll demand that volunteer OSS be released on time! Therefore Nobody will never happy

      Wake up, people, OSS also means Open Source deadlines! Whatever happened to all this "Linux is about quality not quantity" that everybody believed in? I hope the ext4fs developers are paying attention - even if it's buggy and causes inode corruption it's GOTTA BE ON TIME! Sheesh, I wonder what'll happen on Slashdot if Stallman announces, "like Micro$oft we're gonna halt all Hurd development for 12 months while we look for security bugs".

      Let's all be honest - we'd all rather have buggy software than late software.

      --
      A caveman dreams of being us, the incalculable power and riches. We dream of being Q, then what?
  8. 19 years by Anonymous Coward · · Score: 5, Funny

    GNU/Hurd. 19 years in the making, and worth every minute of it.

    Finally the world will have a politically correct OS that works just like other Unices have for decades.

    1. Re:19 years by aardvarkjoe · · Score: 2

      ...And will it be worth the extra 19 years it will take to make it usable?

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    2. Re:19 years by MyHair · · Score: 3, Informative

      GNU/Hurd. 19 years in the making, and worth every minute of it.

      That's not entirely fair. A lot of Linux-based OSes contain very healthy doses of GNU software and are compiled with GCC, one of the first major contributions of GNU.

      The kernel was one of the last things they tackled, but along came Linus Torvalds and now many OS kernel developers would rather work on Linux than the Hurd.

    3. Re:19 years by Arandir · · Score: 2

      A lot of Linux-based OSes contain very healthy doses of GNU software and are compiled with GCC, one of the first major contributions of GNU.

      Most of that GNU software is not a part of the OS. Certainly a compiler is not. It may be useful to you, and necessary to build the OS, but it is no more a part of the OS than a screwdriver is part of a car.

      GNU follows Microsoft's erroneous definition of "operating system". Just because it ships with the OS does not make it the OS.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    4. Re:19 years by Abcd1234 · · Score: 2

      That would be an erroneous statement, IMHO. The kernel is the kernel. It facilitates things. It provides a substrate upon which an OS can be built. The OS, aka, "operating system" is the collection of tools combine with the kernel which provide a working, useable system. After all, the Linux kernel would be totally useless if we didn't have init, bash, mount, ls, etc, etc.

    5. Re:19 years by mangu · · Score: 2
      After all, the Linux kernel would be totally useless if we didn't have init, bash, mount, ls, etc, etc.


      A car would be useless without tyres or seats, but I don't call mine a PIRELLI/RECARO/Chevrolet

    6. Re:19 years by Abcd1234 · · Score: 2

      Yeah, but keep in mind that the work to develop the seats is pretty small compared to that needed to build, say, the engine or the chassis. The opposite is true in the OS world. Yes, the kernel is an impressive feat of software development. But the sheer mass of code which encompasses the GNU toolchain is mind-boggling. Hell, gcc itself is huge, let alone the reset of the system.

    7. Re:19 years by Arandir · · Score: 2

      I didn't say that the kernel was the only component of an operating system. You also need some infrastructure around it, and the ability to run an executable. It's entirely possible, and somewhat common, to have a usuable Linux system without GNU. Throw linux, some minimal infrastructure, and BusyBox on an embedded device and you have an operating system without one GNU utility.

      The problem is that there is no commonly accepted and *specific* definition of operating system. I've talked to CS professors who say that a kernel fits their definition. I've also heard lawyers swear before worldwide TV that Internet Explorer is a part of an operating system. The truth lies somewhere in between.

      My definition is the bare minimum software necessary to manage the hardware and direct the processing of other software. This would include a file system, boot/init structure, process infrastructure, and the like. Excluded is bash, emacs, gcc, ls and tar. They may be damned useful, but they are no more part of the operating system than XFree86 or Perl.

      Even if you don't like my definition, you still have to admit that a complete Linux distro that can fit on a single floppy counts as an operating system. There's a lot of these single floppy distros, and none of them come with much GNU software.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  9. Thank god they're fixing partition size by metalhed77 · · Score: 5, Interesting

    Does anyone here know why they let the partition size issue languish for so long? Hell, I've had files larger than 1GB (and not porn! go figure). Hard disks have been at the 10 GB mark for years, where it really doesnt' make sense to have 10 partitions. I wish richard luck. On another note, does anyone know how HURD benchmarks against linux?

    --
    Photos.
    1. Re:Thank god they're fixing partition size by cscx · · Score: 4, Funny

      On another note, does anyone know how HURD benchmarks against linux?

      Currently, the HURD doesn't support benchmarking software. But they hope to add that functionality within the next few years, if that answers your question.

    2. Re:Thank god they're fixing partition size by Wesley+Felter · · Score: 3, Informative

      IIRC the partition size limit is due to the fact that the filesystem server mmaps the partition; on 32-bit systems there isn't enough address space for large partitions.

      As for benchmarks, I think the answer is "don't ask".

    3. Re:Thank god they're fixing partition size by caseyc · · Score: 3, Interesting

      I have to wonder if GNU/Hurd developers have been partitioning their HD's with so many 1gb partitions up until now. And, at what point did it occur to them that there was a better way to do it?

    4. Re:Thank god they're fixing partition size by Waffle+Iron · · Score: 4, Funny
      IIRC the partition size limit is due to the fact that the filesystem server mmaps the partition; on 32-bit systems there isn't enough address space for large partitions.

      Hmmm. That is a very elegant way to handle disk partitions. Maybe they shouldn't rush into a quick fix for this that loses the benefits of mmaping the whole partition. In a few short years, AMD, Intel and IBM will all be offering mainstream 64-bit CPUs, and they'll be able to mmap exabyte sized partitions without throwing out the current codebase.

      I think that they should just hold tight until then. No need for reckless haste.

    5. Re:Thank god they're fixing partition size by the_other_one · · Score: 3, Funny

      The project has been underfunded

      They must have just got their first 10 GB hard disk in the P100.

      --
      134340: I am not a number. I am a free planet!
    6. Re:Thank god they're fixing partition size by ivan256 · · Score: 2

      But how soon will IBM's pixie dust make possible disks with partitions larger than can be addressed in 64-bits?

      Considering that you can byte address billions of gigabytes with a 64-bit address space, I'm going to go out on a limb and say that there will never be an IBM pixie dust hard drive that can't be mapped with 64 bits.

      The processor with the highest number of valid virtual address bits currently available uses 54 bits of the available 64. Even this machine is not in danger of being unable to address all of a disk that is made with currently available technology.

    7. Re:Thank god they're fixing partition size by defile · · Score: 5, Informative

      It's a really hard problem to fix.

      The ext2fs implementation is actually a userland process which takes a partition as an argument and attaches a translator to the mountpoint. The translator's job is to send requests under this namespace to this server.

      The ext2fs server actually mmap()s the partition containing the filesystem and performs all operations as if it were a contiguous block of memory. Unfortunately the ext2fs driver, since it's a userland process, can only address 2GB of memory (the kernel often takes half). Adding a heap and a stack leaves mmap() with about 1GB to safely play with.

      Eliminating this limitation would mean using either a 64-bit architecture, or using a read/write/lseek interface instead of mmap, which may mean totally throwing out the ext2fs server as-is. Perhaps they weren't concerned with the limitation because they thought everyone would be using 64-bit architectures by now?

      I'm not sure if there are any other reasons other than the filesystem servers using mmap() for the limitation.

    8. Re:Thank god they're fixing partition size by paladin_tom · · Score: 5, Insightful

      Does anyone here know why they let the partition size issue languish for so long?

      The partition size is limited because the Hurd maps the entire disk partition into main memory, and the 32-bit architecture of current Intel processors limits the size of a virtual address space to 2^32 bytes, hence the limitation. Changing the Hurd to do things differently isn't exactly a one-weekend patch.

      On another note, once we go the 64-bit processors, we'll see a much larger virtual address space (double it's current size 32 times), and hence a much higher cap on the partition size (assuming no fix).

      On another note, does anyone know how HURD benchmarks against linux?

      This really isn't the right question to ask: remember that the Hurd is at version 0.2, and that "Premature optimization is the root of all evil." No new Free/Open Source kernel is going to ship and be immediately as fast and full-featured as Linux... things just don't work that way.

      What's important is that the Hurd represents new OS technology... and that's more important that any current lack of performance or drivers.

      --
      #define sig "Every social system runs on the people's belief in it."
    9. Re:Thank god they're fixing partition size by Some+Dumbass... · · Score: 5, Funny

      Hell, I've had files larger than 1GB (and not porn! go figure).

      Hint: "man logrotate"

    10. Re:Thank god they're fixing partition size by Twirlip+of+the+Mists · · Score: 2

      Are you the same AC? Again, your calculator is broken. Two to the sixty-fourth power is 16.7 million terabytes, not 1.6 million terabytes.

      --

      I write in my journal
    11. Re:Thank god they're fixing partition size by istartedi · · Score: 3, Insightful

      Currently, the HURD doesn't support benchmarking software

      Oh man! I take back every bad thing I ever said about RMS and friends. Anyone who can disable benchmarking software deserves not only a McArthur grant, but international acclaim and recognition at every level. Why... oh... OK. Go ahead. Give him his Free Software tax. He deserves it. I'll be there to applaud him at the ribbon-cutting ceremony for the Bureau Of Software Development in Washington DC. Imagine! At last. No more benchmarks. This is a red letter day indeed.

      --
      For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
    12. Re:Thank god they're fixing partition size by Permission+Denied · · Score: 5, Interesting
      The ext2fs server actually mmap()s the partition

      This is completely nuts.

      I can appreciate that the filesystem driver is a userland process - this means I can write a "filesystem" as a normal userland process (eg, make some things have a filesystem-like interface, so you can do interesting things with databases like make /etc/passwd a directory). This is a cool idea.

      However, using mmaping an entire partition is just crazy. This is poor design. What were they thinking?

      Are they trying to avoid the system call overhead for seek() calls? This is the only reason I can think of that someone would do this - when you read/write/seek, you have to do a system call for seek(), but that comes "for free" when you mmap() because you specify the address. This would only be a problem with HURD-like systems, because there is no overhead if the filesystem driver runs in kernel space along with whatever other subsystems it needs to use.

      I know everyone hates backseat designers, but I'd like to know if the following approach has been considered:

      Make two new system calls, say "readaddr" and "writeaddr". These work like read and write, except that you also specify an offset (perhaps with a "whence" field like lseek). This saves you the overhead of calling seek all the time by combining the operations into one system call. This might be useful for other things as well, but I would imagine a filesystem driver is one speed-critical piece of code that does a lot of jumping around. Actually, I just remembered that there already are calls for this: pread/pwrite.

      Another possible approach: using mmap is nice, but mapping in an entire partition is fubar. Why not map in specific parts of the partition as they become needed? Eg, keep superblock mapped right away from startup, and map in other parts as they are needed. Seems a bit complex, but could be done more easily with another layer of abstraction (some library which keeps a hash or something of mmap()ed bits and provides a nice interface for filesystem drivers). I'm guessing mmap was used as this transfers certain operations (eg, cache management) "deeper" into the "kernel" and avoids code duplication.

      But anyway, mmaping an entire partition is really nuts. They're not getting any sympathy from me.

    13. Re:Thank god they're fixing partition size by d_i_r_t_y · · Score: 2, Funny

      the Hurd workaround to 1Gb ext2 partitions: a 1 gig partition for each of / and /usr, and a 78gig fat32 partition for data.

    14. Re:Thank god they're fixing partition size by Olivier+Galibert · · Score: 5, Informative

      No, what they're trying to do is offload the cache management to the virtual memory manager. With mmap() backed by the partition itself, the VM can read and write the pages transparently w.r.t the ext2 server. With read/write/lseek, you have to do actual memory management. Last time I looked, there was no interface for collaboration between the VM and the servers for cache management.

      And this kind of cache management is horribly hard in a monolithic kernel for a start. Look how long 2.4 took before the VM behaviour was considered decent (2.4.16 iirc). A decently fast distributed one is even worse to design.

      OG.

    15. Re:Thank god they're fixing partition size by Leimy · · Score: 2

      Sounds like a fundamental design that should be thrown away so you can do what you really want to do. I think most good software engineers see when things are going to "dead-end" and should abandon the losing design in favor of a better one.

      Did BSD-Lites have this partition issue? It ran a Unix server on top of Mach too I believe. To force people to run a 64bit architecture to run Hurd seems like a bit of a non-liberating liberation :)

    16. Re:Thank god they're fixing partition size by ivan256 · · Score: 2

      Multiply that value by 512 bytes if you are using one address per hard drive sector.

      Aside from the bad math, the issue here was that they memory mapped the disk. That means you have to byte address the disk instead of sector address the disk.

    17. Re:Thank god they're fixing partition size by oconnorcjo · · Score: 2

      No new Free/Open Source kernel is going to ship and be immediately as fast and full-featured as Linux... things just don't work that way.

      What's important is that the Hurd represents new OS technology... and that's more important that any current lack of performance or drivers.


      The Hurd has been in developement for far longer than when the first line of Linux was written. That does not mean that the Hurd will not one day be a spiffy OS but it does beg the question of how does it fair with its distant cousin. If the Hurd wants to be more than an academic curiosity, it has to perform well. It does not have to perform as well as Linux, but well enough that you don't notice it. New technology is only interesting if it is better or faster in some noticable way to the user.

      --
      I miss the Karma Whores.
    18. Re:Thank god they're fixing partition size by paladin_tom · · Score: 2

      Technology that is under development is never better for end-users than stable software. Those of us who run GNU/Hurd and are involved with the project want to help develop an architectually-superior Free OS.

      --
      #define sig "Every social system runs on the people's belief in it."
    19. Re:Thank god they're fixing partition size by ameoba · · Score: 2

      No biggie... By the time the HURD is shipping, 64b procs will either be standard on most computers, or obsolete.

      --
      my sig's at the bottom of the page.
    20. Re:Thank god they're fixing partition size by Permission+Denied · · Score: 2
      This is what they would probably end with, as a workaround for poor legacy 32-bit architectures, like Intel x86 -- but only as a quick-and-dirty, temporary workaround. You can't have cleaner interface to a partition than seeing it as a continuous memory block. At least I can't imagine a cleaner interface, if you have any idea of such a thing, I'll be more than glad to hear it.

      Do you realize how ridiculous your words are? "Legacy" 32-bit environments? Like the "legacy" 32-bit environment with the "legacy" operating system that you used to type into slashdot? So it's cleaner to make the maximum filesystem size depend on the machine's pointer length than it is to simply write better software, even if writing better software means resorting to traditional ("legacy" as you might call it) methods?

      The "single opcode MOV?" You do realize how mmap works? Certainly the user-level program can simply access it like memory, but this then goes through the VM (by means of a hardware interrupt on page fault) which calls some disk subsystem, which will eventually end up calling a disk driver. End result is that you write something to the disk. There is no magic MMU hardware which understands EIDE or SCSI and maps memory to disk blocks - this is done through code. It's merely an abstraction to transfer the complex parts of the code into another layer of software, made necessary because of the poorly-thought-out layers of software.

      How can a single MOV be considered "elegant" when you have to keep a data structure of which parts of the partition are mapped? Your single MOV instruction becomes a series of instructions to select a "view" of a partition, clean out old "views," and map new ones when needed. It won't be a MOV, it will be a function call into some library. How is this more clean than simply calling pread()? Of course, as you say, this is only a "temporary hack" - you can get rid of this once everyone is using 64-bit architectures.

      It's not "clean" or "elegant" in any sense of the word. The mmap is a nasty hack because someone couldn't figure out how to use the same cache management that the VM uses in a user-level process. Someone simply chose a poor abstraction. It's a mistake, and I simply cannot understand how someone could let such a stunning error into any operating system.

      I hate to spoil your naivete, but Intel and AMD don't give a damn about HURD, and they certainly don't design their hardware with this sort of thing in mind. Although the theoreticians don't like this, computer hardware is complex and non-orthoganal. If the HURD was designed to run on only 64-bit machines with clean MMUs, you'll be waiting a long time until HURD is stable on readily-available hardware. (Does HURD even support 64-bit architectures at this time? If not, then how can you possibly justify the mistake of having filesystem drivers use mmap?)

      I don't give a damn about the politics. This is simply bad design. You can attack me with all sorts of accusations that I don't approve because of whatever politics, but this does not change the fact that someone made an immense error when designing the filesystem servers and certain people thought this error was "elegant."

      I really didn't mean to flame you personally, but this is inexcusably bad design. I don't understand how someone can justify it, rather than admitting that it's a fundamental design problem.

    21. Re:Thank god they're fixing partition size by Ayende+Rahien · · Score: 2

      > legacy 32-bit

      ROTFLMAO

      > You can't have cleaner interface to a partition than seeing it as a continuous memory block

      Maybe, but it takes exactly fifteen minutes to do:

      read_partition(unsigned long start, unsigned long length, char * buffer);
      write_partition(unsigned long start, unsigned long length, char * buffer);

      Which gives you just as clean interface, if at the cost of a few more calls.

      --

      --
      Two witches watched two watches.
      Which witch watched which watch?
    22. Re:Thank god they're fixing partition size by TheLink · · Score: 2

      Just curious - are there any issues mmaping stuff on SMP machines? Or it'll still be better/good?

      --
    23. Re:Thank god they're fixing partition size by oconnorcjo · · Score: 2

      Technology that is under development is never better for end-users than stable software. Those of us who run GNU/Hurd and are involved with the project want to help develop an architectually-superior Free OS.

      While I don't necessarily agree with your assertion, I will just skip it because it is not important to the discussion. RMS was saying for awhile that Hurd was almost ready for prime time. If that is the case, then "under developement" is not what Hurd was going for. As I said in the parent post "If the Hurd wants to be more than an academic curiosity, it has to perform well.". You are saying you like Hurd for academic reasons and that is fine. I was only making a point about BEYOND academia.

      --
      I miss the Karma Whores.
    24. Re:Thank god they're fixing partition size by J.+Random+Software · · Score: 2
      The elegant API is read/write with OS-provided buffers. This can be zero-copy, asynchronous, transactional, admit pipes and network associations as well as random-access files, work without vast unused address space (and wasted I/O and physical RAM and TLB contention from trying to guess about readahead and writeback), and make performance much more predictable (you never have to guess which pointer uses will block you and start swapping unless your physical RAM is inadequate for your software).

      mmap() is simple when it works, but the things it can't express show it's a poor fit for the problem space.

  10. Systems work by peterb · · Score: 5, Insightful

    Is harder than most people seem to think it is.

    That being said, I think the Hurd is pretty much a solution in search of a problem. Who cares? And why? The FreeBSD kernel does everything Hurd purports to want to be able to do, and is more mature, stable, and feature-complete. The same could probably be said of the Linux kernel.

    Does that mean the Hurd guys should stop what they're doing? Of course not. Writing operating systems is fun.

    It does, however, probably mean that the stuff they're doing isn't really news.

    1. Re:Systems work by peterb · · Score: 4, Insightful

      Well, that's a little harsh. I mean, we all do things that we want to do. I "could" be writing software to cure cancer and AIDS, but instead I'm working at a storage startup trying to make the big bucks and work with a great group of people. We can't all sacrifice our lives for the Great Cause.

      And I agree that 20 years ago, "wouldn't it be nice if there was a free operating system" seemed like such a cause. But ever since BSDi settled the unix issues, it seems to me that BSD [footnote 1] became that free operating system.

      -pete
      footnote 1: Substitute Linux depending on your political preferences. Void where prohibited by law. Call before midnight tonight for complete refund of price of purchase. Terms available, don't be fooled by cheap imitations, no salesman will visit your home. My apologies to Tom Waits.

    2. Re:Systems work by dvdeug · · Score: 2

      These guys are obviously smart, and can be writing software to find cures for cancer and AIDS.

      If anyone had a theory on how to do that, the National Institute of Health would be shoveling money at them.

      But, hey, why do any of that when you can be working on HURD?

      And I guess talking at slashdot is the best you can do. If you want to harass someone for doing something when they could be engaged in something better, perhaps you should get up and start working on _something_.

    3. Re:Systems work by paladin_tom · · Score: 2

      Who cares?

      Me.

      And why?

      Because of the Hurd's multi-server microkernel architecture. If we keep relying on monolithic kernels (Linux, *BSD) forever, we eventually won't be able to keep up with proprietary OSs, and the Free/Open Source software movement will die.

      It does, however, probably mean that the stuff they're doing isn't really news.

      There's a group of Free Software developers choosing to truly innovate. If that isn't news, there's something wrong with the Free and Open Source communities.

      --
      #define sig "Every social system runs on the people's belief in it."
    4. Re:Systems work by peterb · · Score: 2

      > Because of the Hurd's multi-server microkernel
      > architecture. If we keep relying on monolithic
      > kernels (Linux, *BSD) forever, we eventually
      > won't' be able to keep up with proprietary OSs,
      > and the Free/Open Source software movement will die

      Whahuh? What the hell are you talking about?

      What in tarnation does the architecture of a kernel have to do with "keeping up" with some other OS? That's a completely orthagonal issue.

      Hint: You can write unmaintainable crap code with any architecture. You can write clean maintainable code with any architecture.

      I see absolutely no evidence for your hysterical assertion.

    5. Re:Systems work by Cro+Magnon · · Score: 2

      Well, so far, Linux (and even BSD) has been keeping up better than the Hurd has!

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  11. Ironic by jeramybsmith · · Score: 3, Insightful

    GNU was intended to solve the problem of their not being a free unixlike OS. Now there are like 50 but still no GNU. Maybe they should refocus on providing a great userland?

    --
    Never overestimate the end user. -jeramy b. smith
    1. Re:Ironic by Arandir · · Score: 2

      They already did provide a great userland. Heck, everything BUT the Hurd is userland.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  12. Re:Umm, okay... by aussersterne · · Score: 3, Insightful

    My home directory (which only contains material back to '98, all else is archived on QIC, which I can't even read any more) is already 6GB, and that's just mail and documents -- all of my images and sound files are stored elsewhere.

    No wonder I don't use Hurd.

    I think the Hurd is a nice, interesting CS project, but there isn't enough of a pragmatic influence amongst its developers ranks to make it actually useful to anyone.

    --
    STOP . AMERICA . NOW
  13. Nonstandard Partitioning? by LinuxGeek · · Score: 3, Insightful
    added Stallman. "I don't think it was realized how bad it is practically speaking not to be able to use whatever your disk partitioning is. Clearly most people are not going to repartition their disks to be able to try out our Hurd based system."

    What kind of systems are they using for development that they just noticed the inability to read current large partitioning schemes and interact with them? This dosen't do much to encourage me to try HURD and hope it will support much of my newfangled hardware.
    --

    Kindness is the language which the deaf can hear and the blind can see. - Mark Twain
    1. Re:Nonstandard Partitioning? by LinuxGeek · · Score: 2

      IIRC, that is about what RMS was running the last time I saw him in person at Linux expo '99 in Raleigh. Surely some kind benefactor could buy some up to date hardware for such a talented contributor to the world of software.

      Maybe we could start a (non-PayPal) fund to help him get some ( hardware).

      --

      Kindness is the language which the deaf can hear and the blind can see. - Mark Twain
  14. What is HURD? by randomErr · · Score: 5, Informative


    http://www.gnu.org/software/hurd/hurd.html

    GNU HURD is a slimmer re-write of the UNIX kernel that is completely OOP.

    Here's a cut and paste from the homepage:

    The Hurd is not the most advanced kernel known to the planet (yet), but it does have a number of enticing features:

    it's free software
    Anybody can use, modify, and redistribute it under the terms of the GNU General Public License (GPL).
    it's compatible
    The Hurd provides a familiar programming and user environment. For all intents and purposes, the Hurd is a modern Unix-like kernel. The Hurd uses the GNU C Library, whose development closely tracks standards such as ANSI/ISO, BSD, POSIX, Single Unix, SVID, and X/Open.
    it's built to survive
    Unlike other popular kernel software, the Hurd has an object-oriented structure that allows it to evolve without compromising its design. This structure will help the Hurd undergo major redesign and modifications without having to be entirely rewritten.
    it's scalable
    The Hurd implementation is aggressively multithreaded so that it runs efficiently on both single processors and symmetric multiprocessors. The Hurd interfaces are designed to allow transparent network clusters (collectives), although this feature has not yet been implemented.
    it's extensible
    The Hurd is an attractive platform for learning how to become a kernel hacker or for implementing new ideas in kernel technology. Every part of the system is designed to be modified and extended.
    it's stable
    It is possible to develop and test new Hurd kernel components without rebooting the machine (not even accidentally). Running your own kernel components doesn't interfere with other users, and so no special system privileges are required. The mechanism for kernel extensions is secure by design: it is impossible to impose your changes upon other users unless they authorize them or you are the system administrator.
    it exists
    The Hurd is real software that works Right Now. It is not a research project or a proposal. You don't have to wait at all before you can start using and developing it.

    --
    You say things that offend me and I can deal with it. Can you?
    1. Re:What is HURD? by Eil · · Score: 5, Funny


      This structure will help the Hurd undergo major redesign and modifications without having to be entirely rewritten.

      "...but we might change out the whole kernel from time to time when things aren't looking so good."

    2. Re:What is HURD? by Eil · · Score: 2


      You are correct, but I think it's still not a small issue. The core functions of a kernel are the most complex and time-consuming to develop and maintain.

      One think you could say about Hurd developers is that they're not it for the vanity.

    3. Re:What is HURD? by paladin_tom · · Score: 2

      Perfectly reasonable, since the Hurd isn't a kernel, it just sits between a microkernel and glibc.

      --
      #define sig "Every social system runs on the people's belief in it."
    4. Re:What is HURD? by Cro+Magnon · · Score: 2
      The Hurd is real software that works Right Now. It is not a research project or a
      proposal. You don't have to wait at all before you can start using and developing it.


      ROTFLMFAO!!
      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
    5. Re:What is HURD? by randomErr · · Score: 2

      Dude, why ya posting to a topic that has been dead for like a week? Are you a karma hog or what?

      I wouldn't have know about your post unless I was monitoring this article.

      --
      You say things that offend me and I can deal with it. Can you?
    6. Re:What is HURD? by Cro+Magnon · · Score: 2

      Because I've been away from /. since Thursday and this was the first I saw of this article. Besides, I'm still more timely than the Hurd is. :)

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  15. Relevance by Perianwyr+Stormcrow · · Score: 2, Funny

    You could be out masturbating right now, instead you're writing comments on Slashdot. I mean, what are you using your energy for, anyway?

    --

    What we call folk wisdom is often no more than a kind of expedient stupidity.-Edward Abbey

  16. Why OSKit? by Animats · · Score: 3, Insightful
    OSKit is a collection of operating systems parts for use by researchers, not a production system. It's intended to be straightforward and modular, but not heavily optimized. If the Hurd team is switching to OSKit, they must be in deep trouble.

    Now if they were switching to L4, that would be cool. But it would be a research effort.

    And why does anyone, at this late date, care much about high-speed serial line support?

    1. Re:Why OSKit? by jpmorgan · · Score: 4, Informative
      The Hurd will be switching to L4, when the NDAs on the latest version of L4 are dropped and there's a real implementation to work from.

      That port is fairly extensive, so right now they're moving to Mach + OSKit, since OSKit supports the Linux 2.2 device drivers, something Hurd is sorely lacking.

    2. Re:Why OSKit? by Teferi · · Score: 2

      There is a port of HURD to L4 in process. I was under the assumption that that was going to be the official HURD...guess not.
      Shame the 'main' branch is still on Mach...it may have been neat back when virtual memory was still new and hot, but it's really showing its age now

      --
      -- Veni, vidi, dormivi
    3. Re:Why OSKit? by peter · · Score: 2

      NDA as in non-disclosure agreement? Say what ... what happened to the freedom/liberty idea? (Honest question here, I haven't even googled for anything on this topic.)

      --
      #define X(x,y) x##y
      Peter Cordes ; e-mail: X(peter@cordes , .ca)
    4. Re:Why OSKit? by jpmorgan · · Score: 2

      The developers of L4 are only releasing the specs to the next generation under NDA currently. The NDAs will be dropped, specificaitons and implementations will be available and Free in a couple of months.

  17. So, Linus was rfight? by Royster · · Score: 5, Interesting
    From Open Sources: Voices from the Open Source Revolution

    So at the time I started work on Linux in 1991, people assumed portability would come from a microkernel approach. You see, this was sort of the research darling at the time for computer scientists. However, I am a pragmatic person, and at the time I felt that microkernels (a) were experimental, (b) were obviously more complex than monolithic Kernels, and (c) executed notably slower than monolithic kernels. Speed matters a lot in a real-world operating system, and so a lot of the research dollars at the time were spent on examining optimization for microkernels to make it so they could run as fast as a normal kernel. The funny thing is if you actually read those papers, you find that, while the researchers were applying their optimizational tricks on a microkernel, in fact those same tricks could just as easily be applied to traditional kernels to accelerate their execution.
    --
    I have discovered a truly marvelous sig, unfortunately the sig limit is too small to contain i
    1. Re:So, Linus was rfight? by Pseudonym · · Score: 3, Insightful

      Linus was right at the time, yes. If he were starting Linux today, however, none of those three points would be correct. They're not experimental any more (WinNT before version 4.0, QNX and BeOS are/were all mainstream microkernel OSes), they do not execute notably slower than monolithic kernels (yeah, the Mindcraft survey was rigged, but Linux and NT are still competitive) and (apart from NT) they are no more complex than Linux is today.

      On the other hand, "I know I can do it and get it working" would still be a valid argument for him to write a monolithic kernel today, but that's open source for you.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    2. Re:So, Linus was rfight? by Royster · · Score: 4, Funny
      How about this quote?


      In short: message passing as the fundamental operation of the OS is just an excercise in computer science masturbation. It may feel good, but you don't actually get anything DONE. -- Linus Torvalds

      --
      I have discovered a truly marvelous sig, unfortunately the sig limit is too small to contain i
    3. Re:So, Linus was rfight? by Pseudonym · · Score: 2

      For every Linus quote there is an equal and opposite Linus quote.

      Everything is a stream of bytes. Repeat until enlightened. -- Linus Torvalds

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    4. Re:So, Linus was rfight? by Animats · · Score: 5, Informative
      As it turns out, microkernels aren't all that portable, because they need close ties to the hardware to support all the fast interprocess communication that they do. But because they're small, the fact that they contain CPU-dependent code isn't as much of a limitation. Porting is more work per line of code, but there aren't as many lines to port.

      Look at QNX and L4 as examples of fast microkernels. About all the kernel does is manage memory, interprocess communication, and task switching. Everything else is in user space, where it's easier to debug and can't mess up as much when it breaks.

      In addition, if you're serious about security, a system where only the microkernel is trusted is the only thing that has any hope of working. In a microkernel system, the kernel tends not to change much over time, once it's working. New functionality is all in user space. You're not patching holes forever, like we are now.

      You do take a performance hit, but in a world where Java, Perl, and XML are used for production work, it's tiny by comparison.

    5. Re:So, Linus was rfight? by platypus · · Score: 2
      I'm by no means an expert (esp. not for micro-kernels, that's why I ask), just a regular linux-kernel lurker, and reading all these arguments for micro-kernels leave me wondering if the theory isn't a bit behind the hardware development.

      I see linux kernel developers seeking solutions for very complicated hardware architectures:
      • Hyperthreading
      • multi-core cpu architectures (IBM Power4)
      • "non-homogenous" memory architectures for multiprocessor machines (NUMA, etc.)
      • more and more "intelligent" storage devices
      • high-performance 3d graphics
      • soft/hard real-time performance

      and so on..., where all of these things can occur combined.

      I'm wondering if a micro-kernel is theoretically as good as a monolitic one in mastering the above difficulties - and if code for all of this had to be integrated in a microkernel, and if this thing really should be called microkernel after that.
      And as far as I know, QNX isn't really an example for an OS which shines on an 8-way box.

      Another thing:
      You do take a performance hit, but in a world where Java, Perl, and XML are used for production work, it's tiny by comparison.

      This I doubt, because there are quite a few things an os can do to help gain performance for typical application tasks. See for instance ingo molnars work on thread startup performance -100000 threads in a very short time (some secs) compared to some minutes on linux before that.
      This work was done because of (Oracle/Sun)'s needs for their application - and java needs everything fast which is related to threads.

    6. Re:So, Linus was rfight? by Animats · · Score: 2
      The microkernel people are probably ahead in soft/hard real-time performance, because QNX is a hard real-time OS where the real-time tasks run in user space. (Contrast RTLinux).

      Intelligent storage devices aren't a big issue either way.

      3D graphics cand present some problems, because the integration betwen the GPU and the CPU can be tight. There's per-process state out in graphics board memory. Neither QNX or L4 really addresses that.

      A message-passing microkernel seems to be a win for multiprocessors, because there's a lot more synchronization activity going on. Interprocessor locks in message-passing systems are very short, just long enough to update a queue, because the microkernel never does anything that takes long.

      Non-homogeneous memory architectures are one of those ideas that keep coming back, but are such a pain they go away again. Some 1970s mainframes had "fast" and "slow" memory. So did early Amigas. Cacheing seems to win out over programmer-visible non-homogeneous memory.

    7. Re:So, Linus was rfight? by platypus · · Score: 2

      Thanks for answering the questions.

  18. Re:Tha HURD by SpankTech3000 · · Score: 2, Interesting

    I would really like to know if this project would even be relevant to the FSF if everybody just agreed to call it GNU/Linux and not just Linux. Stallman is pushing this thing because he *hates* Linux, not because he loves free software.

    My $0.02 (-$12.02 after depreciation).

  19. Thoughts of the future? by dacarr · · Score: 4, Insightful
    I'm seeing it now. Hurd will be to Linux what OS/2 Warp is to Windoze.

    Kudos to RMS for fighting the good fight, but he's already contributed significantly to Linux. I really don't think it'll go farther than that.

    --
    This sig no verb.
    1. Re:Thoughts of the future? by asv108 · · Score: 2
      I'm seeing it now. Hurd will be to Linux what OS/2 Warp is to Windoze.

      Not Really, becuase OS/2 Warp was released well before windows 95, I think it was in the early spring of 95 if I remember correctly, while windows 95 was released in the late summer. It really shouldn't have been released because it was quite buggy. I remember returning it to EB the same week I bought it, after finding out I needed windows disks in order to run windows programs.

    2. Re:Thoughts of the future? by ShavenYak · · Score: 2

      I remember returning it to EB the same week I bought it, after finding out I needed windows disks in order to run windows programs.

      I seem to recall there were two versions: the one you apparently bought, OS/2 for Windows Users, and a slightly more expensive version (because of royalties to MS) which included the necessary bits of Windows 3.1. The idea was you bought the cheaper one if you already had Windows and didn't want to pay MS twice (if you had a pirated copy of Win 3.1, s/twice/once/).

      --

      Hey kids, there's only 5 days left 'til Yak Shaving Day!
  20. Relevancy: by Wakko+Warner · · Score: 5, Funny

    It's being built so that GNU weenies will finally be able to claim a 100% PURE GNU OPERATING SYSTEM. This will gain them fame, fortune, and, their primary objective:

    Mad hoes.

    Yes. You see, the GNU HURD project is just a front. These guys are just looking for a little lovin'. I, for one, will be downloading and running HURD 1.0 as soon as it's released, to support the libidos of these great, visionary men.

    - A.P.

    --
    "Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
    1. Re:Relevancy: by wildcard023 · · Score: 2

      libidos?

      Isn't that -lidios?

      --
      Mike Nugent

      --
      -- Mike wildcard@illuminatus.org
    2. Re:Relevancy: by DrXym · · Score: 2

      And by pure, they mean capable of doing fuck all seeing as it won't have X Windows, Apache, Perl, OpenSSH and a bunch of other non-GPL software that makes an OS useful for doing stuff.

  21. Re:Tha HURD by Istealmymusic · · Score: 5, Informative

    No, Stallman is pushing this thing because its modular and relies on the Mach microkernel and the Flux OSKit library, in stark contrast to Linux's monolithic kernel design. Not to say monolithic kernels are bad, but microkernels do have their advantages, and both GNU/Hurd and GNU/Linux will each have their respective pros and cons.

    --
    "The lesson to be learned is not to take the comments on slashdot too literally." --Vinnie Falco, BearShare
  22. Re:Just more Vaporware? by MissMyNewton · · Score: 5, Funny

    Given all the comments I've been reading it's seems to me like this is nothing more than Vaporware.

    Maybe not. But right now it's clearly meant to be Hurd and not seen. ;-)

    --

    ---

    Information wants...you to shut your pie hole.

  23. Re:Tha HURD by rgmoore · · Score: 5, Insightful

    I'd assume that they're working on the HURD because they think that it's interesting, fun, and/or a good learning experience. Not all Free Software development has to take place with the goal of taking over the world. A lot of it, as ESR points out, is done to satisfy the interests of the individual authors. That's why there are a million projects on Freshmeat that are essentially clones of the same basic project- mp3 player frontends, database systems to catalog CD collections, etc. Individual programmers write them for their own personal reasons and then provide them for anyone else who wants a copy.

    --

    There's no point in questioning authority if you aren't going to listen to the answers.

  24. Delayed? by grub · · Score: 5, Funny


    I want a new slashdot poll:

    Which long awaited project will be the first to become reality?
    a) Duke Nukem Forever
    b) SMP for OpenBSD
    c) GNU/Hurd
    d) The second coming of Jeebus

    --
    Trolling is a art,
    1. Re:Delayed? by Xenographic · · Score: 3, Funny

      That couldn't ever be a real /. poll.

      The last option has to be:
      d) The second coming of Cowboy Neal.

    2. Re:Delayed? by ceejayoz · · Score: 3, Funny

      Well, D is the most likely one.

      And that's coming from an athiest.

    3. Re:Delayed? by isorox · · Score: 4, Funny

      d) The second coming of Cowboy Neal. /me shudders at the thought of him doing it once....

    4. Re:Delayed? by Xeriar · · Score: 2

      That couldn't ever be a real /. poll.

      The last option has to be:
      d) The second coming of Cowboy Neal.


      The poll would not be about Cowboyneal's sex life!

      (Sorry, sorry, someone please name a penance)

    5. Re:Delayed? by Soul-Burn666 · · Score: 2

      e) Team Fortress II

      --
      ^_^
  25. Re:Tha HURD by Anonymous Coward · · Score: 2, Insightful

    No kidding, it's just like the situation with Linux. Linux will never be as popular as Windows, it's no more stable or reliable, and it doesn't support nearly the same hardware base as Windows. Why don't they just give up and start coding for a real platform? They'd do us all a favor. Will all the Linux users please stand up so that I may fart in their general direction? I have one question: WHAT are you trying to desperately prove? That you can eventually make something that's "not quite Windows?" I'd like to know your motivation.

  26. Rip Linux by Citizen+of+Earth · · Score: 2, Insightful

    OSKit's Mach which will help them support faster serial I/O and larger hard discs. Currently GNU/Hurd will only support somewhere between 1 to 2 GB partitions.

    So why don't they just rip the grungy device-driver stuff from the Linux kernel rather reinventing a square-cornered wheel? Perhaps they're not familiar with the concepts of Free Software and re-use.

    1. Re:Rip Linux by dvdeug · · Score: 2

      So why don't they just rip the grungy device-driver stuff from the Linux kernel rather reinventing a square-cornered wheel?

      They're using the OSKit's Mach, which has already ripped the grungy device-driver stuff from Linux and repackged in a nice convientent Mach-sized package, which is what the Hurd needs.

    2. Re:Rip Linux by mandolin · · Score: 2
      So why don't they just rip the grungy device-driver stuff from the Linux kernel rather reinventing a square-cornered wheel?

      If it's like everything else in FSF-land, it's because they want the copyright assignment on the code. linux/drivers/char/serial.c is copyrighted by several authors; maybe they'd rather re-implement 6000 LOC than ask those authors for the assignment. (or maybe linus laughed in their face..)

      Of course, given the whole assignment issue, it also suprises me that they're moving to OSKit. Hell I thought that was why they didn't like (for very loose definitions of "like") Linux.

  27. Re:GNU/Hurd by evilviper · · Score: 3, Informative

    Well, if you want to start that arguement.

    Linux has nothing to do with Gnu. If you wanted to, you could make an OS using the Linux kernel & the BSD tools.

    So, it's now the distros (e.g. RedHat) that are supposed to start throwing GNU in there. Of course, that would cause some user confusion when they go searching for this "GNU Linux" kernel.

    Where does it end? What percentage of an OS's software has to come from a certain source that it must be included in all titles? Shall we call it RedHat Linux/GNU/XFree86/KDE ? Hey, the Gnu tools are replacable... XFree86 doesn't have any real competition, and so it more important than GNU.

    What's that you say? rms is just a vain blowhard that will suck up publicity where ever he can get some? I'm sure he would disagree with that completely, and then go and complain about bitkeeper some more.

    Man am I glad BSDs are better. In fact, rms thinks so too. Why else would he run FreeBSD on his server?

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  28. more than a nuisance by nuckin+futs · · Score: 3, Insightful

    according to the article:
    if you get a moderate size disk you have to divide it into smaller partitions, which is a nuisance.

    I'm sorry, but I have an 80gig drive. If I need between 40 to 80 partitions (between 1 and 2 gigs each), it's not just a nuisance.

  29. Linus was right by zurab · · Score: 3, Troll

    To solve the serial port problem, the GNU project is switching from the GNU Mach to the OSKit Mach, a Mach based on the OSKit for OS development from the University of Utah in Salt Lake City, Utah. "That version of Mach is supposed to get high speed serial line support, although it apparently isn't there in it yet," Stallman said. Before the GNU project could switch to the OSKit Mach, it had to rewrite the terminal support in the Hurd to support virtual consoles.

    By the time these guys switch to the new kernel, test all modules, etc., etc. they will have to update it again for new speed improvements and HD sizes.

    Linus was right that Microkernels tend to be overdesigned, give up speed, and are less practical than monolithic. This is the living proof.

  30. Re:Tha HURD by PylonHead · · Score: 3, Insightful

    And compiled high level language programs by definition can't be as fast as assembly language. But at some point we all decided that ease of programming and maintainance was more important.

    As processors get faster and faster the time it takes to do the context switch will become less and less important.

    --
    # (/.);;
    - : float -> float -> float =
  31. Apologies Not Accepted by Anonymous Coward · · Score: 2, Interesting
    The Hurd project is another example of volunteers for Free Software.
    It might one day benefit you directly, in the same sense that
    the GNU project has benefited you in the past, throughout our life.

    Show some respect to the developers of Hurd. Fart their way?
    Unless you are a major kernel developer from a competing OS,
    you are in no position to speak this way. It is not even a joke.



    ( I hope you are not a typical Slashdot reader, for it
    will be a disgrace if are about to read such postings on this site.)

    1. Re:Apologies Not Accepted by GreyWolf3000 · · Score: 2

      Whoever modded this down should be ashamed of themselves--really, good point parent.

      --
      Slashdot: Where people pretend to be twice as smart as they really are by behaving like children.
  32. Re:Tha HURD by Glytch · · Score: 2

    I can't speak for the FSF, since I don't work on any of their projects, but my guess is pride, ego, petty politics, and jealousy that some upstart school project snowballed and eclipsed their baby.

    (And yes, I'm aware of the difference between microkernels and monolithic kernels., folks. I don't give a flying fuck, either. I just care about the difference between a working kernel and a non-working kernel. I do appreciate the utilities, though.)

  33. Slow progress annoys by dh003i · · Score: 2

    People get sick of hearing "well, just wait a little bit longer".

    I mean, the Linux kernel has taken off in a very short time (about 10 years). It was written by one person, Linux Torvalds (almost wrote Linux Pauling there, that'd be a blooper). Why is it taking the folks working on GNU/Hurd 19+ years to make a useable kernel? Is it because there just aren't enough developers, or they're going about it in a lackluster way? Or is it something about microkernels which makes them longer projects?

    Also, why should I switch from Debian GNU/Linux to Debian GNU/HURD when HURD finally becomes useable? From my understanding, the HURD kernel is notably slower than the Linux kernel, so why would I switch? What are the advantages to this HURD kernel?

    I'm not trying to dump on the folks at FSF. I love software that the FSF has created. I love the GNU GPL. But why spend all this time and resources making another kernel which is GPL'ed? I mean, Linux is GPL'ed right now, so what's the beef? It will continue to be GPL'ed. If Linus wanted to put it under another license, he would have done so long long ago.

    I'm not saying that the developers of HURD should just call it quits. 19 years is alot of time to spend on something which never comes to fruitation. If they like doing this, they should continue developing HURD.

    1. Re:Slow progress annoys by dh003i · · Score: 2

      LOL, ok that's an exagerration. But why has HURD taken almost two decades (probably more) just to reach the point where you can USE it for daily use, where as the Linux kernel reached that point much quicker (its certainly useable today, and that's about 10 years, and it's been useable for a while)?

    2. Re:Slow progress annoys by Hitokage_Nishino · · Score: 2

      He's confusing popularity with usability.

    3. Re:Slow progress annoys by Bishop · · Score: 3, Informative

      Linux kernel has taken off in a very short time (about 10 years).

      Try two years maybe less. Seriously. People were doing real work in a Linux environment running the version 0.99.x kernels which were release in 1993. Linux ran X, vi, emacs, and the GNU tools. For a lot of acedemics on a limited budget this was more then enough.

  34. Re:Tha HURD by elmegil · · Score: 3, Interesting

    Given the common whining rhetoric complaining that they don't get enough credit for providing most of the "unix" utilities in Linux (while they do deserve credit, whining about it is not the answer), you'd think they'd be in a bigger hurry to do it themselves and do it "right". After all, Linus took what they claimed to want to do all those years ago, and did it himself in a lot less time and a lot more successfully (at least so far). That's not a ringing endorsement of the gnu/fsf ideology....

    --
    7 November 2006: The day Americans realized corruption and incompetence weren't addressing 11 September 2001
  35. well, duh by cowtamer · · Score: 3, Insightful


    Unlike other popular kernel software, the Hurd has an object-oriented structure that allows it to evolve without compromising its design. This structure will help the Hurd undergo major redesign and modifications without having to be entirely rewritten.

    And you guys are wondering why it's taken 19 years???

    1. Re:well, duh by PSC · · Score: 2

      the Hurd has an object-oriented structure [...] And you guys are wondering why it's taken 19 years???

      Says it all :-)

      --
      --- The light at the end of the tunnel is probably a burning truck.
  36. Re:GNU/Hurd by joe_bruin · · Score: 5, Funny

    when me and richard m. stallman (the m stands for 'merryweather', did you know that?) started GNU/hurd back in 1908, we were out to replace the closed-internals of the international business machines (ibm) automatic punch card tabulator, which was at use at the time in the department of the census (where me and rich were summer interns). those machines had a 2mm steel case sealed with canadian metric square screws (wherever you call them, please don't correct me). since nobody had any metric screwdrivers at the time, much less square ones, we had no access to the internal cogs and wheels of the tabulator. we definitely did not want to punch through the casing, because that would void our warranty and service contract, and we would have to contract ibm to build us a second tabulator (which cost nearly 200 american dollars, and took 7 months to assemble).

    when it (frequently) broke down, we had to call an ibm machinist to come open the case for us and oil the flywheel or unjam the transverse flying arm on the card-feeder. as you can imagine, this seemed hardly the ideal solution, because usually all it needed was a little bit of work that me and rich could easily perform (even through we were not trained calculating machine operators).
    long story short, we starting working on the GNU/hurd tabulator. the centerpiece to our system was the pipelined card loader, which could load the next punchcard while the calculating engine was stilll churning on the previous card. we had also designed the system so that you could have dual loading mechanisms, so that one would always be running if the other jammed. rich always insisted that we should publish the blueprints for our machine, so that other people in our tabulation club could also build similar machines, and help us with the design. to me the whole idea sounded a bit bolshevik, but richard seemed intent to follow through with it, and i didn't mind so much. honestly, i didn't believe he would ever be able to publish anything, given that his handwriting was quite terrible (although he was working on a new type of typewriter, the electro-macs so that he would be somewhat more legible).

    5 years later, when i was conscripted to join the great war in europe, we had a nearly complete tabulator in hand. we had solved nearly all the problems of page clipping and bending that were present in our earlier builds, and our machine could run at a rate of well over 70 cards per minute (compared to the ibm's 42). however, we never completed the loader fully, and the latest model i saw could only hold 3 cards on the loading queue, making it much less than useful (however promising).

    i've lost contact with rich during the war years. i had always assumed he's been killed in action. anyway, i'm glad to see he's still going strong with our GNU/hurd tabulator, and wish him well on it. hopefully it will be done before my great grandkids graduate college.

  37. Re:Tha HURD by Uller-RM · · Score: 5, Insightful

    *shrug* You and I may like speed... but for the average user microkernels offer more advantages.

    You and I are running servers and gaming systems; we want pure performance, and don't mind rebooting a couple of times or recompiling a kernel to change hardware or upgrade drivers. In contrast, my mom has trouble right-clicking My Computer and choosing Properties to get a driver list. For her, a layered driver system that can dynamically load and unload drivers as needed and layer itself against instability is a MAJOR plus, even if it's not for me.

    Just because I favor speed over robustness doesn't mean either is intrinsically better - it just means my needs run that way. And, being a programmer, chances are that my needs represent a very tiny fraction of the computer users out there.

  38. Remind me again.... by jone1941 · · Score: 2, Interesting

    I thought the beauty of a Mach microkernel is that it is only in charge of passing messages...if there were hard drive/serial io issues wouldn't that be a limitation of the disk io server? I'm sure someone out there has an answer for this...in fact I'm sure that if I looked hard enough I could find a good explanation of this. However, given that this project has been going on for so long, and it is probably the most idealistic of all of the GNU projects, shouldn't they have gotten the mach piece right before they started everything else? Let the reasonable responses begin...

    --
    Fear trumps hope and ignorance trumps both
  39. I guess this makes sense by happystink · · Score: 5, Funny

    They better make sure that Hurd supports hard drives up to 20 terabytes or so, since that'll be about the average size by the time Hurd ever gets done.

    --

    sig:
    See the "..for smart people" banners Wired runs here? Look elsewhere guys.

  40. Experimental is good. by matman · · Score: 4, Insightful

    I wish that fewer people would be so damned hardline pragmatic. It's worth putting time into stuff that could be cool and to try to do things in ways that are nice. Maybe it'll fail, but it's worth the attempt, even if it only serves as an example of what doesn't work.

  41. Re:Tha HURD by elmegil · · Score: 2
    Stallman is pushing this thing because its modular and relies on the Mach microkernel and the Flux OSKit library, in stark contrast to Linux's monolithic kernel design.

    Uh huh. The Linux kernel has been very modular (though not at the level of Mach) for quite some time.

    It's also worth noting that Mach was tried in the marketplace as well...where is it today? "monolithic" kernels with modular drivers are quite a bit more common out there.

    --
    7 November 2006: The day Americans realized corruption and incompetence weren't addressing 11 September 2001
  42. Re:Explanation please by Dunkalis · · Score: 3, Informative

    HURD is the kernel designed by the FSF, the people who made all of the GNU tools you and I use on Linux. It is architecturally different than all other Unix kernels in existence. Older Unix kernels are all monolithic kernels (ie, they are in a single file, vmlinuz on Linux). HURD runs servers that communicate with each other to do the functions that the single Linux kernel does. Go to the HURD website and read one of the technical docs, they are very helpful.

    --
    Slashdot is a waste of time. I enjoy wasting time.
  43. Re:Tha HURD by fsmunoz · · Score: 2

    Many reasons; nowadays the simple fact that one avoids being mistaken for what Linux users apparently became (and that is a bunch of whiners that don't care about anything but using CrossOver and pissing in the ppl that made it all possible in the first place) is a bonus.

    And no, I'm not kidding. I guess I shouldn't take /. as an indicator of what a typical Linux user thinks (if not only because 80% of ppl use IE on Windows to view the site), but if it _is_ an indicator, oh boy, what a sad view.It's only natural that some people are going to help develop an OS that stands for something, that makes a point on being Free Software (like it or not)

    Apart from that, the goals are interesting, one can learn something in OS design and I'm convinced that in the near future the GNU OS will be a viable and attractive plataform for every possible use.

    fsmunoz

  44. Re:Tha HURD by Pseudonym · · Score: 3, Interesting

    I think you might be confusing yourself.

    A monolithic kernel has no fewer layers than a modern microkernel OS. Say you want to write to a file. You make a system call, which goes through the system call interface layer, which then goes to the read() system call implementation, which then goes to the disk subsystem, which then goes to the disk driver.

    "But microkernel OSes have to copy stuff around between subsystems", I hear you say. Well that's true under Linux too. At the very least you have to copy the data from user space to kernel space. Compare this with a modern microkernel system where the data is copied straight between your user space and the disk server's user space. Same number of layers, same amount of copying.

    Having said, that I agree with you that Mach can't possibly be as fast as, say, Linux, which is why I carefully said this applied to "modern" microkernel systems, such as QNX. So my hopes aren't high for the Hurd, at least in its current incarnation. However, modern microkernel systems which run as fast as modern monolithic kernel systems are here today and they work.

    --
    sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
  45. Re:GNU/Hurd by corbettw · · Score: 3, Funny

    "when me and richard m. stallman (the m stands for 'merryweather', did you know that?) started GNU/hurd back in 1908, we were out to replace the closed-internals of the international business machines (ibm) automatic punch card tabulator..."

    You forgot to add that you were both wearing onions on your belts, which was the fashion at the time.

    --
    God invented whiskey so the Irish would not rule the world.
  46. Re:Tha HURD by David_W · · Score: 2, Interesting
    It's also worth noting that Mach was tried in the marketplace as well...where is it today?

    MacOS X?

  47. Pioneers of the DNF development model by msobkow · · Score: 2

    I have to wonder if the 3D-Realms team didn't use Hurd as their development/scheduling model...

    --
    I do not fail; I succeed at finding out what does not work.
  48. Stability by Anonymous Coward · · Score: 3, Funny

    Microkernels are much more stable than monolithic kernels. For example, Solaris uses a monolithic kernel, NT uses a microkernel. Which one runs longer? See? - that's the advantage of microkernels.

    What GNU/Mach/OSKit/HURD will be is a unix-like OS with all the famed stability of NT. I can hardly wait. It'll probably ship real soon now, just like they've been promising for the last 20 years.

    Note to RMS - if you don't put Mach in the name, you're denying them their due credit. Seriously. I refuse to type GNU/Linux ever again until I see Mach/HURD on every FSF website.

  49. Re:Tha HURD by be-fan · · Score: 2

    In all reality, microkernels are all BS these days. Monolithic kernels have gotten to the point where they can be utterly stable (I have only crashed Linux a few times, and that was in the process of using development kernels) and totally modular (almost everything in Linux can be compiled as a module, and these days, Linux can dynamically detect USB mice or video cams just as easily as any microkernel). Microkernels still have their advantages, but that's in the massively parallel NUMA market or the distributed processing market, and isn't relavent to consumers.

    --
    A deep unwavering belief is a sure sign you're missing something...
  50. Re:Tha HURD by BlueGecko · · Score: 2, Troll
    and both GNU/Hurd and GNU/Linux will each have their respective pros and cons
    For example, Linux supports more bleeding-edge hardware designs, such as serial ports, VESA, IDE, and may even fully support PCI in the near future.
  51. The dark side.. er. half.. um portion of penguins. by Art+Popp · · Score: 5, Insightful

    The best reason for HURD: "Because they want it that way."

    No one should have to justify what they want to build to you or anyone. Free software is not about the GPL. It's about freedoms. If these people want to build the most paradigmatically pure kernel ever conceived of, I think that's great.

    If they want to turn an architecturally useful chunk of marble into a useless statue of some kid named David. That's great too.

    When I enter a bunch of keywords into freshmeat and pick over the results, I occasionally ask myself, "What was this guy thinking?" Others with that same list ask that same question, but about different projects. It's the fact that we are free to combine conceptual purity, modifiability, stability, speed, and dozens of other engineering trade-offs in exactly the manner that we think is "right" that makes picking through Freshmeat like picking through a box of Dark Chocolates.

    Oddly, the same rule applies. If you don't like a particular chocolate, don't eat it; don't whine about it; just pick a different one

    I wish Mr. Stallman the fewest alpha particles and the best of luck in his noble pursuit.

  52. Heh by autopr0n · · Score: 2

    When someone beats you by ten years it has nothing to do with software paradigms.

    --
    autopr0n is like, down and stuff.
  53. Re:GNU/Hurd by hackerjoe · · Score: 2, Insightful

    Linux has nothing to do with Gnu. If you wanted to, you could make an OS using the Linux kernel & the BSD tools.

    ...except that you'd still need gnu libc to run those tools and gcc to compile them. you can easily find replacements for the gnu textutils or for bash, but libc is kinda essential.

    on the other hand it's easy to see why people drop the gnu part of gnu/linux, and it has nothing to do with credit or attribution; they're just picking out the most identifying feature of an os that otherwise has no name.

    gcc and gnu libc are critical (and incidentally account for about as much source code as the linux kernel last I checked), but all libc's and cc's aspire to work according to the same standard; so saying that your os was compiled on gcc or uses gnu libc isn't helpful to someone trying to grok its major characteristics.

  54. oi... by BiOFH · · Score: 2

    Nearly 20 years to produce something that's not practical as compared to everything that's already out. And it's not done yet. And now they're switching microkernels. Sorry... whatever, dude... no one but Stallman (and maybe Linus) could hold people in thrall over something like this for so long. It's PromiseWare. "Real soon... promise!"

    OK, let's say I'll hold out... but if, when it finally arrives -- assuming it ever does, I have to partition my [future] 10 terabyte drive into 50 slices I will most decidely be more than 'annoyed'.

    Come on, y'all... isn't pragmatism something to be sought after??? This project is a never-ending spiral of 'just wait'. What's next? "Oh, we have to switch microkernels again since the one we're using doesn't support CPU speeds greater than 999 MHz." ? (this theroretical example is merely meant to illustrate a point, I don't need a bunch of replies stating that it can do so -- that's not the point)

    Where exactly is the "cool" part?

    "In short: just say NO TO DRUGS, and maybe you won't end up like the Hurd people" - Linus

    -----

    --
    - I am made of meat.
    1. Re:oi... by matman · · Score: 2

      I wasn't saying that pragmatism is useless. I was saying that spending a lot of time trying to do something neat is worth it. You, as a user, don't need to use it for it to be a worthwhile exercise, just as every person on earth doesn't need to use Linux for it to be a worthwhile exercise.

      At least they're trying to do something neat.

    2. Re:oi... by Per+Wigren · · Score: 2

      Nearly 20 years to produce something that's not practical as compared to everything that's already out. And it's not done yet.

      Don't forget that those 20 years include writing gcc, glibc, bash and hundreds of other essential tools...

      --
      My other account has a 3-digit UID.
    3. Re:oi... by BiOFH · · Score: 2

      Flip remark:
      I didn't see the bit where Stallman said "once we're done with these hundreds of other tools".

      or

      Serious remark:
      I'm not disparaging RMS or GNU or (insert other) here. I'm talking about GNU/Hurd. The relevance of anything else has no withstanding in that regard.

      If this weren't a FSF thing no one would be defending it. But by all appearances it's a terribly flawed project that will most likely never see the light of day or, if it does, will be a curiosity for geeks to spend a day or so playing with before casting it aside.

      Stallman's done great things for computing. But I don't believe this is one of them. But I guess we'll see... in a few years.

      --
      - I am made of meat.
    4. Re:oi... by swillden · · Score: 2

      If this weren't a FSF thing no one would be defending it.

      Bull. If this were being done by some research laboratories funded by IBM or AT&T people would be very interested to see what ideas they were trying out and what results they were getting.

      The HURD may someday become useful, but even if it never does, it will still be interesting. No one else has tried to make an operating system this modular, that pushes the microkernel idea this hard.

      Actually, the project's association with the FSF is the thing that makes it *most* worthy of criticism, because the FSF is supposedly about building software for people to use, share and enhance. Instead, at least for now, the HURD appears to be more of an open research project rather than what you'd expect the FSF to be doing.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    5. Re:oi... by swillden · · Score: 2

      let's call it what it is ... an experimental research project

      That's *exactly* what I called it. Where were you?

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  55. Urban Legend by mindstrm · · Score: 2, Insightful

    That's a crock of shit.
    If the compiler is solid, it most certainly can be as fast as hand coded assembly.

    In many cases, it is FASTER than hand coded assembly; unless the person doing the assembly knows a great deal about the exact processor, cache, how to align instructions to execute faster, etctera....

    Where is compiled defined to mean "slower than assembly?"

    Yes, in some cases where the hardware is fairly new and nobody has written a compiler to optimize for the right tasks, hand coded assembly is better; it's still used quite a bit.

    1. Re:Urban Legend by Daniel · · Score: 2

      That may be true with modern processors and compilers, but I don't believe it was true when compiled languages first became popular. My compiler/processor history may not be up to snuff, though..

      Daniel

      --
      Hurry up and jump on the individualist bandwagon!
  56. Re:Solution in search of a problem? by child_of_mercy · · Score: 3, Insightful

    well the debian framework is poised to be bolted on around it.

    so you'll have all the apps, functionality of a solid, if slightly sluggish linux distro.

    in theory the more elgant design should bring performance increases,

    and the superirio code maintainability won't need Bitkeeper to submit patches for it.

    in theory.

    --
    'There is a Light that never goes out.'
  57. Re:Tha HURD by tzanger · · Score: 3, Insightful

    You and I are running servers and gaming systems; we want pure performance, and don't mind rebooting a couple of times or recompiling a kernel to change hardware or upgrade drivers. In contrast, my mom has trouble right-clicking My Computer and choosing Properties to get a driver list. For her, a layered driver system that can dynamically load and unload drivers as needed and layer itself against instability is a MAJOR plus, even if it's not for me.

    Linux can dynamically load and unload drivers with ease. It's been able to do this since the 2.0.x kernels, IIRC. Hell you can compile modules and install them without updating the kernel tree in many cases. And kernel OOPSes in the stable trees have been few and far between, to say the least.

    Yes, microkernels are nifty but there isn't a whole hell of a lot one can do that a modular monolithic kernel can't. I hear there's even work to make the networking stack itself a module. Yer mom isn't going to notice any difference between a microkernel and the hybrid kernel that Linux offers.

  58. Why look at that example? by Inoshiro · · Score: 3, Insightful

    There are plenty of other microkernels in use very sucessfully. WinNT/2k/XP, Mac OS X, MkLinux, Minix, just to name a few!

    Don't make such wide-ranging judgements based off of one case. You're counting your chickens before they are hatched.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
    1. Re:Why look at that example? by zurab · · Score: 2

      There are plenty of other microkernels in use very sucessfully. WinNT/2k/XP, Mac OS X, MkLinux, Minix, just to name a few!

      Actually you prove what I am saying. Look at WinNT - originally designed as one of the most portable operating systems. Look at it now - they dropped the last Alpha support few years back, and went x86 only; Mac OS X runs only on Apple hardware, still to be proven how well and easily it can be ported outside of that. MkLinux and Minix are not practical solutions compared to monolithic Linux packages, not even close.

      I am not claiming or arguing their success, however you define it, only pointing out Linus was right - the overdesign, performance issues are not worth their benefits. Someone still has to prove him wrong on this one, or threaten to fail the class, or whatever...

  59. Re:GNU/Hurd by aardvarkjoe · · Score: 2
    Are there any gnu-free linux distros available?


    Actually, I did the linux from scratch thing with non-GNU utilities, just for fun, and came up with a usable system. I didn't spend the time to get X and everything running, but I understand that it's possible.


    The only real requirement is that you use GCC to build the software, but you don't need any GNU software to run a Linux system.

    --

    How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
  60. depend on what you mean by "right" by g4dget · · Score: 3, Insightful
    The choice that Linus made was great for getting the project going: something that's easy to understand and easy to hack. But that doesn't mean it's good in the long run--the same could have been said for DOS. Microsoft makes such expedient choices constantly--that doesn't mean they are "right" in the long term.

    The Linux kernel is running out of steam--the software development is becoming more and more unmanageable (see the BitKeeper debates), and drivers and new functionality often take years to appear in stable, up-to-date form in the kernel.

    Those are the kinds of problems microkernels were supposed to address. I have no idea whether the GNU/Hurd does or does not address them, and even if it does, it is 15 year old technology. But I do know that Linux isn't addressing them right now, and that's a problem.

    I suspect that what will actually happen is that in a couple of years, there will be a severely hacked Linux kernel fork that keeps driver and file system compatibility at the source level for a while but otherwise goes its own way.

    1. Re:depend on what you mean by "right" by Ian+Bicking · · Score: 4, Interesting
      I have no idea whether the GNU/Hurd does or does not address them, and even if it does, it is 15 year old technology.
      The Hurd isn't really a good microkernel -- it's not really a microkernel at all, but a bunch of services built ontop of a microkernel (Mach). Of course, the microkernel is essential to the actual operation, and the services have been written with a specific micokernel in mind... but it's not unreasonable to consider the Hurd running on a different (better, more advanced, faster) microkernel. People in the Hurd community have talked about just this, though of course no one has actually done the hard work of converting it.

      But sadly, my impression of what the Hurd has shown, is that just because something is userspace doesn't mean its easy to debug. It seems like code accessibility -- even for original developers -- has not been very good. I think it's in the same way that threaded programming is much harder to debug... a complex set of interworking services is even worse.

      And while microkernels allow a certain level of modularity, it really should be possible to achieve a great deal of modularity in a monolithic kernel as well -- just not in as safe a manner. I don't know that safety is the difficult part of Linux development. Well... I'm not entirely clear on what is the difficult part, I've never tried to program on the kernel. Probably an issue of factoring -- when refactoring needs to occur across module boundries (for whatever reason) it requires different developers to communicate and agree on things (which is where the overload is occuring). But that same problem will exist in a microkernel -- only the refactoring will be occuring between processes. That's not a big difference.

      Maybe with enough thoughtfulness you can refactor everything in the Right Way, so that interfaces are entirely stable and development can occur without as much interdependence. That's not impossible -- there's a lot of experience from Linux and elsewhere to learn from. But I don't think that is related to monolithic or microkernel design.

  61. Is this really a surprise anyway? by mosch · · Score: 5, Funny

    What's the next big headline, 'Flying Cars That Turn Into Briefcases Not Available Yet'?

  62. Re:The Hurd by paladin_tom · · Score: 5, Insightful

    Bang on the money.

    If I might add to what you've pointed out, RMS has explained that the motivation for continuing development of the Hurd is that it has the potential to be something much more powerful.

    Which leads to what really bothers me about the Slashdot crowd's reaction to the Hurd. Lot's of people I know criticize Free/Open Source Software just rips stuff off, and doesn't innovate. Well, the Hurd is one of the most innovative Free Software projects around. These guys were talking about buiding a multi-server OS back at the beginning of the 90s.

    Come on, once the Hurd is finished, GNU/Hurd will be years ahead of GNU/Linux, Windows NT, or Mac OSX. The only other OS I know of that's as theoretically-advanced as GNU/Hurd is QNX another multi-server.

    This is cool stuff. Unfortunately, it seems that most people just want to complain, "Oh, does it have the drivers for XXXXX? No. Then it's useless." Grow up - the value of an operating system isn't defined by what hardware it runs on. That's much easier to change than the fundamental architecture of the system.

    --
    #define sig "Every social system runs on the people's belief in it."
  63. we need something new by g4dget · · Score: 2
    I share the lack of confidence of many people here that the GNU/Hurd will be able to deliver much of anything.

    But I think we do need a new kernel: in my opinion, Linux kernel development is not keeping up with the needs and capabilities people are creating. Every single addition seems like a major battle. Drivers take forever to get into the official kernel distribution. And the most frequent problems with installations is missing hardware support and the need to recompile the kernel.

    So, don't gloat over what happened with the GNU/Hurd. While Linux is still one of the best kernels in town, we really need more alternatives and more choice in architectures.

    1. Re:we need something new by platypus · · Score: 2

      You confuse "not getting in linus' tree" with "not existant".
      No vendor kernel (exception is debian) is using the pure linus tree, and there is a plethora of projects offering custom (patched) kernels. Add to that the possibility to roll your own kernel with drivers you download from the vendors (programmers) website, which in most cases you can even build as a module (read: completely unintrusive), which takes away one advantage of microkernels.

  64. Re:GNU/Hurd by Twirlip+of+the+Mists · · Score: 4, Informative

    Not true, friend. There are alternatives even to the GNU C library for those who object to RMS's politics.

    And whether or not one uses the GNU C compiler is irrelevant. Code compiled with GCC is not part of the GNU project, nor it is required to be licensed with the GNU license. If you prefer, though, you can use Intel's C compiler, or Metrowerks's, or whichever compiler will work with your target architecture.

    And you're mistaken about one more thing. The reason people drop the "GNU/" part of the name "GNU/Linux" is because "Linux," as has been pointed out again and again here by a persistent AC, is a registered trademark. Calling anything "GNU/Linux" without Linus Torvald's permission is infringement, and it's illegal. The name of the operating system is "Linux," and unless Torvalds says otherwise, that's the end of that.

    --

    I write in my journal
  65. Re:Just more Vaporware? by scotch · · Score: 2
    Given all the comments I've been reading it's seems to me like this is nothing more than Vaporware.

    Not to flame, but never form an opinion on anything important from the opinions expressed in the comments pages of slashdot.

    Present comment, excepted of course.

    --
    XML causes global warming.
  66. Re:Hurd developers, please by paladin_tom · · Score: 3, Insightful

    Right. Any software project that takes effort, breaks new ground, and has real academic value isn't worth it.

    Microsoft should be thanking you for spreading this attitude among Free/Open Source developers.

    --
    #define sig "Every social system runs on the people's belief in it."
  67. In 1985... by ttfkam · · Score: 5, Informative

    microkernels were the rage. HURD answered the call and started work. Now, almost 20 years later, MIT pulls the rug out with exokernels. So will we wait until 2020 to get a working model of that too?

    God bless HURD for trying to advance the state of the art and improve upon the dated UNIX model, but sheesh! I wish HURD were ready for prime time. I really do. But a working model with caveats (Linux, OSX, *BSD) will always be better than a better model that's mostly theoretical in the real world.

    That said, no one's paying the HURD developers. If it gos their nads, have at it. RMS needs to relax and realize that it is little more than a research experiment and not the second coming.

    --

    - I don't need to go outside, my CRT tan'll do me just fine.
  68. Re:Tha HURD by Pseudonym · · Score: 2

    I am shocked that someone who calls themselves "be-fan" would be calling microkernels BS. What about BeOS, for heaven's sake?

    --
    sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
  69. Re:Tha HURD by paladin_tom · · Score: 2

    There's a difference. Linus wrote a monolithic Unix-like kernel. That's a *huge* accomplishment (I know I couldn't do it!), but Unix-like kernels are well-understood.

    The Hurd, on the other hand, is a multi-server design. This is new stuff -- the only other major such system I know is QNX. Building multi-servers is something that most people have no experience with.

    So, if you're going to complain that the Hurd is taking too long to implement, I ask you this: do you think it is the place of Free/Open Source developers to innovate (which will take a long time), or only to copy what Microsoft and other proprietary software companies do?

    --
    #define sig "Every social system runs on the people's belief in it."
  70. Where is Mach today? Here are two places. by aussersterne · · Score: 3, Informative

    Try:

    MkLinux and
    Mac OS X

    Of course, both are somewhat more successful than the HURD...

    --
    STOP . AMERICA . NOW
  71. Re:GNU/Hurd by dvdeug · · Score: 2

    The reason people drop the "GNU/" part of the name "GNU/Linux" is because "Linux," [...] is a registered trademark

    Bull. That has nothing to do with it. It's all about personal preference. If it really was a legal thing, don't you think that Debian GNU/Linux (around for 6 years, and holding over a 10% share of Linux users) would be concerned? (Yes, the name is Debian GNU/Linux, and yes, if you study their history, you'll know they've been diligent about crossing their legal t's.)

    Calling anything "GNU/Linux" without Linus Torvald's permission is infringement, and it's illegal.

    Good thing Linus Torvald gave RMS permission, then, isn't it?

    The name of the operating system is "Linux," and unless Torvalds says otherwise,

    And what gives Linus Torvalds the right to say what the name of the OS is? He wrote a kernel; a cast of thousands wrote the rest, and it is assembled into an operating system by at least a dozen different groups.

  72. Mach/Hurd by IvyMike · · Score: 2, Flamebait

    Out of fairness, shouldn't this thing be called Mach/Hurd? (Or Mach/Gnu/Hurd, or Gnu/Mach/Hurd, or whatever....the point is the addition of "Mach") I suggest this for all the same reasons Stallman thinks it should be Gnu/Linux.

    1. Re:Mach/Hurd by paladin_tom · · Score: 2

      When distinguishing the current Hurd with the planned port of the Hurd to L4, we often say Hurd/Mach, and Hurd/L4 (putting the higher layer before the lower layer, like with GNU/Linux).

      --
      #define sig "Every social system runs on the people's belief in it."
  73. do you actually use it? by pitc · · Score: 2, Interesting

    I've got the hurd installed... and although I almost never use it, being subscribed to the mailing lists offers me insight into kernel development.

    Linux was created years before I knew of its existance... and now that I'm interested in understanding how it works, it seems like I missed the boat...

    --
    aoeu
  74. Re:GNU/Hurd by Twirlip+of+the+Mists · · Score: 2

    Good thing Linus Torvald gave RMS permission, then, isn't it?

    That never happened, did it?

    And what gives Linus Torvalds the right to say what the name of the OS is?

    The United States Patent and Trademark Office. The trademark serial number is 74560867. Feel free to look it up at http://www.uspto.gov.

    --

    I write in my journal
  75. Re:The Hurd by dalassa · · Score: 2

    Isn't that what is said about all projects? It doesn't matter if you are theorectially advanced. Most people want concrete advancedness. People also want to be able to use the damn thing.

    --
    Feminism is the radical notion that women are people.
  76. Re:Tha HURD by Twirlip+of+the+Mists · · Score: 2

    Stallman is pushing this thing because its modular and relies on the Mach microkernel and the Flux OSKit library....

    Okay, that's why he's pushing it today. Why was he pushing it yesterday, when it had nothing to do with OSKit?

    --

    I write in my journal
  77. Open letter by Anonymous Coward · · Score: 2, Funny

    Dear HurdTeam,

    It is with great pleasure that I received news about the latest developments on the Hurd front. I'm glad to know that you are planning for the future while building support for 2GB partitions. But really, does anybody need such insane amounts of space.

    On a different note now: I know that given all the effort you have been putting in for the last 20 odd years, you are hard pressed for time. Hence I thought I'd bring this, to your attention. Please keep this in mind, during development. However much that I'd like to see the latest and greatest feature in Hurd, I'd still want to see my copy of GNU/Hurd before the prophecies come to pass (not that I believe the so-called visionary, but you know how it is...)

    And please don't be disheartened by the comments you might read on Slashdot. They do not appreciate the hard work you folks are putting into the OS - last I hurd (hehehe) it was an OS; it still is, isn't it? Well, please keep up the good work.

    Godspeed, fellas.

    Yours sincerely,
    HurdFan

  78. Re:The Hurd by paladin_tom · · Score: 5, Insightful

    People can use GNU/Linux. You don't use the kernel (as an end-user), you use your applications.

    I think we've got a best-of-both worlds situation here: in the meantime, we've got a very good monolithic kernel (Linux), and we've got a nice multi-server in the works (Hurd), for when the time comes when monolithic kernels just can't cut it anymore.

    And regarding your statement, "It doesn't matter if you are theorectially advanced.", that's a load of BS. If no one is innovating, technology stagnates. What we're seeing here is the price of innovation. And if Free/Open Source isn't willing to do this, then we'll deserve the criticism that we're just ripping off proprietary software.

    --
    #define sig "Every social system runs on the people's belief in it."
  79. Re:The Hurd by Twirlip+of+the+Mists · · Score: 2

    Lot's of people I know criticize Free/Open Source Software just rips stuff off, and doesn't innovate.

    (Hand goes up.) That would be me. Just, you know, credit where it's due.

    These guys were talking about buiding a multi-server OS back at the beginning of the 90s.

    The thing is, though, that they're still talking about it, and haven't been able to actually do anything with it. The world has gotten bored with Hurd. It's just not interesting any more, except possibly to academics who are fascinated by it for its abstract value alone. Not that there's anything wrong with that, but don't expect me to get all hot and bothered because the design is different in some exciting but arcane way.

    --

    I write in my journal
  80. Re:Tha HURD by Twirlip+of+the+Mists · · Score: 2

    I ask you this: do you think it is the place of Free/Open Source developers to innovate (which will take a long time), or only to copy what Microsoft and other proprietary software companies do?

    It is the place of the open source developers to innovate. Most of them don't. It is the place of the FSF to engage in politics. Most everyone ignores them.

    Meanwhile, companies like Apple, and others, are doing the really interesting things.

    The open source idea sounds okay, but it's not working out the way people seemed to expect it to.

    --

    I write in my journal
  81. Re:The Hurd by paladin_tom · · Score: 3, Interesting

    The thing is, though, that they're still talking about it, and haven't been able to actually do anything with it.

    Haven't been able to do anything with it? Buddy, I've got a GNU/Hurd box running at my university. It's not vapourware. And it's rapidly making progress.

    don't expect me to get all hot and bothered because the design is different in some exciting but arcane way.

    I don't call microkernel architecture "arcane." I'm not satisfied with the long-term potential of monolithic kernels, hence I support the Hurd.

    Actually, IBM is getting all hot and bothered by this stuff. They're financing the development of SawMill, a multi-server version of Linux running on top of the L4 microkernel. This stuff is the future.

    --
    #define sig "Every social system runs on the people's belief in it."
  82. Re:Tha HURD by Twirlip+of+the+Mists · · Score: 2

    You have got to be kidding, right?

    --

    I write in my journal
  83. Re:Tha HURD by paladin_tom · · Score: 2

    Meanwhile, companies like Apple, and others, are doing the really interesting things.

    I hope you don't mean Darwin. That's just Mach and FreeBSD running in the same address space, which completely wastes all the advantages of a microkernel. There's no interesting technology there.

    --
    #define sig "Every social system runs on the people's belief in it."
  84. Re:2^64 by Twirlip+of+the+Mists · · Score: 2

    Your calculator is broken.

    2^64 = 18,446,744,073,709,551,616, or
    16,777,216 terabytes, 1 TB = 2^40 bytes

    (Amazingly, the lame(ness) filter did not vomit all over this post.)

    --

    I write in my journal
  85. Re:Umm, okay... by Usquebaugh · · Score: 2

    Nothing I'd guess. So go back to your XP machine and quit worrying about it.

    Not every project has to have a purpose. Or be useful. Some people think it's a good thing to do so off they go.

    Personally I think Plan9 is the way forward from unix. But I'm not going to rubbish the hurd project.

  86. Re:GNU/Hurd by dvdeug · · Score: 2, Informative

    That never happened, did it?

    Yes, it did.
    http://www.tlug.jp/docs/linus.html

    And what gives Linus Torvalds the right to say what the name of the OS is?

    The United States Patent and Trademark Office.

    Nope. That gives Linus Torvalds control over the word Linux. It doesn't give him any right over what the name of the OS is, if it doesn't include Linux. If it does include Linux, then GNU/Linux is as good as Red Hat Linux or Corel Linux; Linus has given explicit permission for all those names.

  87. Debian GNU/Hurd? by grytpype · · Score: 2

    Isn't there a Debian arch for Hurd? How can they offer a complete distro like Debian on Hurd if Hurd is so incomplete?

    --

    - Have a picture

  88. Re:The Hurd by Inthewire · · Score: 2, Funny

    once the Hurd is finished...

    ...there will be men on Mars growing vegetables.

    --


    Writers imply. Readers infer.
  89. You don't need a big hard drive to install Debian by MichaelCrawford · · Score: 4, Insightful
    My understanding is that Hurd works reasonably well for the hardware it's designed for. And you don't need that big a hard drive to install Debian. I have the PowerPC port of Debian on my Macintosh, and everything including /home is on a single 2 GB hard drive. The largest partition is 834 MB, well under Hurd's limit if I were to install Hurd instead.

    I think everyone here is being pretty unfair to Hurd and RMS's efforts. Hurd can easily do all kinds of stuff you'll never get Linux to be able to do, like allow unpriviliged users to mount filesystems in their home directories without causing problems for security, allowing ordinary users to hack the kernel without breaking security and so on.

    All of this has been a major advancement in computer science, and they simply haven't needed things like large partitions that of course would be needed for widespread acceptance. I simply don't see it as a big deal that they've taken so long to add the features needed for an end-user, because they had to take a long time to write the architectural underpinnings that are miles beyond Linux.

    --
    Request your free CD of my piano music.
  90. Re:GNU/Hurd by Twirlip+of+the+Mists · · Score: 5, Informative
    Oh, dude, you pretty much stuck your foot in it here. As evidence that Torvalds gave Stallman permission to use the name "GNU/Linux," you cited this article. Did you read it? Here's the salient portion.
    HY: About the GNU/Linux argument; have you talked with Richard Stallman about this?

    Linus: rms asked me if I minded the name before starting to use it, and I said "go ahead".
    Sounds good, right? But the thing is, it didn't stop there. Torvalds goes on:
    I didn't think it would explode into the large discussion it resulted in, and I also thought that rms would only use it for the specific release of Linux that the FSF was working on rather than "every" Linux system.

    I never felt that the naming issue was all that important, but I was obviously wrong judging by how many people felt very strongly about it. So these days I just tell people to call it just plain "Linux" and nothing more.
    (Emphasis mine.)

    So Torvalds, who has exclusive control over the name "Linux," as used to describe computer operating system software, initially granted permission for the use of the name "GNU/Linux," but he and Stallman had different ideas of how that variation on the "Linux" trademark was to be used. In this interview, Torvalds makes it clear that he does not approve of the use of the mark "GNU/Linux" to describe "'every' Linux system." Consequently, the name "GNU/Linux" is an infringement on Torvalds's trademark.

    If you want to call the operating system "Foonix," you're free to do so. You can call it whatever you want-- to the extent that you don't violate anybody's copyright. But you can't dilute or otherwise distort the trademark "Linux" without permission, which Torvalds explicitly denied in that interview.

    Thanks for pointing out that article. It makes the issue even more crystal-clear to me.
    --

    I write in my journal
  91. Re:Tha HURD by Twirlip+of+the+Mists · · Score: 2

    You and I obviously have different definitions of "interesting." But no, I wasn't referring specifically or exclusively to Darwin. Rather, I was referring to the fact that Apple-- partly by standing on the shoulders of NeXT-- has been able to do something that no one else have ever been able to do before: create a UNIX-based operating system that is suitable for general-purpose desktop use by nontechnical users. What's more, they've even done such a good job with OS X that they've got people paying for it! I mean no disrespect to anybody, but in a very real sense you can't even give Linux or FreeBSD to the average home computer user, while Apple has people paying for OS X. That's an amazing accomplishment. Whether you like OS X or not, you have to respect Apple's achievement.

    That's what I meant by "interesting."

    --

    I write in my journal
  92. You don't understand Mr.Stallman's reasons at all. by Inoshiro · · Score: 4, Informative

    You're totally misinterpretting Mr. Stallman's beliefs about naming.

    The free operating environment he has been trying to create for 20 years is called GNU. This encompases a kernel, userland, system libraries, compilers, etc. It's a whole, big lot of work. They started out with the editors, a C library, and a compiler so they could write the rest, and they went very far. GNU userlands started to supplant the traditional ones on most UNIX machines because GNU applications were full featured and matured quickly (try the BSD userland sometime, you'll start to notice missing options quickly), and because they were open and free.

    But their kernel, the Hurd, lagged in development. Linus took the amazing GNU userland and added his Linux kernel. The GNU/Linux system was born, a fusion of the GNU userland and the Linux kernel. Mr. Stallman believes than Linus deserves much credit for bringing a free kernel into the world (remember, it was released when BSD was dealing with much legal ramblings), and that's why it's listed as a part of the name (and not just included in the name "GNU").

    A modular layer deep in the kernel which can be swapped at will is not really relevant to it. You could ask why XFree86 is not in the name of GNU/Linux, and you'll be told it's because only the GNU and Linux parts were designed towards the goal of a free system. XFree86 is just a reference version of X11R6 which runs on x86 (and other) hardware. The same can be said of Mach, it's just a reference implementation of some software.

    GNU is the only operating environment designed to be free as in freedom from the very start, which is why Mr. Stallman asks that you properly credit the GNU contributors for their many man-centuries of effort.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
  93. Re:GNU/Hurd by amccall · · Score: 4, Interesting
    The Intel guys got Linux compiling on their compiler several months ago. Look it up. The patch was small, and it should already be in development kernels.

    So, replacement for gcc, replacement for libc(bsd/other libc's mentioned), replacement for all other standard unix utilities.

    As a side note several other OS projects use the GNU compiler to create their binaries. Should the be called GNU/Projects as well, even though they use few if any other GNU components? And I thought GNU and the FSF was about freedom....

    --
    ------ 24.5% slashdot pure
  94. Oh, of course. by Inoshiro · · Score: 2

    You're retarded because you don't want to break 10 trillion applications and reset your current "I have a browser, I have a word processer," etc progress to a state of nothingness.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
  95. You're rehashing questions already answered. by Inoshiro · · Score: 2

    Your trolling questions are answered in very nice detail here.

    In a nutshell:
    The free operating environment he has been trying to create for 20 years is called GNU. This encompases a kernel, userland, system libraries, compilers, etc. It's a whole, big lot of work. They started out with the editors, a C library, and a compiler so they could write the rest, and they went very far. GNU userlands started to supplant the traditional ones on most UNIX machines because GNU applications were full featured and matured quickly (try the BSD userland sometime, you'll start to notice missing options quickly), and because they were open and free.

    But their kernel, the Hurd, lagged in development. Linus took the amazing GNU userland and added his Linux kernel. The GNU/Linux system was born, a fusion of the GNU userland and the Linux kernel. Mr. Stallman believes than Linus deserves much credit for bringing a free kernel into the world (remember, it was released when BSD was dealing with much legal ramblings), and that's why it's listed as a part of the name (and not just included in the name "GNU").

    As to why it's not including other names, you could ask why XFree86 is not in the name of GNU/Linux, and you'll be told it's because only the GNU and Linux parts were designed towards the goal of a free system. XFree86 is just a reference implementation of X11R6 which runs on x86 (and other) hardware.

    I would like to see a GNU/BSD system myself, because the Linux kernel can be buggy, and verification that the bug is in the kernel is a lot less hard if I use one system which can boot a few different kernels.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
  96. Re:Just more Vaporware? by peter · · Score: 2

    Hurd is not vapourware. Debian has packages in unstable for hurd-i386. See http://ftp.debian.org/debian/dists/unstable/main/. I don't know if the next stable release will include hurd. (By the time it's ready for release, maybe Hurd will be finished. :)

    --
    #define X(x,y) x##y
    Peter Cordes ; e-mail: X(peter@cordes , .ca)
  97. Re:The Hurd by ealar+dlanvuli · · Score: 4, Funny

    Come on, once the Hurd is finished, GNU/Hurd will be years ahead of GNU/Linux, Windows NT, or Mac OSX

    And all of those operating systems will be years ahead of themselves....

    --
    I live in a giant bucket.
  98. If you can't say something nice... by Ageless · · Score: 5, Funny

    [this space intentionally left blank]

  99. Re:GNU/Hurd by dvdeug · · Score: 2, Informative

    So these days I just tell people to call it just plain "Linux" and nothing more.

    That doesn't mean he sues people who don't call it just Linux; that means he encourages people to call it just Linux.

    Torvalds explicitly denied

    The normal way to explicitly deny use of a trademark is through your lawyer.

    Consequently, the name "GNU/Linux" is an infringement on Torvalds's trademark.

    And as I mentioned before, Debian GNU/Linux has existed for six years, with Torvald knowing about it. To this day, SPI has failed to get a letter from Torvald's lawyers about the issue. Letting someone use your trademark in business for years with your full knowledge is not what you do if you mean to specifically deny that use.

    Honestly, I'm not sure the Linux trademark is valid anymore. I'm not familar with any attempt to police the mark, and there's a million different distributions called Linux with no quality control, which are two major issues in keeping a trademark.

  100. Re:Solution in search of a problem? by peter · · Score: 3, Insightful

    > in theory the more elgant design should bring performance increases,

    Stupid need-for-portability, making everything slow :(

    --
    #define X(x,y) x##y
    Peter Cordes ; e-mail: X(peter@cordes , .ca)
  101. Re:You don't understand Mr.Stallman's reasons at a by Arandir · · Score: 3, Insightful

    It's taken me a few years to understand RMS' perspective on the issue. But just because I can understand it does not make it right.

    From his viewpoint, linux was merely dropped into The GNU System. But from the perspective of the rest of the world, Linus made an OS and a the Linux distributions added a bunch of userland stuff from different projects, GNU being a major supplier.

    To use an analogy, Linus built an internal combustion engine, then his friends when to the local AutoParts and built a car. The name of the completed vehicle is not AutoParts/Linux.

    If you take a look from any perspective but Mr. Stallman's, a heck of a lot of GNU was adjusted to fit the Linux kernel. Linux was not adjusted to fit GNU. Just browse through the glibc ChangeLog for proof.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  102. Re:GNU/Hurd by Twirlip+of+the+Mists · · Score: 2

    That doesn't mean he sues people who don't call it just Linux; that means he encourages people to call it just Linux.

    Sorry, you must have misread. The interview didn't say "I just encourage people to call it just plain 'Linux.'" It said "I just tell people to call it just plain 'Linux.'" He owns the trademark. If he says, "Call it just plain 'Linux,'" then that's what you have to do. It's not a question of encouraging. It's black-and-white.

    The normal way to explicitly deny use of a trademark is through your lawyer.

    Nope. Trademark licensing is a business transaction, not a legal one. Unless the license is part of a larger contract negotiation-- which is often, but not always, the case-- there's no need for lawyers to be involved.

    And as I mentioned before, Debian GNU/Linux has existed for six years...

    Do you have any information on licensing agreements between the Debian organization and Torvalds? (It's Torvalds, by the way, not Torvald.) Is there any evidence to indicate that the Debian organization does not have permission to use the name "GNU/Linux" from Torvalds? In fact, isn't it true that the aforementioned interview contains information that strongly suggests that they may?

    Torvalds said, "rms asked me if I minded the name before starting to use it, and I said 'go ahead'. ...I also thought that rms would only use it for the specific release of Linux that the FSF was working on." This indicates that Torvalds clearly has no problem licensing the use of the name "Linux" as "GNU/Linux" with respect to a specific distribution. His objection is to the FSF's attempted use of "GNU/Linux" to describe any and all Linux operating system releases. Because the Debian organization releases uses the name "GNU/Linux" only to describe "the specific release of Linux" that they distribute, it's clear from his own statements that Debian's use of the "Linux" trademark is within the limits of Torvalds's unpublished guidelines.

    Honestly, I'm not sure the Linux trademark is valid anymore.

    It is. While it's true that a failure to defend one's trademark can be grounds for denying legal action to protect that trademark, it is not true that one's trademark becomes invalid through lack of litigation. Torvalds's trademark is valid until challenged in and annulled by a court of law.

    --

    I write in my journal
  103. Re:You don't understand Mr.Stallman's reasons at a by IvyMike · · Score: 3, Insightful

    You're totally misinterpretting Mr. Stallman's beliefs about naming.

    Probably.

    A modular layer deep in the kernel which can be swapped at will is not really relevant to it.

    "Swapped at will?" Not to put to fine a point on it, but this is in an article about the Hurd being delayed an indeterminate amount of time due to just such a swap.

    You could ask why XFree86 is not in the name of GNU/Linux, and you'll be told it's because only the GNU and Linux parts were designed towards the goal of a free system.

    1) I really don't believe those were the only parts developed towards the goal of a free system, so I suspect I must be misinterpreting your point, and 2) I would suspect I would really be told that you can have a perfectly reasonable Gnu/Linux system without XFree86. The GNU/Linux FAQ seems to imply it's really a matter of giving credit for effort, and not a matter of the philospohical goals.

    GNU is the only operating environment designed to be free as in freedom from the very start, which is why Mr. Stallman asks that you properly credit the GNU contributors for their many man-centuries of effort.

    Doesn't follow. Mach sure seems like it's free (and thus Hurd can use it), and it seems necessary to enabling the Hurd to exist. I still don't see why the efforts of the developers deserve any less credit for their man-years of effort towards making Hurd possible.

    I'm not trying to be arbitrary here; I don't know all the issues, and I didn't know about the planned port to a different microkernel, but it seems like the current Hurd owes a lot of credit to the existence of Mach, in a way simliar to the way Linux-based OSes owes a huge amount of credit to the existence of GNU.

  104. None of you so called geeks get it. by slashdot_commentator · · Score: 5, Insightful


    HURD is not the operating system choice of "hackers" or slashdotters. Hackers want to run computer applications (reliably and speedily). That is not what HURD is about. Its the utopian platform for computer science geeks; people who want to go beyond the current paradigm of UNIX, classic sequential computing, etc. . By abstracting the ukernel to a couple of critical operations (time slicing, memory allocation, and IPC), and moving every other operation to user mode, you have a tool that can be used to implement new concepts in computer operating systems.

    Its not an alternative to Linux. Its an orange to Linux's apple. It will suck as an alternative to Linux. It will run slower than Linux (especially if they stick with Mach). It will not run more stablely than Linux (given its increased complexity). It may be a better platform for multiple CPU configurations, be we won't know that for sure until its ukernel design is complete, and an implementation of HURD actually proves it to be faster. Very few people will want to port useful packages to HURD; they'll go to Linux for reliability and performance. HURD's purpose is not a platform to run applications. Its a platform for computer science research.

    That is the reason why I do not wish death on HURD and rejoice when there is good news for it. It does not really compete with Linux for mindshare. If it proves to be a superior platform for MP processing, only then will it have a mundane use.

    I have massive contempt for its project management. Its currently looking like the OS that will never get released. And it does not deserve a serious look until it gets a quality ukernel, like L4 (which itself is unfinished). MACH will not cut it, or its UKS(?) version.

    --
    There is no America. There is no democracy. There is only IBM and AT&T and DuPont, Dow, General Electric, and Exxon
    1. Re:None of you so called geeks get it. by slashdot_commentator · · Score: 2


      And who runs device drivers that crash the OS??? How many drivers in the stable version of Linux that crash the operating system have been kept??? Its a theoretical selling point. Right now, current distributions of HURD cannot match the uptime of Linux.

      --
      There is no America. There is no democracy. There is only IBM and AT&T and DuPont, Dow, General Electric, and Exxon
    2. Re:None of you so called geeks get it. by Christopher+Doopov · · Score: 2, Informative
      Its not an alternative to Linux. Its an orange to Linux's apple. It will suck as an alternative to Linux. (...) Very few people will want to port useful packages to HURD; (...) HURD's purpose is not a platform to run applications.
      Have you ever heard about Debian GNU/Hurd? Are the four (yes, 4) full CDs *today* just "few people [porting] useful packages" to you?! Truely amazing troll -- and modded as Score:5, Insightful -- my congratulations, you have successfully fooled the Slashdot moderators. Now please don't spread this lies, because this crap is nothing more than just lies. Maybe next time before you post something like this download Debian GNU/Hurd ISOs, burn them, install the system, count how many packages there are, and then post your opinion about it.
      --

      ~Christopher Doopov

    3. Re:None of you so called geeks get it. by slashdot_commentator · · Score: 2
      Have you ever heard about Debian GNU/Hurd [debian.org]? [...] Maybe next time before you post something like this download Debian GNU/Hurd ISOs, burn them, install the system, count how many packages there are, and then post your opinion about it.

      Yes, I did. I installed it when Debian first made its distribution public last year. I threw it out shortly after the first crash. I did not bother to count the number of packages, and it won't change the fact that xBSD will get more package support than HURD. Perhaps you could support your argument by providing a link to where those HURD application packages can be obtained. (Its not at the links you provided.)

      Only a clueless academic regurgitator such as yourself will think that when HURD gets a couple MORE of years of development under its belt, that it will run more quickly than the linux kernel. After all, expending more CPU time creating superfluous interprocess communication somehow makes kernels more efficient. Or HURD will run more stably with all those system and application threads competing with each other to get work done. Oh, people will be running on top of each other to run a slower, buggier OS. And people love to spend their free time developing for obscure platforms like xBSD, QNX, and BeOS

      Look, maybe in your world RMS is God, and believe everyone should run their lives by his dogma. But if I see the emperor is naked, I'm going to call him on it. You take one of my statements, misconstrue it, and conclude everything I say is a lie. But you and your smelly, unwashed zealots missed the whole point of my exposition.

      No commercial entity is going to run their webservers or databases on HURD in this decade (if ever). They will chose a commmercial product or chose the OS with the faster, more stable kernel (it will not be HURD). The same goes for people who use their computers to websurf, write documents, and handle email. These are applications used by the "real world".

      The value of HURD is not as a viable alternative to Linux. HURD as valdidation of RMS communist theories is only of value to RMS. HURD will not experience widespread adoption once it can create a disk partition greater than 1 GB. HURD has tremendous potential as a platform which can construct new computer paradigms we cannot implement with our current OSs. But it needs to work, and it needs to work efficiently enough for people to discount the performance hit due to its design. Porting web servers, other popular applications, or obscure device drivers to a platform that currently does not meet minimal requirements in performance and stability is a freaking waste of time. Judging HURD as valueless because it is not a viable Linux alternative is equally clueless.

      --
      There is no America. There is no democracy. There is only IBM and AT&T and DuPont, Dow, General Electric, and Exxon
  105. Re:Linux? an OS? by Twirlip+of+the+Mists · · Score: 2

    I'm sorry, but a kernel is not an OS.

    This is not at issue. The trademark "Linux" describes "computer operating system software to facilitate computer use and operation." Whether Linus Torvalds's kernel constitutes a computer operating system or not is irrelevant. The question is whether the name "Linux" refers to the entire operating system or just the kernel, and the answer is clearly the former.

    Give RMS his credit

    This isn't about credit. This is about infringement. Torvalds has the exclusive right to determine how the name "Linux," when describing computer operating system software, is applied. That's what having a registered trademark means. He has indicated that while he has no objection to the term "GNU/Linux" to describe one particular release of the Linux operating system-- be it the FSF's, or Debian's, or the one released by Handsome Pete who dances for nickels-- he does object to the FSF's use of the name "GNU/Linux" to describe all releases of the Linux operating system. Torvalds's instructions are to call the Linux operating system "just plain 'Linux,'" so that's what people must do.

    Either that, or stop calling it any derivative of "Linux" altogether. Call it "GNUnux," or what have you.

    --

    I write in my journal
  106. Re:GNU/Hurd by dvdeug · · Score: 2
    If he says, "Call it just plain 'Linux,'" then that's what you have to do. It's not a question of encouraging. It's black-and-white.

    I'm sure it's black and white to you. I'm also sure that those of us inside the community understand that he really doesn't care, and has the trademark only as a formality.

    According to Marcus Brinkmann:

    Note that Linus did explicitely say that he does not want to enforce the
    Linux trademark he owns, so this is a different pair of shoes.


    Trademark licensing is a business transaction, not a legal one.

    A signed letter, then. An interview with a third party is not the way that business decisions are communicated.
  107. OpenBEOS by Abnormal+Coward · · Score: 3, Funny

    At this rate, the OpenBEOS team will have the entire OS rewritten before the hurd kenel gets to version 1.0 :).

  108. Re:Tha HURD by Twirlip+of+the+Mists · · Score: 2

    Actually, I'd say making it actually work comes before branding. The reason why Apple doesn't use Hurd and XFree86 2 is because those things don't work, as in the often-used phrase "just works." Apple spent years and lots of money making OS X "just work." Nobody else in the world has ever had a UNIX-based operating system that "just worked." This is a significant achievement.

    --

    I write in my journal
  109. Mach-less? by geoff+lane · · Score: 2, Informative

    There comes a time when you have to cut your losses. HURD is a project that has gone seriously wrong. Mach development ENDED in 1994 (http://www-2.cs.cmu.edu/afs/cs.cmu.edu/project/ma ch/public/www/status.html)

    There's nothing intrinsically wrong with microkernels or message passing (assuming you use zero-copy mechanisms and avoid contect switches) and they do provide excellent discipline to the design process.

  110. Good Architecture, Bad Community by multiview · · Score: 2, Interesting

    I really love Hurd if you take hurd just as the bunch of source files, but I can't stand hurd if you view the Hurd project as a developer community. Most of these guys waste their time with flaming you because you are dare to try booting GNU/Hurd within proprietary software (VMWare in that case).

    Instead of giving you straight answer ignoring the sematical inaccuracies in a newbies questions, they spend the largest part of the discussion on explaining things you already know.

    I tried to join the hurd project serveral times, but before I've been able to contribute, I've been turn of by the ignorance and fanaticism of that community, therefor..

    Hurd will fail, because the Hurd community fails to attract people.

  111. Re:The Hurd by photon317 · · Score: 2


    Actually microkernels with multiple servers and virtually everything in userspace are at this point a pretty old concept. Most of the CS world already "been there, done that, moved on". I don't want it to sound like this reference is the only motivation for my opinion, but in any case a good read is the old tannenbaum vs torvalds debate on microkernels that's archived on kernel.org, from way back in the first days of linux. The point is that a lot of the supposed gains of a microkernel architecture can also be accomplished in a monolithic kernel with proper code layout and interfacing, since they're really more semantic than anything. You're paying a rather large runtime penalty in performance and complexity for something that can be mostly dealt with at coding/compile/link or even insmod time.

    --
    11*43+456^2
  112. GPL 3 by dolmen.fr · · Score: 2, Informative


    The FSF is also modifying the GNU General Public License (GPL), though the fundamental principles will remain unchanged, according to Stallman.
    "We have looked at, for example, adding a clause that explicitly states that you give a patent license when you redistribute the software," Stallman added.


    This will hopefully remove some incompatibilityies between the GPL and other free licenses such as the IBM Public License 1.0 used for Eclipse.

  113. Re:Tha HURD by DrXym · · Score: 2
    Unfortunately, such talk is moot these days since modern monolithic kernels such as Linux are capable of dynamically loading and unloading drivers - they're called modules.


    Anyway, in terms of stability I have yet to see anything that beats Linux. I've been running it for 4 or 5 years in various roles on some terrible hardware and I'm actually taken aback when it crashes it happens that rarely.


    Micro kernels are not immune from crashes either. My OS X box crashed once too, which again surprised me since it's been a very stable system.

  114. Re:Innovations Vs Practical system by adb · · Score: 2

    I don't think the Hurd can ever catch up as a Unix system. The interesting things about it have to do with how it's not like a modern Unix: any user can completely change how the OS works for himself or any other user who cooperates.

  115. Could someone explain something to me? by 10Ghz · · Score: 2

    HURD is a microkernel right? Then what is Mach microkernel? People say that HURD uses the Mach Mircokernel, but isn't HURD kernel in itself? What is the relation between HURD and Mach (and the other microkernels out there)?

    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  116. Glad you noticed!!! by 3seas · · Score: 3, Interesting

    How many commenting would have never noticed any delay had they not read it here?

    Regardless of any negativity being expressed here towards the efforts of the Hurd Developers or the goal, this is a project that needs to be done.

    I have no doubt that had Linux not come along, there would have been more man power and efforts put into the Hurd these past years.

    Of course Linux was a distraction for many, yet it was also NOT a distructive distraction. Alot of GNU and GPL software has been developed and put into use. Enough So that, as we all know, MS has taken notice and has even launched a competitive campagin against not just Open Sourse, Linux and GNU, but with a focus on the GPL.

    What software there has been made to run on Linux, can and probably already has been ported to run on the Hurd....(except for a few packages that just don't make sence to port as they deal with monolithic kernel issuse that don't exist in the Hurd). The count of software packages ported is in the thousands.

    Even the drivers written for Linux are usable on the Hurd.

    All of that porting and compatability was/is alot of work for which the Hurd Development team has done. So there has been energies going into alot more than just the hurd core.

    Perhaps the really good part of all this is that MS probably doesn't have a clue as to what to expect of developer who will develop applications for the Hurd, to take advantage of the hurd. And it should be understood that the hurd opens the door up a lot more for development innovations.

    So what will you have when the Hurd is officially publicly released... production version...??

    You will have what appears to be no or very little different than using Linux. On the surface. But under the hood.... It's a more versatile, stable and in sum of.... overall more powerful in ability to bring about advancements.

    There are quite a few other OS's being developed today, under the open source idea. And there is nothing about the Hurd that says you cannot attach a personal choice smart user space interface OS to the Hurd. Integrating it to benefit from the security of the Hurd, the GNU number crunching software already written, etc... thru the IPC of the Hurd....

    I like the idea of plugging my personal Smart Interface OS into a hurd system for such benefits. A 3" CD, a smart card, or some yet to be developed re-writable device I can take with me.

    1. Re:Glad you noticed!!! by iggymanz · · Score: 3, Insightful

      I have no doubt that had Linux not come along, there would have been more man power and efforts put into the Hurd these past years.

      Really, this is getting to be too much.....after over a decade of floundering around, the FSF has yet to produce anything even remotely useful as a production operating system kernel. Linus and the people who worked on Linux did that in 7 - 8 years.

      It's great what the FSF has done, to give the world a compiler to produce free software, and the tools and utilities to make Linux and other OS's a finished OS. And even the Hurd as a computer science experimental kernel to play with new ideas.

      But it is ridiculous to say that Linux has distracted from the Hurd effort....the Hurd simply is not about designing a useful kernel.....it is a playground for ideas in OS architecture, and it will be many more years of flounder/play/redesign before it is known what ideas in there will even be useful for a production kernel,

  117. RMS by thoolihan · · Score: 5, Interesting

    I'm sure I will get flamed on /. for this one, but since 98% of the comments are along the lines of "down with RMS", I have to say this.

    At some point you have to decide if you are going to go along with the pithy flames or do real research. It's not popular, but it reveals the truth. If not, go to the next comment, this isn't for you.

    From a proctical standpoint, I understand the "Linux" side of the argument. However, people make that argument with statemnt like... "Don't do drugs, you'll end up like the Hurd peopl" - LT. RMS makes his argument respectfully on the GNU website and encourages people to use GNU/Linux. On the GNU site, he says the easiest and best way to start using free software is to go get a GNU/Linux distro. Personally, I respect people who make their arguments with facts instead of one-liners. If you buy things because they sound like a good quick answer, then you start going for things like "trusted computing".

    Finally, since this is a discussion of the HURD kernel: I think people should find this interesting. The GNU tools we are already familiar with are going to get a microkernel. Merit arguments aside, there are a lot of people who choose/like microkernels (apple, *BSD). Also, it's a kernel project that offers a ton of work to be done. After all, 1GB partitions is a sign that there is a long way to go. Entry level kernel hacking on a system that has a LONG way to go is easier than "even though you've never kernel hacked, figure out how to save a few cycles with this kernel module that has been working for five years". Also, keep in mind, the HURD has one major advantage over the Linux kernel. There is not a one man bottle neck.

    Personally, I like the linux kernel and use several Gentoo systems, and some OpenBSD. But I always welcome another choice in software and look forward to seeing the HURD in a more usable state.


    There is a fine line between picking your battles and cowardice

    --
    http://unmoldable.com W:"No one of consequence" I:"I must know" W:"Get used to disappointment"
  118. Linux is a victim of its own success by Royster · · Score: 2

    It's turned out to be a pretty portable kernel. It runs on my Sharp Zaurus as well as large clusters and IBM mainframes. The initial development was very x86-centric, and it still is to some extent because that's where most of the users are, but most of the growth in the size of the tree is all of the different architectures supported.

    I see the BitKeeper debate as one of ideology v. pragmatism. The GNU ideologue says "Use only free software" and the pragmatist says "Use free software if its up to the task". I've always sided with pragmatists.

    --
    I have discovered a truly marvelous sig, unfortunately the sig limit is too small to contain i
  119. Re:Could the Linux kernel be used. by Espen+Skoglund · · Score: 2

    This has been tried (albeit not using Linux). It's called Mach, and is by many people considered somewhat of a failure.

  120. Isn't all this just posturing and rhetoric? by Real+World+Stuff · · Score: 2, Interesting
    I believe Microsoft has been doing this (software) for years, and has made a very profitable business. It is hard to argue with a model that can defeat the U.S. government, and have 40 billion dollars in the bank. Sure it is not free like your siter after a cuple of beers, but business drives the economy.

    OTOH something to think about
    " The FSF is also modifying the GNU General Public License (GPL), though the fundamental principles will remain unchanged, according to Stallman. "We have looked at, for example, adding a clause that explicitly states that you give a patent license when you redistribute the software," Stallman added. "
    --
    If we don't fight for ourselves no one will.
  121. Re:Cool stuff? by paladin_tom · · Score: 2

    No, it's built on the Mach kernel.

    --
    #define sig "Every social system runs on the people's belief in it."
  122. Re:Tha HURD by paladin_tom · · Score: 2

    Actually, microkernels have the potential to increase the performance of applications such as databases and multimedia.

    A very good read that I recommend to anyone interested in operating systems is Towards Real Microkernels by Jochen Liedtke. It explains the advantages of microkernel-based systems, what is wrong with older microkernels like Mach, and why current second-generation microkernels are better.

    --
    #define sig "Every social system runs on the people's belief in it."
  123. Have any of you actually tried the HURD? by rootmon · · Score: 2, Informative

    I'm reading a lot of misinformation. First of all, THE HURD IS NOT A KERNEL! The HURD standards for Hird of Unix Replacing Daemons, wherein Hird stands for Hurd of Interfaces Representing Depth (a mutually recursive acronym according to the FAQ). The HURD is a bunch of servers that provide services around a microkernel. The revolutionary thing about it is that many of the traditional "kernel" tasks are moved into userspace. Result: the users are empowered. Why should mounting directories, shring NFS volumes, etc, require root? Normal users can use devices and network resources that previously only the administrator could control. For example, a normal user couldn't share the / volume, but he could share his home directory over the network, or mount a remote FTP site as a local folder in his home directory. (Yes, I did say mount FTP, HURD has some exciting new features like FTPFS, HTTPFS, etc, because so much of the implementation is left to the servers rather than the kernel.) Also, security is better, rather than root being the default access level, the default is guest priviledges, so priveledges start at none and are "tickets" are issued as credentials are elevated. Also, the Unix everything-is-a-file is taken further, where everything is part of the filesystem, including servers, etc. The HURD is a thing of beauty, and unless you've seen it down't knock it. I have a HURD test box on my LAN and it's running X with IceWM, Apache, FTP, NFS, etc. With some sound drivers and a complete pthreads implementation (which was just released), it could function as a workstation too. I don't see why we have to fight over Linux VS Hurd! Why can't we have both and pick the right tool for a specific job. I mean, we're the winners here, because the HURD gives us another *CHOICE*. It's about more freedom! So don't knock the HURD, most of the work is being done by a few programmers, Marcus Brinkman, Neal Walfield, and Thomas Bushnell. If Linus hadn't had the help of an army of developers where would Linux be? So give these guys their credit and realize that their efforts are giving you more freedom!

    --
    "As flies to the wanton boys are we to the gods; they kill us for sport." - William Shakespeare, King Lear
  124. You'refilling my mouth with words not mine. by Inoshiro · · Score: 2

    "If you care about what you are running on your system, you should already know who contributed what aspects."

    Most people don't know, even if they do care. Head over to a LUG meeting. I'd wager the great majority of them care, but only a few properly know the history of the system. Obviously if they're interested, education is something that should be given to them. That's why I tell them about the history of the system, and clarify for confused people (such as yourself) about why it's called GNU/Linux.

    "Under this logic, windows graphic and multimedia designers should be calling their machines Adobe/Windows or Macromedia/Windows, etc, etc, etc."

    Microsoft does follow the same naming contention very closely:
    Windows 95
    Windows 98
    Windows ME
    Windows NT
    Windows XP

    First is Windows, which encompases the API (libraries) and interface (UI) and most of the userland (the ubiquitous Notepad :)). Second is the kernel (the "friendly name" of it), with flavours following ("Professional," "Server," etc). RMS also answers why it's GNU/Linux instead of GNU Linux because:
    "Following the rules of English, in the construction "GNU Linux" the word "GNU" modifies "Linux". This can mean either "GNU's version of Linux" or "Linux, which is a GNU package." Neither of those meanings fits the situation at hand."

    The BSDs also follow this naming contention, with Free, Open, or Net prefixing the BSD kernel. GNU/BSD would be a BSD distribution which has a complete GNU userland around a BSD kernel, with the slash to denote that they are logically separated.

    As for more credit than credit is due: I have no problem for giving RMS the credit for starting freely available, modifyably software back in the 1980s before anyone else was developing software for the purpose of giving it away. If you don't like it, TS. Unless you build a time machine to beat him to the punch, he deserves the credit.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
  125. Re:GNU/Hurd by evilviper · · Score: 2
    I'm well aware of that... It's just a subject that annoyed me too much to ignore it.

    Don't you think a conversation would start if someone had posted this:

    Abortion is okay

    --God


    Joking or otherwise, the topic was brought up.
    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  126. Once the HURD is finished? by McSpew · · Score: 2

    Come on, once the Hurd is finished, GNU/Hurd will be years ahead of GNU/Linux, Windows NT, or Mac OSX.

    Don't you mean if it's ever finished, it ought to be years ahead of whatever operating systems are in use on the by-then-ubiquitous quantum computers? Don't get me wrong, I love the idea that the HURD is pushing the limits of what OSes can and can't do, but it's much closer to a research project than an operating system. It's so ambitious that it can't ever just freeze the feature set and issue a release.

    We've seen this kind of thing before. Borland suffered from it with its Windows port of dBase. Every time they were about to release, they'd discover some other new thing they just had to build into it, so they'd burn the codebase to the ground and start over. I don't remember when Borland finally released dBase for Windows, but it was at least two or three years late and by the time it shipped, FoxPro for Windows had stolen its market and dBase was irrelevant.

    The point isn't that the HURD isn't cool (it is), the point is that the HURD takes too long to get where it's going, so by the time it gets there, it's no longer good enough. Who cares how cool the underlying OS features are if it can't support partitions greater than 2GB or common devices like USB mice?

    I agree with the common point made here. If the HURD had shipped years ago, even as an incomplete OS, it would at least have some chance of improving and getting more people to contribute code. As it stands now, only the Stallman^H^H^H^H^H^H stalwart are involved and the project continues to drag on forever.

    "...And in other news, Valve Software still declines to announce a release date for its mythical TeamFortress 2 product...."

  127. Re:Tha HURD by Twirlip+of+the+Mists · · Score: 2

    What are you, an idiot? Read the rest of my post. I said-- paraphrasing here-- that you can't give desktop Linux away, but Apple has people paying for Mac OS X. That demonstrates that Apple has done something that all the Linux and BSD hackers in the world have been unable to do: create a UNIX-based operating system that ordinary people actually want to use.

    You can be as sarcastic as you want; it doesn't diminish Apple's accomplishment.

    Yet, community-led initiatives are actually becoming a viable alternative to the existing dominant OSes, competing with companies which have ungodly ammounts of money and huge user bases, and you're not impressed or excited.

    That's because, as you say, "community-led initiatives" (which is what I call "hobby projects") are not viable alternatives to the existing OSs. If they were, people would be using them. But instead of downloading Red Hat Whatever for free, they're still buying Mac OS X by the truckload. Mac OS X was initially very sluggish-- it's gotten a lot better with each release-- and incompatible with tons of older Mac software. And yet people pay good money for it. Doesn't that tell you something?

    --

    I write in my journal
  128. Re:I disagree...IANAL by Twirlip+of+the+Mists · · Score: 2

    Linus gave RMS permission to call anything Gnu/Linux

    Nope. Read the interview again. He gave RMS permission to call GNU's distribution of Linux "GNU/Linux." Only thing is, that's not what RMS was asking for. So RMS does not now, and never has, had permission to use the "GNU/Linux" name the way he wants to.

    I know RedHat, SuSE, Debian, Slackware, and Gentoo use kernels built by Gnu development tools

    That's not important. Microsoft has repeatedly accused the GPL of being "viral," and of "infecting" every piece of software it touches. The big counter-argument to that point has been the GCC license, which explicitly says that programs compiled with GCC are not required to carry any particular license, and are not part of the GNU project. I use Mac OS X, and Apple's compiler is based on GCC. When I compile SurfWriter, I feel no particular compulsion to call it "GNU/SurfWriter." What development tools you use has no bearing at all on what you should call the end product.

    Any software compiled with Gnu, upon a Linux-based OS, defines the software as Gnu/Linux.

    By that same reasoning, any software compiled with GCC on Mac OS X defines the software was GNU/Mac OS X. Which is absurd. Your argument is flawed.

    It also has nothing whatsoever to do with any other argument put forward to justify the bastardization "GNU/Linux."

    --

    I write in my journal
  129. Re:The Hurd by paladin_tom · · Score: 2

    There are performance advantages of a microkernel that come from your ability to run multiple memory servers with different policies on a single machine, and hence have proper support for regular applications, as well as realtime applications such as multimedia.

    --
    #define sig "Every social system runs on the people's belief in it."
  130. Re:Linux? an OS? by Twirlip+of+the+Mists · · Score: 2

    That's a mighty strong statement to be putting in somebody else's mouth. Might want to back off of that position just a tad before you start to look like an idiot.

    Trademarks are not just "legal formalities that only exists because of lawyers and idiots". Whether any given person believes that they are or not is irrelevant. Trademarks, and the rules governing them, are an important part of intellectual property law. Of course, I know that the most vocal Slashdotters will assert that all intellectual property law is baseless and corrupt, but those people simply don't know what they're talking about, so I won't even bother responding to such arguments.

    If you want to violate the laws governing the use of trademarks, that's fine by me. But don't argue that they don't apply. If you want to ignore Torvalds's own explicit instructions, that's fine too, but don't argue that he doesn't care whether you do.

    --

    I write in my journal
  131. Re:BSD microkernel? by MobyTurbo · · Score: 2
    there are a lot of people who choose/like microkernels (apple, *BSD).
    BSD (which is an OS that I've run and respect) is *NOT* a microkernel, in fact it's been implemented as a bit more monolithic than the Linux kernel. BSD is usually pointed to as an example of a monolithic kernel... Maybe the fact that Apple uses BSD userland has confused you a bit, no offense.
  132. Re:Innovations Vs Practical system by adb · · Score: 2

    Shrug. It's no harder than writing for all the other different flavors of Unix, and a hell of a lot easier than dealing with Windows or (shudder) pre-X MacOS. (Takes off "been there, done that" hat.)

  133. Re:Tha HURD by Twirlip+of+the+Mists · · Score: 2

    So stipulated. But to be fair, let's describe Apple's work as being interesting in the "sell millions of copies and become, in less than a year, the world's largest supplier of UNIX-based operating systems" sense, while Hurd is interesting in the "Hurd who?" sense.

    --

    I write in my journal
  134. Re:GNU/Hurd by Wesley+Everest · · Score: 2
    It's kinda funny. Linus says he doesn't see what the big deal is about names -- people generally use his name to refer to distributions built around his kernel, and he's happy with that.

    But then big bad self-important Richard Stallman comes along and says that given that Linux wouldn't exist if it weren't for the GNU project, and given that much of the software included in Linux distributions is a product of the GNU project, and given that most of the software included uses the GNU license, the system as a whole should share credit with the GNU project and call it GNU/Linux.

    Note that there is no suggestion to name things Richarix or Stallix. Anybody else see the irony? I mean I have great respect for both Stallman and Torvalds, and I think they have both made great contributions. I even respect both of their views on the naming of Linux vs. GNU/Linux. But, really, if you're going to whine about self-important people, it seems to me that it would be easier to make a case that Torvalds is being egotistical for insisting that the system be named only after himself, with no other people or projects sharing the credit.

    If anything, you could say that Stallman only cares about promoting his pet project, while Torvalds only cares about promoting himself. Of course, you'd be wrong to suggest such a thing, since both of them spend more time creating software than promoting a name for it... (as opposed to many people who post on slashdot)

  135. the whole world is a desktop -- not by g4dget · · Score: 2

    If it's not in the main kernel distribution, it might as well not be there for many users: patching the kernel is beyond their ability. And it's beyond my own ability (or at least patience) as well for a number of devices I own: they require a cross-platform development environment to be installed, and few people seem to have figured out how to distribute pre-compiled kernel modules.

  136. Re:Linux? an OS? by dvdeug · · Score: 2

    Trademarks are not just "legal formalities that only exists because of lawyers and idiots".

    I never said they were. I said the Linux trademark is.

    all intellectual property law is baseless and corrupt, but those people simply don't know what they're talking about

    You're amazingly arrogant, aren't you? It seems like anyone who holds an opinion you disagree with are idiots and fools.

    If you want to ignore Torvalds's own explicit instructions, that's fine too, but don't argue that he doesn't care whether you do.

    I will so argue, if I so believe my argument is correct. My opinion is that you put legal significance to a causal statement made by some one who had no intent of it having legal significance. Again, your arrogance is overwhelming to presume to tell others what arguments to make and not to make.

  137. Once again, something seems missing. by Inoshiro · · Score: 2

    RMS is not being given credit at all. The GNU contributors (of which RMS is a part) is being given credit, when you say GNU/Linux.

    If you have just the kernel, only the kernel running your system, then you have a pure, only-Linux system. Every disturibution I can think of is based on the GNU/Linux marriage. I don't see why this is so hard for people to understand, the entire system is more than a kernel.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
  138. Re:I disagree...IANAL by Twirlip+of+the+Mists · · Score: 2

    The BUILD of a kernel, for example, as reported by the uname user-land tool, says operating system is redhat-pc-gnu-linux.

    Except it doesn't. I have four UNIX computers in front of me. Their "uname -s" strings are as follows:

    Linux
    Linux
    FreeBSD
    Darwin

    I can't find a machine that reports redhat-pc-gnu-linux.

    RMS is being taken the wrong way, I think, or could I be wrong and he realy is an asshole?

    Bingo. ;-)

    --

    I write in my journal
  139. and dont donate to the FSF either? by QuantumG · · Score: 2

    If you're talking about a bunch of people on
    Sourceforge (aka, The Projects) doing something because they think it is interesting them I'm all for your chocolate analogy. Unfortunately, the HURD is a project financed by donations to the Free Software Foundation. So if I don't like the particular chocolate that is the HURD, then I shouldn't donate to the FSF? That kind of seems like throwing out the baby with the bath water isn't it?

    This is truely another example of democracy gone wrong. Some people get upset when others express their opinion, or try to convince you to change yours. Often their justification for this outrage is to point to the voting system, or worse yet, the market. They say "hey, don't try to make me think, just vote against me or don't buy my product". I cant count the number of times I have been in a group situation and heard the immediate call for a vote, without even the slightest preliminary discussion of the issues. Unfortunately people believe this is the only fair way to resolve conflict, but this not how democracy works!

    --
    How we know is more important than what we know.
  140. Re:Tha HURD by Twirlip+of+the+Mists · · Score: 2

    Apple sold 100,000 copies of Mac OS X 10.2 during the first weekend it was available. At $129 each, that's $12,900,000 in gross revenue for just that one weekend. Red Hat, on the other hand, sold 4,802 copies of their software in the entire month of July. Even if you're generous and assume all of those units were the $150 "Professional" version-- they almost certainly weren't-- that comes to $720,300 in revenues for an entire month. If Red Hat were able to do that for an entire year, they wouldn't be able to match the gross sales of Mac OS X for one weekend.

    Note that this doesn't count units of Mac OS X that were bundled with a new machine; this only counts actual retail packages sold. The number of units of Mac OS X 10.2 shipped is somewhat higher than this figure, making it difficult to estimate gross revenue from all sales of Mac OS X-- bundled and retail-- until we see the annual report.

    (All figures from PC Data. If you have other figures that lead to a different conclusion, we can discuss them. Until then, STFU about sales figures about which you have no information.)

    --

    I write in my journal
  141. Re:Solution in search of a problem? by child_of_mercy · · Score: 2

    For sure,

    I dunno if it will work but the question was why do they bother.

    At one level this could be viewed as a CS experiment, if it can't be made to work then there's a lot of CS theory that should be reviewed.

    --
    'There is a Light that never goes out.'
  142. Re:The Hurd by paladin_tom · · Score: 2

    The only interesting thing about HURD is that RMS is the lead developer!

    Actually, RMS isn't the Hurd's lead developer. He's just the head of GNU, and the Hurd is a GNU project. And yes, the Hurd does get extra exposure by being a GNU project.

    I'm interested in the Hurd because it's a Free mutli-server. SawMill is also interesting.

    If you can find me a POSIX-compliant multi-server written by a single person in less time than it's taking the Hurd to get finished, I'd be very interested to hear about it.

    --
    #define sig "Every social system runs on the people's belief in it."
  143. Re:GNU Hurd harmful to Open Source movement... by Cro+Magnon · · Score: 2
    Besides, who's ever going to want to admit to running an operating system that rhymes with "Hurl".


    It does NOT rhyme with "Hurl"! It rhymes with "Turd"!
    --
    Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.