Slashdot Mirror


Groklaw Starts Unix/Linux History Project

An anonymous reader writes "Over on GrokLaw, PJ and others have decided to create a 'timeline' for Unix and Linux development. The plan is to recreate, as completely as possible, the history of these two operating systems '...from the perspective of tracing the code by copyright, patents, trade secret, and trademark. The idea is that the final timeline will be a publicly-available resource, released under a Creative Commons license, that will assist the community in defending against - or better yet in deterring - future lawsuits against GNU/Linux code.'"

13 of 71 comments (clear)

  1. Don't do it. by Quasar1999 · · Score: 4, Insightful

    Sco will find a way to use this history to further 'prove' that source code was acquired from commercial software at specific times from specific companies, using nothing more than the fact that some feature was added to linux on a specific date. This aids insane companies like SCO who want to find relationships and infringement where there really was none... go back far enough, and no one from the time/company/developer will be able to defend their IP...

    --

    ---
    Programming is like sex... Make one mistake and support it the rest of your life.
    1. Re:Don't do it. by Kalak · · Score: 3, Insightful

      While PJ is on the side that is generally against SCO and Linux, that is because she is on the side of finding the truth of the issues relating to SCO. The truth is against SCO because they are not looking at things with more than an eye for profit. If she (and the others at groklaw) were to find that there was a place for infringement in Linux, you can bet that she would be the first to e-mail a copy of it to LKML so that those that are interested in protecting Linux are able to insure it is clean, or becomes clean, and remains clean.

      Linux will not come through this because it's better at hiding things than SCO, but because it is better at opening things up to be revealed to all than SCO. Such a history only reveals more truth to Linux and its development, and can only help Linux.

      Image if they did find something. How long it would remain in the kernel? Everyone would switch to non-tainted kernels, and SCO would have no one left to sue.

      Revealing the truth can only help Linux

      --
      I am, and always will be, an idiot. Karma: Coma (mostly effected by .hack)
  2. the past might haunt us by thexdane · · Score: 4, Funny

    they will have to watch out because it will finally be revealed that SCO invented unix while a person called Al Gore worked for them and then everything will be lost

  3. The press by Message+Board · · Score: 3, Interesting

    I'm curious to whether the Linux derivitive work(s) that SCO released and distributed in its own products will come out more in the press. Considering that this will be backed up with creditable resources, it could provide valuable insight for the press into "our side" of things. Big corporations have lots of nice looking graphs and reports to make things look rosy, but Linux really does not.

  4. No... by debilo · · Score: 5, Insightful

    Fearing SCO is not really a reason not to do this.

    go back far enough, and no one from the time/company/developer will be able to defend their IP...

    I don't really understand this conclusion. Are you trying to say that documenting and publishing events of the past somehow aids criminals? If so, how?

  5. Hrm... by Niacin · · Score: 3, Interesting

    They better have valid sources for the timeline, or SCO will say something along the lines of "this is crap, we did it all!" and the courts would care less.

    And whats up with the lack of responses? People must be getting fed up with SCO crap.

    1. Re:Hrm... by Dukael_Mikakis · · Score: 3, Insightful

      I agree. It seems like it's going to be a damn hard project. But I guess it depends on how they want to approach it. If they want to document the major events (i.e. Linus had an idea) then it might not be so daunting, but then it might not be so interesting either. If they want to go into any depth, it seems like it'd be impossible because so many people have had their hands on Linux, and there are so many different versions and branches and everything.

      Sounds something like documenting the history of the English language. The "big picture" stuff might not be very interesting, but then it'd be impossible to document when every word was first used, and by whom.

      I guess, obviously, the logical plan is sketch out major events then flush out the details.

  6. UNIX Timeline by mmca · · Score: 3, Informative

    Isnt this pretty complete:

    http://www.levenez.com/unix/
    http://www.unix.org/what_is_unix/history_timeline. html

    Now just follow the the copyrights and patents.

    1. Re:UNIX Timeline by j-pimp · · Score: 4, Insightful

      Well I must be fucking new here cause I RTFA. Allow me to 'splain to you.

      Groklaw is run by a paralegal. This is a legal history. All those diagrams of Unix, networking etc, are from a geek point of view. groklaw wants to make a history that concerns itself with patents and trademarks being declared, licensed, expired etc.

      --
      --- Justin Dearing http://www.justaprogrammer.net/ We're just programmers.
    2. Re:UNIX Timeline by pigpogm · · Score: 4, Funny

      Yes, you must be new. Allow me to 'splain...

      If you RTFA, you don't get to post for at least a minute. Anything not posted in the first 45 seconds won't stand a chance of getting moderated, so it would be a waste of time.

      So i just wasted my time completely.

      Damn.

      --
      PigPog.
  7. History of UNIX by Anonymous Coward · · Score: 5, Funny

    Unix was a program gone bad. Born into poverty, its parents, the phone company, couldn't afford more than a roll of teletype paper a year, so Unix never had decent documentation and its source files had to go without any comments whatsoever. Year after year, Papa Bell would humiliate itself asking for rate increases so that it could feed its child. Still, unix had to go to school with only two and three letter command names because the phone company just couldn't afford any better. At school, the other operating systems with real command names, and even command completion, would taunt poor little Unix for not having any job or terminal management facilities or for having to use its file system for interprocess communication and locking.

    Then, bitter and emasculated by its poverty, the phone company began to drink. During lost weekends of drunken excess, it would brutally beat poor little Unix about the face and neck. Eventually, Unix ran away from home. Soon it was living on the streets of Berkeley. There, Unix got involved with a bad crowd. Its life became a degrading journey of drugs and debauchery. To keep itself alive, it sold cheap source licenses for itself to universities which used it for medical experiments. Being wantonly hacked by an endless stream of nameless, faceless undergraduates, both men and women, often by more than one at the same time, Unix fell into a hell-hole of depravity.

    And so it was that poor little Unix began to go insane. It retreated steadily into a dreamworld, the only place where it felt safe. It took heroin and dreamed of being a real operating system. It took LSD and dreamed of being a raspberry flavored three-toed yak. It liked that better. As Unix became increasingly attracted to LSD, it would spend weekends reading Hunter Thompson and taking cocktails of acid and speed while writing crazed poetry in which it found deep meaning but which no one else could understand.

    Eventually, Unix began walking down Telegraph Avenue talking to itself, saying "Panic: freeing free inode," over and over again. Sometimes it would accost perfect strangers and yell "Bus error (core dumped)!" or "UNEXPECTED INCONSISTENCY: RUN FSCK MANUALLY!" at them in a high pitched squeal like a chihuaua with amphetamine psychosis. Upstanding citizens pretended it was invisible. Mothers with children crossed to the other side of the street.

    Then one evening Unix watched television, an event which would change its life. There it discovered professional wrestling and knew that it had found its true calling. It began to take huge doses of corticosteroids to build itself up even bigger than the biggest of the programs which had beaten it up as a child. It ate three dozen pancakes and four dozen new features for breakfast each day. As the complications of the steroids grew worse, its internal organs grew to the point where Unix could no longer contain them. First the kernel grew, then the C library, then the number of daemons. Soon one of its window systems was requiring two megabytes of swap space for each open window. Unix began to bulge in strange, unflattering places. But Unix continued to take the drugs and its internal organs continued to grow. They grew out its ears and nostrils. They placed incredible stresses on Unix's brain until it finally liquefied under pressure. Soon Unix had the mass of Andre the Giant, the body of the Elephant Man, and the mind of a forgotten Jack Nicholson character.

    The worst strain was on Unix's mind. Unable to assimilate all the conflicting patchworks of features it had ingested, its personality began to fragment into millions of distinct, incompatible operating systems. People would cautiously say "good morning Unix. And who are we today?" and it would reply "Beastie" (BSD), or "Domain", or "I'm System III, but I'll be System V tomorrow." Psychiatrists labored for years to weld together the two major poles of Unix's personality, "Beasty Boy", an inner-city youth from Berkeley, and "Belle", a southern transvestite who wanted to be a woman. With each

    1. Re:History of UNIX by Anonymous Coward · · Score: 3, Informative

      http://www.wards.net/~bill/humor/geek/unix-history .shtml

      credits this text as:
      Posted to the unix-haters@ai.mit.edu mailing list by ian@ai.mit.edu (Ian D. Horswill) on 10/12/92

  8. Re:Licensing of mass disruption/destruction by n3k5 · · Score: 3, Informative
    You're missing a most essential point here. In the proprietary software world, every comapnay makes its own, proprietary licences. If you want to know the contents of one, you have to fight your way through the legalese, full length. On the open source side, however, most projects use one of only a couple of licences, all of which have very simple rights and restrictions attached to them. The legalese is just for the lawyer types, most users can get away just reading the very easily understandable summaries. Creative Commons is not a waste of time, it adresses issues that haven't been adressed before, in other licences. In fact, they do insanely useful things, for example they adress one issue you brought up: making the same license compatible with the legal system of many countries.

    Now supposing I decided as an admin on one of the machines I -obviously ADMIN - I decide to go with the "non commercial" license.
    Huh? WTF? You have to choose a licence when you release a work. Your administrative tasks are not something you release, they're not a work your users are copying ... I don't get it.
    --
    but what do i know, i'm just a model.