Slashdot Mirror


Plan9 is now Officially Open Source

DrSkwid writes "The OSI have approved the revised license for the plan 9 operating system according to attendees returning from this year's Usenix Bof."

21 of 399 comments (clear)

  1. Re:How long until? by thoolihan · · Score: 5, Interesting

    I know you're kidding, but this brings up an interesting question. IIRC, Dennis Ritchie worked on Plan 9. He also wrote the original Unix at Bell Labs. If he wrote certain functions similarly (as one would expect him to reuse code snippets he had successfully written before), could there be intellectual property issues. Could a company in SCO's position claim that he has to completely avoid writing anything that similar to the code he wrote for a previous company?

    Just a thought...

    -t

    --
    http://unmoldable.com W:"No one of consequence" I:"I must know" W:"Get used to disappointment"
  2. excellent news by jacquesm · · Score: 3, Interesting

    After the QNX thread a bit ago, this is probably the best news possible. Plan 9 is a nicely evolved version of UNIX, it is very scaleable, and 'orthogonal' (you can run a new version of the window manager in a window in the old one!).

    If there ever was a viable alternative to the monolithic unices then Plan 9 is probably it.

    Macro kernels are pretty much like turtles and sharks, very well adapted to living today, but dinosaurs nonetheless. Let's give this one the attention it deserves and see how it stacks up against the 'hurd', time to evolve !

    1. Re:excellent news by renehollan · · Score: 2, Interesting
      Macro kernels are pretty much like turtles and sharks, very well adapted to living today, but dinosaurs nonetheless.

      That's one of the more insightful comments I've seen in a long time.

      Personally, I run a Linux kernel, and have worked with both Linux (continue to do so) and FreeBSD professionally, but I always found the idea of a monolithic kernel, you know, somewhat inelegant.

      Notions like the Hurd, for example, therefore, are appealing, in an academic sense, but suffer from the chicken and egg problem of "I've got to have something working NOW for my existing application needs and don't have time to contribute to the next great thing". Sigh, would that I were back in school and had time to spare on kernel work. But, not 10 but 20 years have past me by as I run on the employment treadmill, with little time for such projects (though, if there were a Linux-derived O/S cross-development environment for the Hurd, that might be interesting to play with).

      So, good luck to Plan9 and other post-modern kernels and operating systems.

      --
      You could've hired me.
    2. Re:excellent news by jacquesm · · Score: 2, Interesting

      plan 9 is a computer program and as such does not have a 'will' or a 'want'.

      The micro-macro debate never ended, it's just that the macro camp has a head start in terms of programmer experience and installed base.

      Plan 9 has not been tested for scaleability outside of it's development lab, but on paper it scales better than anything that is in the marketplace right now, if only because the clustering is built in right at the lowest level.

      The real 'unlock' for microkernels is advances in message passing techniques, which so far caused overhead to be added to every message passed.

      With the new page table based message passing algorithms (where the message is 'moved' by mapping a page from the sender to the receiver instead of by a byte-by-byte copy) the playing field has been equalized and micro kernels using message passing are now competitive performance wise. Newer technologies allow such memory management tricks to be played transparently over the network, but this will come with a penalty (same with a macro kernel).

  3. Hierarchical "File" System for all resources by RevMike · · Score: 2, Interesting
    This sounds an awful lot like the way JNDI is used to locate resources within a J2EE system.

    Anyone with experience with both Plan9 and J2EE care to comment on similarities/differences?

    ObSCOComment: System V represented many resources as files. This must be derivitative of SysV. Get the lawyers ready!

  4. Long term, does this mean anything? by Jack+William+Bell · · Score: 5, Interesting

    My first subject line was 'Cool', but then I changed it. Why? Well, I have been interested in Plan 9 for a long time. I especially like the services-based architecture. In many ways it is a project with an awful lot of potential. But...

    Problem 1: What is it good for? Right now Plan 9 has no compelling applications and a dearth of the applications most people use daily. This might be fixed soon as people port things like OpenOffice to it, but don't hold your breath.

    Problem 2: It is a research tool, and may never be more than that. Chances are, any truly compelling features in Plan 9 will soon find their way into Linux and even MS Windows.

    Problem 3: Overcoming the installed base. It took Linux nearly ten years to achieve name recognition, and it still is running a distant third on the desktop. What does Plan 9 offer that would make me, or you, want to spend time installing and learning it? Especially considerint Problem 2 and Problem 1.

    Problem 4: Wrong direction. In my opinion the real important projects right now are ones that are removing the distinctions between OSs. Cross platform tools like Python, Chandler, Mono and Mozilla. Using standards-based DHTML as the UI. Why add another platform to the mix when the real goal is to become platform agnostic?

    It all sums up to the same issues that squeak smalltalk has: Everything about it is great, but no-one uses it for anything real.

    Of course all these problems I describe are based on my opinions, needs and preferences. Your mileage may vary. But I be most people's won't...

    --
    - -
    Are you an SF Fan? Are you a Tru-Fan?
    1. Re:Long term, does this mean anything? by tuffy · · Score: 4, Interesting
      Problem 4: Wrong direction. In my opinion the real important projects right now are ones that are removing the distinctions between OSs. Cross platform tools like Python, Chandler, Mono and Mozilla. Using standards-based DHTML as the UI. Why add another platform to the mix when the real goal is to become platform agnostic?

      What good is being platform agnostic if all platforms are completely homogenous? Clearly Plan 9 isn't going to take over the world, but that was never the point. What is important is that the best aspects of Plan 9 can be incorperated into existing platforms like Linux and *BSD and generate some real innovation without too much disturbance to the existing software base. Because it sure looks like the deeper innovations coming out of Plan 9 are more helpful to me than the more superficial stuff coming from Gnome/KDE.

      --

      Ita erat quando hic adveni.

    2. Re:Long term, does this mean anything? by F2F · · Score: 4, Interesting

      Problem 1: What is it good for? Right now Plan 9 has no compelling applications and a dearth of the applications most people use daily. This might be fixed soon as people port things like OpenOffice to it, but don't hold your breath.

      it's good for research. an antidote to Systems Software Research is Irrelevant.

      Problem 2: It is a research tool, and may never be more than that. Chances are, any truly compelling features in Plan 9 will soon find their way into Linux and even MS Windows.

      Judging by how hard it is to bring Private Namespaces to Linux I can tell you that some of Plan 9's concepts will never make it back to UNIX. Some things in UNIX' design are just too hard to fix -- that's why Bell-Labs started this radical new OS (14 years ago).

      Problem 3: Overcoming the installed base. It took Linux nearly ten years to achieve name recognition, and it still is running a distant third on the desktop. What does Plan 9 offer that would make me, or you, want to spend time installing and learning it? Especially considerint Problem 2 and Problem 1.

      Plan 9 does not want to be a desktop OS but a research one. Its goal is not to crush Microsoft, it simply wants to fix the problems that cannot be easily fixed in UNIX today.

      Problem 4: Wrong direction. In my opinion the real important projects right now are ones that are removing the distinctions between OSs. Cross platform tools like Python, Chandler, Mono and Mozilla. Using standards-based DHTML as the UI. Why add another platform to the mix when the real goal is to become platform agnostic?

      to quote: "That's the good thing about standards -- there's so many to choose from"...

  5. Does this still make Richard Stallman cry? by iamdrscience · · Score: 3, Interesting

    Was the Plan9 license ever changed? I know for a while the FSF had a page listing the reasons why they don't consider Plan 9 a "free" OS regardless of the openess of it's source (blah blah, difference between open and free, blah blah, speech, blah blah, gratis).

    I think it'd be really great if Plan9 were released under a more "free" license.

    ...so basically I'm too lazy to use the internet to answer my questions... please find answers for me slashdot!

  6. Powered by Plan 9? by randomErr · · Score: 2, Interesting

    Is the site powered by Plan 9? I wonder because it seems to have been suffering from the /. effect.

    --
    You say things that offend me and I can deal with it. Can you?
  7. Re:How long until? by cshark · · Score: 1, Interesting

    Interesting. Does anyone know how Dennis Ritchie feels about the Unix debockle?

    --

    This signature has Super Cow Powers

  8. Of Course by w.p.richardson · · Score: 4, Interesting
    Consider this analogue from the music industry:

    John Fogerty sued for sounding like John Fogerty!

    Fortunately, he won that case, but who knows how a similar case in the computer industry would turn out?

    --

    Curb CO2 emissions: Kill yourself today!

  9. License Compatability between Linux & Plan 9? by FreeUser · · Score: 3, Interesting

    This is really great news for Linux. For too long we've been trapped in the out-moded hierarchical/graphical paradigm. Plan 9, with its revolutionary "factotum" and "secstore" structures, could really provide a breadth of fresh hair to the Linux kernal, putting it head and shoulders above Windows.

    While it is nice that the new license conforms to the requirements of the Open Source folks, that does not mean it is compatible with the GNU General Public License (GPL) under which Linux is written. Indeed, not even all free software licenses are compatibel with the GPL (though the vast majority certainly are), and as yet I have not been able to find any commentary from the FSF on whether the modified license qualifies as "free", much less is GPL compatible (the old one certainly wasn't, as RMSes comments posted to this thread quite definitely explain).

    So, before getting too excited about Plan 9's potential contribution to Linux, we need to first find out whether or not the licenses are even compatible, so that code can be shared between the two projects.

    --
    The Future of Human Evolution: Autonomy
  10. I'd like to give it a try... by Anonymous Coward · · Score: 1, Interesting

    ...but first I'd like to know if it supports ext2 and if it can be booted with lilo?!

  11. Re:Open Source, only in US and Canda by russcox · · Score: 5, Interesting
    This is NOT true.

    We do IP address checks to make sure you're in a country that the U.S. allows us to export crypto to, and that is all.

  12. Re:I tried Plan 9 by 1010011010 · · Score: 3, Interesting


    There's occasionally talk on LKML of using 9P, the universal Plan9 protocol, in Linux.

    9P is the filing protocol, but *everything* in Plan9 is a file, so it's a universal protocol. It allows you to do things like nest devince namespaces, so you can have windowing systems inside windowing systems without any extra work.

    --
    Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
  13. Re:FSF take? by Elwood+P+Dowd · · Score: 2, Interesting

    Agreed. The changes are enough that most Free Software types will probably be comfortable. However, that last issue:

    "Contributors shall have unrestricted, nonexclusive, worldwide, perpetual, royalty-free rights, to use, reproduce, modify, display, perform, sublicense and distribute Your Modifications, and to grant third parties the right to do so, including without limitation as a part of or with the Licensed Software;"

    Definitely means that this isn't GPL compatible. Sure, a copyright owner can do whatever the hell they want with their stuff, so Reiser could start putting ReiserFS under this license & incorporate Plan 9 code, but Linus can't. Neither can Redhat, for any of their externally developed software.

    The place that this will probably cause the most chaffing is that Plan 9 folks won't be able to port GPLed Linux drivers. Then of course, the architectures are different enough that porting drivers could be impossible anyway.

    --

    There are no trails. There are no trees out here.
  14. Re:Viral or free? by dspeyer · · Score: 2, Interesting
    No, GNU and MS aren't the same here.

    As the grandparent stated, hat you create is not automatically a derived work of everything you've seen. If it were, Disney would own the entire creative output of humanity (who didn't watch their IP as a child?)

    What can be automatic is trade secrets. Here, there is precident (though I'm not sure how much) for presumption of automatic disclosure. Those who have seen MS code are forbidden to work on similar code elsewhere not because it would be a derived work but because it would reveal to the world some mystical MS essence.

    We're safe from all that here. Nothing that can be publicly downloaded from the web can be a trade secret.

  15. Plan 9 compatible with BSD ? by Anonymous Coward · · Score: 1, Interesting
    Don't the following terms from the Plan 9 license suggest parts of Plan 9 might taken and re-licensed under a BSd license ?

    "A. Distributor may choose to distribute the Program in any form under this Agreement or under its own license agreement, provided that:

    1. it complies with the terms and conditions of this Agreement;
    2. if the Program is distributed in source code or other tangible form, a copy of this Agreement or Distributor's own license agreement is included with each copy of the Program; and
    3. if distributed under Distributor's own license agreement, such license agreement:
    1. effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose;(ok the BSD license does that)
    2. effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits; and(ok BSD does that)
    3. states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party.(So Theo de Raadt can just note that he placed it under the BSD, not Bell Labs, and he's ok)

    B. Each Distributor must include the following in a conspicuous location in the Program:

    Copyright (C) 2003, Lucent Technologies Inc. and others. All Rights Reserved.

    C. In addition, each Contributor must identify itself as the originator of its Contribution, if any, and manifest its intent that the additions and/or changes be a Contribution, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution. Once consent is granted, it may not thereafter be revoked."

    Seems to me like Bell Labs wanted to let the source go, but didn't want anything coming back to bite them. So they merely are making sure any claims stop with the first person to copy it and re-license it under the BSD license, and don't waste their lawyer money.

    What's the big deal with Theo ?

  16. Re:How long until? by Rip!ey · · Score: 2, Interesting

    How long until SCO claim that SCO IP was stolen and put into plan9?

    They already have. The linked article is dates June 16 2003. Since many do not appear to read the articles ...

    "... We believe that UNIX System V provided the basic building blocks for all subsequent computer operating systems, and that they all tend to be derived from UNIX System V (and therefore are claimed as SCO's intellectual property)."

    This obviously included Microsofts operating systems as well. And despite Microsoft having paid for a licence recently, they do not appear to be ruling out going after the beast at a later date.

    "So is anybody clean? What about Apple and Microsoft?" I wondered. "Sun is clean," he saidâ"but he gave no answer in regards to Apple and Microsoft. "But I thought that Microsoft had signed a license agreement?" "No," Sontag said. Microsoft merely licensed an "applications interface layer."

  17. Re:Plan 9? by spitzak · · Score: 3, Interesting
    Far more important than the distributed processing is the "everything is a file" method of accessing all information outside of a process.

    This is a huge deal, it is a real object-oriented system interface. All these proponents of COM and Corba and .net and all that other wannabe stuff should pay attention: "object oriented" is meaningless unless the "methods" match between the objects so they can be substituted for each other. Plan9 does this (so did original Unix before they added ioctl and sockets). In Plan9 all objects have "read" and "write" methods (and a few others) and can be reused. Now some people will scoff and say that that is not the type of methods they want on their objects, but they fail to realize that if they build their methods atop these they will be able to reuse any of the base objects. The files also provide a usable method of copying an object from one point to another that respects the actual size of these objects and the fact that executable code typically does not work on any machine other than the one it was supposed to be on.