Plan9 is now Officially Open Source 399
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."
"The hands that help are better far than the lips that pray." -- Robert G. Ingersoll
How long until? (Score:5, Funny)
Re:How long until? (Score:5, Interesting)
Just a thought...
-t
Of Course (Score:5, Interesting)
John Fogerty sued for sounding like John Fogerty! [cmt.com]
Fortunately, he won that case, but who knows how a similar case in the computer industry would turn out?
Winners and Losers (Score:5, Funny)
Fortunately, he won that case, ...
Yeah, but he also lost!
SteveM
Re:How long until? (Score:3, Informative)
This does not mean that he can use all the material he produced at his former employer but it does mean that he can use his intellect how he sees fit. This would include finding solutions to problems that are part of his normal work. Now the big question is how much such "snippets of code" are normal work routines or real intellectual property of his former employer.
I would assume that, for programmers, t
Re:How long until? (Score:2)
LOLOLOLOL *wiping tears from eyes* (Score:4, Funny)
Beowulf clusters of those! SCO claims infringement! Hot grits down Natalie Portman's pants!
Re:How long until? (Score:5, Funny)
That's impossible. Plan 9 is from outer space.
Re:How long until? (Score:2)
No, there are some straight lines that should be left untouched.
Movie (Score:2, Funny)
Re:Movie (Score:5, Funny)
Cult? (Score:3, Funny)
Usenix Bof? Sounds like what happens when a bunch of greasy, miserable nerds decide to play doctor in the server room.
More information (Score:5, Informative)
Latest release notes [bell-labs.com]
Download the source [bell-labs.com] (Warning: requires identification--privacy advocates maybe be excluded here)
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.
Re:More information (Score:2, Informative)
License Compatability between Linux & Plan 9? (Score:4, Interesting)
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.
You are as disingenuous as SCO (Score:4, Insightful)
Please.
First, which part of "this will contribute to Linux" didn't you understand? Linux has absolutely nothing to do with the FreeBSD license, so spreading your divisive nonsense in this thread is woefully off-topic.
Second, the FreeBSD license is perfectly compatible with the GPL. It is also compatible with Microsoft's proprietary license, not to mention anyone elses. The fact that the GPL isn't compatible with FreeBSD (meaning you can't take GPLed code and incorporate it into FreeBSD-licensed code), and the fact that Microsoft's proprietary license is likewise incompatible, is entirely irrelevant.
Indeed, that one-way compatability was a deliberate decision made by the FreeBSD folks...who valued the developer's freedom to incorporate their hard work into proprietary products over the protection of the freedom of future developers and users. Which is a perfectly legitimate stance to take, though it just so happens to be in disagreement with the decision by the GPL folks to protect their users and derivative developers freedoms above even their own.
It is extraordinarilly disingenuous to criticize one free licenses philosophy and imply it to somehow be improper, when the very same license has led to FreeBSD code being included in products which protect neither the developers, nor the users freedom, such as Microsoft's usage of the FreeBSD network stack. Before lambasting the thousands of volunteers who have contributed millions of man hours for FREE, to enhance your FREEDOM, merely because you disagree with the aspects of freedom they choose to emphesize over the ones you would emphesize (if any, which I find questionable in this particular troll), perhaps you would like to address the use of FREE code in products that strip all said FREEDOMs away? Until you justify lambasting the 1-way compatability between two free licenses while ignorning the same 1-way compatability between FreeBSD and virtually every proprietary license, your entire argument devolves to hypocritical grandstanding, misinformation, and spin.
The GPL is free. FreeBSD is free. In different ways, with different protections, different emphesises on different aspects of freedom, and with different consiquences. Most of us who use FreeBSD are perfectly comfortable with this, and understand the differences that are part of the diversity of our community. Most of us who use GNU/Linux are likewise understanding and appreciative of both schools of thought, and can recognize the advantages and limitations of both.
It is only the few zealots on either side, and much more commonly divisive trolls like yourself, for whome this concept poses such difficulty.
Re:More information (Score:2)
Most Unix geeks already have a large enough breadth of hair, although freshening it once in a while would be a good idea, as would the use of Head and Shoulders.
Thanks, folks, I'll be here all week.
Squeak? (Score:2)
Every new Open Source OS is a benefit. Just consider the current SCO imbroglio. Well, for this one the *BSDs provide a storm shelter for the worst case scenario. They aren't my choice of an OS, but it's comforting to know that they're there.
Likewise, the Hurd is coming along. It will provide an additional measure of security, as it derives from differe
Re:More information (Score:3, Insightful)
And you managed to fit in the word "paradigm", too.
Plan 9? (Score:4, Funny)
Re:Plan 9? (Score:4, Informative)
Re:Plan 9? (Score:3, Insightful)
the Plan 9 approach seems useful for stuff that needs extreme abstraction of resources, but exactly what needs that? At that level you need to have access to the guts.
Re:Plan 9? (Score:4, Interesting)
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.
Basically, Plan9 is Unix done right. (Score:4, Informative)
Will it take over the world and replace Unix? No but it has a lot of very good ideas which can help direct future Linux and Unix development.
Re:Plan 9? (Score:5, Informative)
Instead of everything being a file, everything's a file system. Instead of processes communicating through pipes, everything communicates through plumbing (like a cross between pipes and an email system).
It's tiny, coherent, and elegant. I really hope we see more of it.
-Billy
Re:Plan 9? (Score:2)
Oh wait, you were asking about the OS?
Plan9 is really cool (Score:4, Informative)
DAMMIT (Score:5, Funny)
Runs in VMWARE (Score:2, Informative)
excellent (Score:5, Insightful)
Open sourcing OS code has proven to be a good way to keep ailing systems relevant in the current marketplace. It kept BeOS and VMS from dying in obscurity, and even helped BSD limp along for a few more years.
I predict nothing but good things from GNU/Plan9. Hopefully Debian will introduce a Plan9 distro, to go with their Darwin, HURD, and Linux distrii. I still have a few spare boxen lying around that I could use this on.
Re:excellent (Score:2)
What are you talking about? BeOS and VMS were never open sourced.
Re:excellent (Score:2)
Re:excellent (Score:2)
Re:excellent (Score:2)
You know, that's one of the problems I have with the Linux/Open Source movement. Everything is just fodder for rape and pillage. Failed/abondoned OSes/Games/whatever are just resources to be picked through and glommed onto Linux, like the junked robots from A.I.
Re:excellent (Score:4, Insightful)
I'd call it learning from previous experience and survival of good ideas. One of the great things about open-source is that great ideas don't have to die with the project they originated in.
I tried Plan 9 (Score:2)
Re:I tried Plan 9 (Score:2)
Re:I tried Plan 9 (Score:4, 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.
Re:I tried Plan 9 (Score:4, Informative)
They already have. Have a look at these:
9wm [plig.org] - a window manger that acts like 8 1/2 from Plan 9
Wily [yorku.ca] - a clone of Plan 9s programmers editor, Acme (v cool)
There's also WindowLab [freshmeat.net], another window manager which uses the same window resizing system as Plan 9.
I'm sure there's more that I don't know of...
Re:I tried Plan 9 (Score:2)
First TRON now plan 9. (Score:4, Funny)
Re:First TRON now plan 9. (Score:2)
Note to self: do not use WOPR operating system for anything. Especially games.
The only problem w/ the Plan9 OS... (Score:3, Funny)
Eventually, a bad double - in the form of the CEO's dentist - was brought in to replace Ritchie - the result being that the first half of the Plan9 OS is decent, but the last half is just terrible.
Oh, and it turns out that the CEO is a cross-dressing lunatic, whose obsession with C-grade OSes (like BeOS, NetBSD, NeXT, Apple OS9, OS2 Warp, etc) eventually led to him living out the rest of his life if relative obscurity and poverty. Sad, really... but, it might make a decent movie... nah.
Re:The only problem w/ the Plan9 OS... (Score:2)
Re:The only problem w/ the Plan9 OS... (Score:2)
Ummmm, looks like drgroove's joke went over your head...
(Nice one, drgroove!!!)
Re:The only problem w/ the Plan9 OS... (Score:2)
RMS oked as well? (Score:2, Insightful)
Although the intent does not conflict with the GPL I think the requirment of commercial distributors to defend contributors against certain suits might be a show stopper beacause of how it's written. But IANAL; can someone comment on this?
Re:RMS oked as well? (Score:2)
Re:RMS oked as well? (Score:2)
Since if meets the OSD, it surely also meets the FSD (they're virtually identical) and the FSF will probably acknowledge it soon.
GPL code clearly can not be included into plan9 (except by dual-license, of course)
Plan9 code (I think) can be included into a GPLed word (such as linux). The relevant provision is "Distributor may
this license is (Score:2, Informative)
in summary..
it is not open source, it is a TRAP
excellent news (Score:4, Interesting)
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 !
Re:excellent news (Score:2)
Micro vs macro kernel wars were held in the early nineties. Nobody won, macrokernels came ahead slightly.
Plan 9 has not been tested for scalability.
Re:excellent news (Score:3, Interesting)
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 tec
Re:excellent news (Score:3, Interesting)
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
Re:excellent news (Score:2)
First of all, there's no need to evolve unless there are dramatic changes in your environment. While hardware has become many many times bigger and faster over the three decades of Unix, computer architecture issues (for example, memory hierarchy, CPU scheduling, I/O) have remained most
RIT... (Score:3, Informative)
Props to my profs Bischof and Schreiner.
Long term, does this mean anything? (Score:5, 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.
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...
Re:Long term, does this mean anything? (Score:3, Funny)
It's good for shut up the people who yell "OMG stop copying and start innovating dammit!!!" all the time.
Answering (Score:2, Insightful)
Problem 3: What does Plan 9 offer that would make me, or you, want to spend time installing and learning it?
These seem to be the biggest "issues" you propose, which you fully address in your other problem: Problem 2: It is a research tool, and may never be more than that.
Many people seem to forget that there are many many many OSs out there that aren't flavors of *nix or Windows which are used for research purposes. There are quite a few which would make great multi-purpo
Re:Long term, does this mean anything? (Score:5, Interesting)
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.
Re:Long term, does this mean anything? (Score:5, Interesting)
it's good for research. an antidote to Systems Software Research is Irrelevant [uiuc.edu].
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"...
Re:Long term, does this mean anything? (Score:3, Insightful)
This is exactly the reason why projects like Plan9 are a good thing. If everyone concentrated on developing current technologies, the rate of innovation would drop dramatically. Will plan9 ever become a widely used, vastly supported operating system? Probably not, but the beauty of open source is that the advancements made by resear
FSF take? (Score:3, Informative)
i wonder if this new revised license has fixed any of those problems?
here is the statement from RMS.
When I saw the announcement that the Plan 9 software had been released as "open source", I wondered whether it might be free software as well. After studying the license, my conclusion was that it is not free; the license contains several restrictions that are totally unacceptable for the Free Software Movement. (See http://www.gnu.org/philosophy/free-sw.html.) [slashdot.org]
I am not a supporter of the Open Source Movement, but I was glad when one of their leaders told me they don't consider the license acceptable either. When the developers of Plan 9 describe it as "open source", they are altering the meaning of that term and thus spreading confusion. (The term "open source" is widely misunderstood; see http://www.gnu.org/gnu/philosophy/free-software-fo r-freedom.html [slashdot.org]
Here is a list of the problems that I found in the Plan 9 license. Some provisions restrict the Plan 9 software so that it is clearly non-free; others are just extremely obnoxious.
First, here are the provisions that make the software non-free.
You agree to provide the Original Contributor, at its request, with a copy of the complete Source Code version, Object Code version and related documentation for Modifications created or contributed to by You if used for any purpose.
This prohibits modifications for private use, denying the users a basic right.
and may, at Your option, include a reasonable charge for the cost of any media.
This seems to limit the price that may be charged for an initial distribution, prohibiting selling copies for a profit.
Distribution of Licensed Software to third parties pursuant to this grant shall be subject to the same terms and conditions as set forth in this Agreement,
This seems to say that when you redistribute you must insist on a contract with the recipients, just as Lucent demands when you download it.
1. The licenses and rights granted under this Agreement shall terminate automatically if (i) You fail to comply with all of the terms and conditions herein; or (ii) You initiate or participate in any intellectual property action against Original Contributor and/or another Contributor.
This seemed reasonable to me at first glance, but later I realized that it goes too far. A retaliation clause like this would be legitimate if it were limited to patents, but this one is not. It would mean that if Lucent or some other contributor violates the license of your GPL-covered free software package, and you try to enforce that license, you would lose the right to use the Plan 9 code.
You agree that, if you export or re-export the Licensed Software or any modifications to it, You are responsible for compliance with the United States Export Administration Regulations and hereby indemnify the Original Contributor and all other Contributors for any liability incurred as a result.
It is unacceptable for a license to require compliance with US export control regulations. Laws being what they are, these regulations apply in certain situations regardless of whether they are mentioned in a license; however, requiring them as a license condition can extend their reach to people and activities outside the US government's jurisdiction, and that is definitely wro
Re:FSF take? (Score:5, Insightful)
It seems that this rewrite was an attempt to address Richard's concerns. That said I think some of these issues may still be valid, but IANAL.
RMS != FSF (Score:2, Insightful)
RMS has on many occassions been a complete idiot and anyone who would have looked into the new license or even the freeking headline, would have seen that the issue of it being truly open is in fact true.
OpenSource != FreeSoftware, but OpenSource does bring more freedom, odd isn't it?
GNU is old school ... OSI is new school ... lets get together and change our collective phiolosophies.
Re:FSF take? (Score:3, Informative)
This has been changed:
You agree to provide the Original Contributor, at its request, with a copy of the complete Source Code version, Object Code version and related documentation for Modifications created or contributed to by You if distributed in any form, e.g., binary or
Re:FSF take? (Score:3, Interesting)
"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 whateve
Does this still make Richard Stallman cry? (Score:4, Interesting)
I think it'd be really great if Plan9 were released under a more "free" license.
Re:Does this still make Richard Stallman cry? (Score:2)
Re:Does this still make Richard Stallman cry? (Score:2, Informative)
It denies liability.
It allows you to modify the liscence if you're new liscence meets the requirements.
It makes you grant the rights to any patanted tech you incluede
It lets you redistribute.
The catches I see are
1) in a "conspicous place" in your program you must add a copyright Lucent and others tag
2) if you distribute it commercially you must protect the contributers from damages against any claims you make (The way I understood it is if you s
Re:Does this still make Richard Stallman cry? (Score:2)
From reading it, it appears to be Debian Free Software Guidelines compliant also, or at least that's my interpretation. I'm pretty sure that the old license required you to either assign copyright of your work to Lucent, or send them changes (or both), but it's been years since I read the original Plan9 license.
Powered by Plan 9? (Score:3, Interesting)
Introduction to Plan 9 (Score:5, Informative)
Plan 9 from Bell Labs (Score:4, Funny)
These news are funny when Slashdot's poll is "Worst Sci-Fi Movie Ever [slashdot.org]".
ESR has some info on Plan9 [catb.org] OS, wich include this footnote:
Plan 9 Wiki (Score:4, Informative)
If you found the Plan-9 FAQ but saw the URL to the Plan-9 wiki was broken, try http://plan9.bell-labs.com/wiki/plan9/plan_9_wiki
Main Plan9 differences versus UNIX (Score:2, Funny)
everything in UNIX is modelled as a "file", whereas in Plan9 everything is modelled after a "burrito"
UNIX makes extensive use of the commandline and pipe metaphor, while Plan9 has a chaw spitbucket metaphor.
UNIX programmers are very wealthy and considered to be generally cool by all, whereas Plan9 programmers generally only are popular with other Plan9 programmers. This leads to inbreeding and other nasty stuff which is why AT&T was forced to put a stop to it.
but is it Free Software ? (Score:2)
Personally, I think it's great that software is Open Source by OSI's definition, but 9 times of 10 I prefer Free Software [gnu.org] over Open Source.
License is questioned by Theo de Raadt (Score:2, Informative)
Re:Umm, (Score:3, Informative)
Re:Umm, (Score:4, Informative)
Our web server and FTP server serve the same files. /hidden is the exception to the rule, meaning that you can't list that directory using the FTP server (or the web server). We use it for things we don't want people stumbling upon. The license files were kept there when we were doing the initial OSI approval, and we just haven't moved them yet.
Re:Screenshots (Score:5, Informative)
Plan 9 is designed around the basic principle that all resources appear as files in a hierarchical file system (namespace) which is unique to each process. These resources are accessed via a network-level protocol called 9P which hides the exact location of services from the user. All servers provide their services as an exported hierarchy of files.
Features
The dump file system makes a daily "snapshot" of the filestore available to users
Unicode character set support throughout the system
Advanced kernel synchronization facilities for parallel processing
ANSI/POSIX environment emulator (APE)
Plumbing, a language driven way for applications to communicate
Acme - an editor, shell and window system for programmers
Sam - a screen editor with structural regular expressions
Support for MIME mail messages and IMAP4
Security - there is no super-user or root, and passwords are never sent over the network
Hierarchical "File" System for all resources (Score:2, Interesting)
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!
Re:Screenshots (Score:5, Funny)
must.. have.. the bunny OS!!
Re:Screenshots (Score:4, Funny)
Indeed, untill I had seen a screenshot or two, I had no idea how to write in C, now I'm rewriting Linux from a monolithic kernel to a micro kernel, thanks to the power of screenshots!
Re:Screenshots (Score:2, Funny)
Already been done (Score:2)
Re:Screenshots (Score:2)
Re:Screenshots (Score:2)
Re:Screenshots (Score:3, Informative)
Yeah, but now it's been posted to slashdot, loads of people are bound to rush out and code/port bells, whistles, flashing lights, and all sorts of stuff to make it look 1337.
On a more serious note, it's a reinvention of unix with the benefit of hindsight by the original inventors AFAIK. Read the specs - it has loads of wacky and inventive features. It runs on a cluster of PCs instead of a single processor, for example.
Re:Bela Lugosi and bad lighting (Score:2)
Re:Viral or free? (Score:5, Informative)
The reasons aren't obvious. I've seen this myth before, notably from Microsoft employees. The idea that you can be "infected" by simply looking at GPLd code is nonsense. The GPL explicitly covers only derived works of the code. If you looked at a GPLd algorithm and reimplemented it, somebody would have a hell of a time arguing in court that it was "derived". This is doubly the case for the vast majority of GPLd code, which is written by people who don't have huge piles of cash and who probably have a disdain for the legal system as well.
The idea that some random geek, or even a big company, is going to sue you on a legal platform as wobbly as "judge, he looked at it, so the rest of his work is clearly based on ours" is somewhere slightly above absolute zero and in any case applies just as equally to proprietary code, as the case of SCO shows.
Ironically, proprietary code is generally far more "infectious". I work on Wine - if I were to have seen the Windows code, I would be immediately banned from working on it, indeed, probably I'd be banned from working on most GPLd code. The EULA for Windows is extremely vague about such things, and Microsoft have armies of lawyers and it's quite feasable for them to sue me or others on a virtually non-existant legal basis. The reverse is not true.
I see that this post has been marked as a troll. I'm not sure it was, but this FUD should not be propogated any further regardless.
Re:Viral or free? (Score:3, Insightful)
The reasons aren't obvious. I've seen this myth before, notably from Microsoft employees. The idea that you can be "infected" by simply looking at GPLd code is nonsense.
Indeed you are correct. Imagine it like this. I write books for a living. I read a detective novel. Therefore I am banned from writing a detective novel. .. Erm, I don't think so.
Ironically, proprietary code is generally far more "infectious". I work on Wine - if I were to have seen the Windows code, I would be immediately banned fr
Re:Viral or free? (Score:2)
Right. Unfortunately distinctions like legality or illegality have little meaning when the mismatch is as great as a corporation vs the individual. People simply can't take the risk of a legally groundless but nonetheless devastating lawsuit.
Re:Viral or free? (Score:2)
Really?? well I have a few people to inform of this
I've been wanting to tell that consultant here at work wher to shove hos Ferarri for a long time... and he only USES and WRITES GPL code, and for some silly reason we pay him....
Thanks for letting me know that you cant make a living off of your work if you use the GPL!
I knew the lawyer team was stupid telling me they can sell GPL based programs.....
Re:Viral or free? (Score:3, Interesting)
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 bec
Do you read books? (Score:3, Offtopic)
You don't want to accidently read a book for obvious reasons.
Re:Viral or free? (Score:4, Informative)
I worked on this license. It is NOT viral.
It's basically the IBM license but changed not to be viral. Contributions must be covered by the same license, but that only applies if you declare your changes to be a Contribution.
If you want to take the code and go work on a closed project, no problem.
GPL is not viral! (Score:3, Informative)
Re:Open Source, only in US and Canda (Score:5, Interesting)
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.
Theo doesn't think GPL is free either (Score:3, Funny)