public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CD/DVD record
Date: Thu, 26 Aug 2004 11:41:22 +0200	[thread overview]
Message-ID: <20040826114122.79daaa16.skraw@ithnet.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1040825174749.3199M-100000@gatekeeper.tmr.com>

On Wed, 25 Aug 2004 17:54:25 -0400 (EDT)
Bill Davidsen <davidsen@tmr.com> wrote:

> On Wed, 25 Aug 2004, Stephan von Krawczynski wrote:
> >
> > Actually this is only FUD spread by Joerg. He is definitely not the only
> > man on this planet knowing how to program CD/DVD burning equipment.
> 
> Good, glad you have a supply of SCSI gurus who want to dedicate all their
> spare time to maintaining OS software. Joerg has been at this for years,
> and I think that while identifying technically competent people is
> possible, I doubt there's a big overlap with the set of people who have
> nothing better to do with their spare time. When I said "find" I certainly
> meant both qualifications.

Well, please read the docs for cdrecord again carefully. The story is not about
_free_, it is about _money_. Certain versions of cdrecord are licensed to
commercial customers for _money_. So please rethink your position.

> > Generally cdrecord has one big deficiency, which obviously was intended:
> > it does not allow medium skilled programmers from drive _vendors_ to add
> > support for their latest hardware easily. Everyone has to beg Joerg, which
> > obviously increased his ego dramatically over the years.
> > It would be a lot better to start off a new project where vendors (or
> > anybody with skill and will) can contribute more easily, i.e. something
> > that is truely_open_.
> 
> A nice idea, but in truth if a vendor wants support in cdrecord a tech ref
> and sample unit will almost certainly do it. I'd love to have support for
> HD_BURN in Linux, but Joerg can't seem to get the info needed. I doubt
> that people who won't release the info will trouble to write the driver.

Well, if I were owner of docs that are important for Joerg to make money and
had listened to him for the past 4 or 5 years and how he treated people (and
still does) it would be highly probable that I wouldn't be very cooperative,
too.
Please see the whole picture, not only what Joerg talks about.
Just take a clear look at his latest code changes and tell me if they look like
being done by an open-minded and friendly person to you.

Speaking from a potential commercial customers' point of view I decided against
using this software, not because of the money, but because of the
closed-everything-and-his-ears habit of the author. I don't see how this
project can survive its current author. Therefore I consider it an already dead
horse.

-- 
Regards,
Stephan

  reply	other threads:[~2004-08-26  9:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 13:25 CD/DVD record Richard B. Johnson
2004-08-19 12:33 ` Alan Cox
2004-08-19 14:41   ` Richard B. Johnson
2004-08-19 15:04     ` David Woodhouse
2004-08-19 13:37 ` Nigel Rantor
2004-08-19 14:46   ` Richard B. Johnson
2004-08-19 14:59     ` Nigel Rantor
2004-08-20  8:24   ` Helge Hafting
2004-08-20  8:46     ` Nigel Rantor
2004-08-23 22:07       ` Bill Davidsen
2004-08-25 11:51         ` Stephan von Krawczynski
2004-08-25 12:45           ` Henning P. Schmiedehausen
2004-08-25 21:54           ` Bill Davidsen
2004-08-26  9:41             ` Stephan von Krawczynski [this message]
2004-08-26 20:21               ` Bill Davidsen

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=20040826114122.79daaa16.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=davidsen@tmr.com \
    --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