From: Matthias Andree <matthias.andree@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [OT] Joerg Schilling flames Linux on his Blog/cdrecord replacement
Date: Sun, 22 May 2005 16:36:12 +0200 [thread overview]
Message-ID: <20050522143612.GC13232@merlin.emma.line.org> (raw)
In-Reply-To: <42900929.1000408@khandalf.com>
On Sun, 22 May 2005, Brian O'Mahoney wrote:
> 1--
> SUN uses RPM internally, but continues to insist its Solaris
Can this please move to a Sun vs Linux advocacy group or list?
While Solaris' pkg* is certainly inferior to aptitude/dpkg, what the
heck has this got to do with the Linux kernel?
...
> 2--
> There was little wrong with cdrecord until DVDs came out and
> H Schilling decided to take DVD PRO private and became petty
> about his build system, smake, and others extending a fork
> of cdrecord to support DVDs; which was done by both SuSE and
> Debian -- but with weird add in Copyright, and you can't change
> this, and "Inofficial Version" junk from Schilling.
Check GPL clause 2 a - it was Schilling's right to insist that the
modified versions displayed those notices. If we make a fuss about
netfilter GPL compliance, we must grant that application programmers
make the same fuss about GPL compliance if distributors hack the
versions with inofficial patches.
And there has been a time when I've been using the "vanilla" versions
because the SUSE versions didn't work for me, for reasons I wouldn't
investigate, so I have nothing to complain about. ProDVD being
commercial has fostered alternative free DVD writing software that works
with Linux, so just use it and move on. Pragmatism is sometimes the
option of less resistance. :)
It is true Schilling's unrelated rants (like making GNU make sleep for
15 seconds or such) are tiresome and often fought in places where they
are inappropriate, but his complaints about ide-scsi not working
properly and the Kernel inventing SG_IO for ide-cd and the command
filtering behind it and all that fuss were fundamentally right, if a bit
exaggerated in volume. Let's see what becomes of ide-scsi and all that
as libata takes over parallel ATA devices in the future %-)
--
Matthias Andree
next prev parent reply other threads:[~2005-05-22 14:36 UTC|newest]
Thread overview: 27+ 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 [this message]
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
2005-05-23 14:35 ` Brian O'Mahoney
2005-05-23 14:58 ` Nix
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=20050522143612.GC13232@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®