public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Patrick McFarland <pmcfarland@downeast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] Joerg Schilling flames Linux on his Blog
Date: Mon, 23 May 2005 14:17:16 +0100	[thread overview]
Message-ID: <87acmmf5er.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <200505201345.15584.pmcfarland@downeast.net> (Patrick McFarland's message of "20 May 2005 18:47:53 +0100")

On 20 May 2005, Patrick McFarland suggested tentatively:
> As everyone knows, Joerg Schilling has a blog, and he often pushes his 
> pro-Solaris agenda, and flames the LKML about how Linux breaks cdrecord 
> (instead of just admitting cdrecord is broken) or how much more awesome 
> Solaris is compared to Linux.
> 
> Well, he just fired yet another salvo at the Linux community: 
> http://schily.blogspot.com/2005/04/value-marketing-and-freedom.html

His research sucks.

: Later, the LGPL has been created and parts of the GCC (libgcc) has
: been put under LGPL.

Wrong. It is trivial to check gcc/libgcc*c and observe that libgcc is
*not* LGPLed, but licensed under the GPL plus an exception permitting
unrestricted linkage to proprietary software. (Related exceptions are
used for the libstdc++ headers and the Ada runtime.)

Just before that, he said:

: This acceptance has not been present from the beginning. In the
: beginning, the whole GCC has been published under the GPL and thus could
: not be used to compile software that itself has not been published under
: the GPL. For this reason, there has been an excited discussion about the
: usability of GCC.

Note that in Joerg's worldview, a mistake equals conspiracy. This is a
classic kook's mindview. Jeff's right: the best thing we can do is to
just ignore him.

-- 
`Once again, I must remark on the far-reaching extent of my
 ladylike nature.' --- Rosie Taylor

  parent reply	other threads:[~2005-05-23 13:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-20 17:45 [OT] Joerg Schilling flames Linux on his Blog Patrick McFarland
2005-05-20 17:02 ` jmerkey
2005-05-20 18:24 ` Markus Plail
2005-05-20 18:34 ` Matthias-Christian Ott
2005-05-20 18:41   ` Lee Revell
2005-05-20 23:20 ` Brian O'Mahoney
2005-05-21  7:38   ` Adrian Bunk
2005-05-21 11:25     ` Bernd Petrovitsch
2005-05-21 11:33       ` Måns Rullgård
2005-05-22 18:24         ` Bernd Petrovitsch
2005-05-21 11:41       ` André Tomt
2005-05-21 23:24         ` Adrian Bunk
2005-05-22  0:27           ` Andre Tomt
2005-05-22 14:17             ` Matthias Andree
2005-05-21 16:39     ` Brian O'Mahoney
2005-05-21 23:59       ` Adrian Bunk
2005-05-22  1:22 ` Andrew Haninger
2005-05-22  4:23   ` [OT] Joerg Schilling flames Linux on his Blog/cdrecord replacement Brian O'Mahoney
2005-05-22 14:36     ` Matthias Andree
2005-05-22 17:42       ` Matthias Urlichs
2005-05-22  4:50   ` [OT] Joerg Schilling flames Linux on his Blog Patrick McFarland
2005-05-22 14:39     ` Matthias Andree
2005-05-22 20:40     ` Bernhard Rosenkraenzer
2005-05-22 15:54   ` Alistair John Strachan
2005-05-23 13:17 ` Nix [this message]
2005-05-23 14:35   ` Brian O'Mahoney
2005-05-23 14:58     ` Nix
  -- strict thread matches above, loose matches on Subject: below --
2005-05-25 13:15 OT] " Joerg Schilling
2005-05-25 23:12 ` Kyle Moffett
2005-05-26 10:15   ` Joerg Schilling
2005-05-26 12:47     ` [OT] " Alexander E. Patrakov
2005-05-27 10:31       ` Joerg Schilling
     [not found] <4847F-8q-23@gated-at.bofh.it>
2005-05-25 22:46 ` OT] " Joerg Schilling
2005-05-25 23:31   ` Kyle Moffett
2005-05-26  3:45     ` [OT] " Alexander E. Patrakov
2005-05-26  5:06       ` Giuseppe Bilotta
     [not found]       ` <Pine.LNX.4.58.0505261335440.2939@be1.lrz>
2005-05-26 12:33         ` Alexander E. Patrakov
     [not found]           ` <Pine.LNX.4.58.0505261651220.3407@be1.lrz>
2005-05-27 10:44             ` Joerg Schilling

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=87acmmf5er.fsf@amaterasu.srvr.nix \
    --to=nix@esperi.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmcfarland@downeast.net \
    /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