From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: cdrtools incomplete?
Date: Tue, 8 May 2007 19:04:21 -0500 [thread overview]
Message-ID: <200705081904.26103.bss03@volumehost.net> (raw)
In-Reply-To: <2267552.IBWh4gRImt@kn.gn.rtr.message-center.info>
[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]
On Tuesday 08 May 2007, Alexander Skwar <listen@alexander.skwar.name> wrote
about '[gentoo-user] Re: cdrtools incomplete?':
> Leonhard Gruener <gentoo@lgruener.de> wrote:
> > Am Montag, 7. Mai 2007 schrieb Kevin O'Gorman:
> >> On 5/6/07, Philip Webb <purslow@sympatico.ca> wrote:
> >> > 070506 Kevin O'Gorman wrote:
> >> > > I'm trying to burn a CD for the first time in a long while.
> >> > > It's not going well. I've got cdrtools-2.01.01-alpha10
> >> > > installed. The description says it includes cdrecord, but I
> >> > > cannot find it.
> >
> > So install cdrkit.
>
> The "real" cdrecord
> is from cdrtools, though.
I'm pretty sure the one in cdrkit is real. Either that or I'm only
imagining that I burned and used my last rescue CD. *boggle*
:)
Just to be clear, cdrkit is a fork off of an older version of cdrtools that
was made because Debian doesn't believe cdrtools to be distributable by
anyone other than the copyright holder since parts are licensed under the
GPL and parts are under the (GPL-incompatible) CDDL. The issue is further
since the work isn't from an single author (contributions licensed under
the GPL from others have been integrated) AND at least one party involved
believes the GPL and CDDL to be compatible.
That doesn't make cdrkit less real, but it does mean that you'll probably
have fewer issues using cdrtools. (I use cdrkit and have never had any
problems with it; YMMV.)
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss03@volumehost.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.org/ \_/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-05-09 0:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 22:47 [gentoo-user] cdrtools incomplete? Kevin O'Gorman
2007-05-07 1:07 ` Philip Webb
2007-05-07 1:18 ` Kevin O'Gorman
2007-05-07 5:02 ` Leonhard Gruener
2007-05-07 5:59 ` Dirk Heinrichs
2007-05-08 13:41 ` [gentoo-user] " Alexander Skwar
2007-05-08 18:42 ` [gentoo-user] Problems starting X Johannes Skov Frandsen
2007-05-08 18:59 ` Francisco Rivas
2007-05-08 19:03 ` Francisco Rivas
2007-05-09 9:22 ` Johannes Skov Frandsen
2007-05-09 12:41 ` Francisco Rivas
2007-05-10 8:45 ` Johannes Skov Frandsen
2007-05-10 11:07 ` Aleksandar L. Dimitrov
2007-05-10 10:24 ` Johannes Skov Frandsen
2007-05-10 10:45 ` Aleksandar L. Dimitrov
2007-05-10 13:35 ` Francisco Rivas
2007-05-11 21:24 ` Johannes Skov Frandsen
2007-05-11 22:42 ` JD
2007-05-12 5:41 ` Francisco Rivas
2007-05-12 12:31 ` Johannes Skov Frandsen
2007-05-12 15:34 ` Francisco Rivas
2007-05-12 19:25 ` Aleksandar L. Dimitrov
2007-05-15 16:18 ` Johannes Skov Frandsen
2007-05-15 18:18 ` Francisco Rivas
2007-05-15 19:54 ` Dan Farrell
2007-05-12 15:56 ` Guillermo A. Amaral
2007-05-10 13:44 ` young sun
2007-05-08 21:22 ` Dale
[not found] ` <46411BE5.90009@paradise.net.nz>
2007-05-09 4:14 ` Dmitry
2007-05-09 0:04 ` Boyd Stephen Smith Jr. [this message]
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=200705081904.26103.bss03@volumehost.net \
--to=bss03@volumehost.net \
--cc=gentoo-user@lists.gentoo.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