From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] My response to SCO vs. Linux
Date: Fri, 13 Jun 2003 08:46:27 +0930 [thread overview]
Message-ID: <20030612231627.GH1015@wantadilla.lemis.com> (raw)
In-Reply-To: <Law14-F30jwGXSXCWV8000236a2@hotmail.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.
Greg
--
Finger grog at lemis.com for PGP public key
See complete headers for address and phone numbers
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20030613/91df20d0/attachment.sig>
next prev parent reply other threads:[~2003-06-12 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 11:31 zmkm zmkm
2003-06-12 20:21 ` Andy Newman
2003-06-12 23:16 ` Greg 'groggy' Lehey [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-13 4:55 Carl Lowenstein
2003-06-19 11:00 ` Peter Jeremy
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=20030612231627.GH1015@wantadilla.lemis.com \
--to=grog@lemis.com \
/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).