From: peterjeremy@optushome.com.au (Peter Jeremy)
Subject: [TUHS] My response to SCO vs. Linux
Date: Thu, 19 Jun 2003 21:00:54 +1000 [thread overview]
Message-ID: <20030619110053.GC9069@cirb503493.alcatel.com.au> (raw)
In-Reply-To: <200306130455.h5D4tHa15069@opihi.ucsd.edu>
On Thu, Jun 12, 2003 at 09:55:17PM -0700, Carl Lowenstein wrote:
>> From: "Greg 'groggy' Lehey" <grog at lemis.com>
>> On Thursday, 12 June 2003 at 11:31:52 +0000, zmkm zmkm wrote:
>> > Good old dear BSD , where is it ?? still fighting a niche turf , why
>> > it didn?t burst in the open ?
>>
>> Glad you asked. It was the victim of a law suit ten years ago. Don't
>> underestimate what the current legal challenges can do to Linux.
>In case you are referring to the BSD vs. AT&T suit, BSD won.
But BSD basically stagnated during the suit - which took 2-3 years.
No-one wanted to have anything to do with BSD whilst the suit was
on and it took a while to recover. Linux was unaffected and basically
gained 3-4 years headstart.
What Greg is suggesting is that if something equivalent comes along
for Linux (and I don't believe the SCO case is it), it will put a
really serious dent in its growth. Even if Linux won, the after-effect
will last for years.
Peter
next prev parent reply other threads:[~2003-06-19 11:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 4:55 Carl Lowenstein
2003-06-19 11:00 ` Peter Jeremy [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-12 11:31 zmkm zmkm
2003-06-12 20:21 ` Andy Newman
2003-06-12 23:16 ` Greg 'groggy' Lehey
2003-06-10 21:01 Michael Sokolov
2003-06-11 6:03 ` Jeroen Ruigrok/asmodai
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=20030619110053.GC9069@cirb503493.alcatel.com.au \
--to=peterjeremy@optushome.com.au \
/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).