public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Haninger <ahaning@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [OT] Joerg Schilling flames Linux on his Blog
Date: Sat, 21 May 2005 21:22:13 -0400	[thread overview]
Message-ID: <105c793f050521182269294d64@mail.gmail.com> (raw)
In-Reply-To: <200505201345.15584.pmcfarland@downeast.net>

> ... flames the LKML about how Linux breaks cdrecord
> (instead of just admitting cdrecord is broken)

I've always used cdr-tools on Linux and Windows since it is the
only/best tool for mastering CDs. It takes the installation of Joerg's
library, but after that, it's worked wonderfully. This is even the
tool that is suggested by the HOWTOs that newbies are told to read. It
has always appeared to me that it was the only/best tool.

If it's broken, then surely there's an unbroken drop-in replacement
program that should be used. And surely it works much better than
cdr-tools and is easier to use. However, after a few seconds of Google
searches, I was unable to find it.

So what is the new tool that is suggested to be used? I'd rather not
be using broken software. Thanks.

(This is really only a half-sarcastic reply. I really would like to
know if there's a better tool. However, I'm also trying to point out
that Joerg's software seems to be all that can be used at the moment
and so it's hard for me as a humble end-user to really care if his
software is broken since it works.)

  parent reply	other threads:[~2005-05-22  1:22 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 [this message]
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
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=105c793f050521182269294d64@mail.gmail.com \
    --to=ahaning@gmail.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