The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wes.parish@paradise.net.nz (Wesley Parish)
Subject: [TUHS] SCO sues IBM?
Date: Tue, 11 Mar 2003 10:52:21 +1300	[thread overview]
Message-ID: <200303111052.21237.wes.parish@paradise.net.nz> (raw)

Well, the impression I got from IBM re: AIX and Linux's relationship, was that 
they were going to give AIX a Linux makeover so that they could maintain an 
apparently unified Un*xish shop - as far as AIX and Linux _are_ Un*ces, that 
is!

How that gets interpreted as importing Un*x trade secrets into Linux, I have 
no idea.

I also thought IBM was going to allow some of their mainframe high 
availability ideas to influence Linux - not through direct porting of the 
code - VM/ESA is apparently written in PL/I, and I doubt that most Linux 
programmers would touch that with a barge-pole.  And a waldo at a workplace 
on a planet on the other side of the galaxy.  Or universe.

I myself wanted to get some information on the internal structure - ie, the 
part that gets passed between the SFS client and the Reusable Kernel Server - 
of the VM/ESA Shared File System way back when, and was told in no uncertain 
terms, not to bother trying.

I don't see SCO has much chance of doing anything except causing a bit of 
unwelcome disruption and - I hope - getting bought out at bargain basement 
prices by IBM and getting the entire Un*x source tree BSDed or LGPLed to stop 
all this useless nonsense at the "source".  Or at the "sauce", to give it a 
rather appropriate spin.

Wesley Parish

On Tuesday 11 March 2003 12:45 pm, Greg 'groggy' Lehey wrote:
<snip>
>
> I am very sure that IBM has not put any UNIX code into Linux.  For one
> thing, it's not their style, and in fact they keep the AIX and Linux
> people very separate.  Last year I wrote a clone of AIX's JFS file
> system on Linux for IBM.  This is the old JFS, not the JFS they
> released under GPL.  I was not allowed to see the AIX source code, for
> exactly the reasons of the complaint.  The only information I had were
> the header files they distribute with the development system.
>
> The AIX code wouldn't have helped, anyway.  Linux is not UNIX, as
> anybody who's done kernel programming in both knows.  I had thought
> that this childish superstition about the holiness of source code
> would have been stamped out at the end of the last UNIX wars.
>
> Greg

-- 
Mau e ki, "He aha te mea nui?"
You ask, "What is the most important thing?"
Maku e ki, "He tangata, he tangata, he tangata."
I reply, "It is people, it is people, it is people."



             reply	other threads:[~2003-03-10 21:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 21:52 Wesley Parish [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-11  5:25 Dennis Ritchie
2003-03-11  6:01 ` Greg 'groggy' Lehey
2003-03-12  4:34 ` Jeffrey Sharp
2003-03-10  1:21 Greg 'groggy' Lehey
2003-03-10  2:33 ` David C. Jenner
2003-03-10  3:28   ` Peter Jeremy
2003-03-10 20:23     ` Jeffrey Sharp
2003-03-10  3:13 ` Michael Davidson
2003-03-10 20:21   ` Jeffrey Sharp
2003-03-10 21:15     ` Peter Jeremy
2003-03-10 21:54       ` David C. Jenner
2003-03-10 23:45       ` Greg 'groggy' Lehey
2003-03-11  0:22         ` Peter Jeremy
2003-03-11  1:14           ` Gregg C Levine
2003-03-11  1:51             ` Warren Toomey
2003-03-11  1:59               ` Greg 'groggy' Lehey
2003-03-11  3:51                 ` Warren Toomey
2003-03-11  4:11       ` Michael Davidson
2003-03-11  9:44         ` Sven Mascheck
2003-03-11 15:40           ` Gregg C Levine
2003-03-12  4:05             ` Jeffrey Sharp
2003-03-12  4:46       ` Jeffrey Sharp
2003-03-12  5:03         ` Greg 'groggy' Lehey
2003-03-12 20:31           ` Peter Jeremy
2003-03-12 20:33           ` Wm. G. McGrath
2003-03-11  3:51 ` Wm. G. McGrath

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200303111052.21237.wes.parish@paradise.net.nz \
    --to=wes.parish@paradise.net.nz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).