Projects / cdrtools / Comments

Comments for cdrtools

15 Apr 2011 10:17 schily

It is a fact that 100% of all CD/DVD/BluRay writers are SCSI devices,
ignoring this fact would make cdrtools less useful.

BTW: cdrtools compile and run on nearly all operating systems (> 20),
its interfaces have been designed to best match all supported platforms.
If there is a problem with compiling on Linux 2.6.32, this is problem resulting
from include files that are needed for the Linux kernel interfaces but that are
frequently delivered inconsistend from the view of a userland program. Ask
your distributor for a fix to the related files.

15 Aug 2010 01:59 raycast

Not really written for Linux, but tries to force the Solaris way on everybody. Tries to see everything as a SCSI device, which is not particularly user friendly, given that 99% of CD writers nowadays are not SCSI.

12 Aug 2010 03:49 exvor

With current version of the kernel 2.6.32+ this package will no longer compile cleanly. I am using a current version of LFS and there are numerous errors about headers being incorrect. I am not sure if this is a problem with the program or with its "strange" make system that I have not seen on other projects. I do not have kernel headers in /usr/src/kernel as this is a bad practice. I hate to find an alternative but if this will not compile I have no choice.

22 Jan 2010 10:11 noamik

Well, jones501 is all wrong.

- cdrtools runs perfectly on linux (better than cdrkit)
- cdrtools supports /dev-devices, it's just a bad idea to use them, better use the scsi-id discovered with ./cdrecord --scanbus (if you have only one burning capable device, you do not even need to tell cdrecord a device, it chooses by itself)
- stuck in 1997? you mean, it still supports OSs which are this old? Why would this be a negative fact?
- if you get a lot of coasters, maybe try another burner or blanks from another vendor ... AND, cdrkit does no better, in contrary it still has lots of bugs which are not present in cdrtools anymore
- UTF-8 problems? Are you sure you used a recent version (like less than 3 years old)
- well, if you have problems with the license (which is your right of course), you can use an old version of cdrecord as well, cdrkit does no better. All they fixed are some typos in the man pages

21 Jan 2010 08:39 jones501

still crap on linux
still doesn't support real addressing schemes
still stuck in 1997
still burns coasters half the time in TAO
still can't handle utf-8 correctly
and now it's a licensing nightmare, since jorg changed the license on half the code and left it gpl on the other half.
save yourself a lot of trouble and use cdrkit, which works reliably, works right on linux, has a sane license, and isn't managed by a megalomaniac who can't handle criticism and won't accept patches

14 Oct 2009 13:18 schily

I cannot change anything on the problems that are all
caused by the hostility of the person who started "cdrkit"
and the original project is just a victim of a hostile
downstream. Many people have been fooled by this
person but more and more people realize that "cdrkit"
is full of bugs that are not fixed since years, so the needs
of the users of "cdrkit" are just ignored by the people behind it.

Fortunately, the original cdrtools project exists and is actively
maintained. The original project has no known problems. This is
because problems reported to the original project are not
ignored but dealt with care in a polite way and fixes are made
available quickly, so nobody is forced to live with the problems
in "cdrkit". All known problems caused by "cdrkit" just go away
if you upgrade to a recent original cdrtools version.

The fact that the original project cdrtools was attacked by a hostile
downstream did not change anything in cdrtools. Everything is done
to the benefit of the users in order to defend the original software
against attacks and to make sure that the original project will stay
freely available under a free, permissive license that is compatible
with the OpenSource definition from the OpenSource initiative.

Since "cdrkit" was given up by it's initiator on May 6th 2007, the original
cdrtools did have 3800 file edits in 1500 putback groups, this is a
sustained average putback rate of 4 file changes per day. Since "cdrtkit"
was started, it did not introduce any new feature but the original software
added many new features in the same time. Users can decide whether
they prefer the unmaintained "cdrkit" that was created from an extremely
outdated cdrtools version by a hostile downstream or whether they prefer
actively maintained original cdrtools software from a cooperative author.

I hope this helps people who hesitate about the state of the original

12 Oct 2009 21:38 ivan420

cdrkit 1.1.9 was released on 2008-10-26. It was created out of necessity by people fed up with the cdrtools's authors' shenanigans, not out of hostility.

Perhaps the situation is changing these days (though I would hardly call Gentoo and Slackware leading indicators), but for a point of view based on current reality rather than the author's hopes for the future, try

Hope this helps some folks out there.

12 Oct 2009 18:58 schily

I am sorry to see that "ivan420" spreads incorrect information.
Most Linux distributors corrected their mistake and
distribute the well maintained original software again.
Gentoo always distributed cdrtools as Slackware does.
Suse did go back to the original software a month ago.
Even Debian promised to go back to the original software
as soon as possible.

Redhat is currently the only noticable Linux distribution that
rejects to follow the needs of theLinux users that are interested
in working and well maintained software.
There was no problem in cdrtools that took longer than
a few hours to fix and there are no known unfixed problems in
cdrtools. drkit on the other side has a long list of bugs that have
not been fixed for years. Note that this cdrkit is unmaintained
since May 6th 2007 and was created by a hostile packaging

Read background information on the fork

12 Oct 2009 16:09 ivan420

The author is a class-A nutjob who has gotten in huge flamewars with everyone distributing his software. djb anyone? The result is a package that works well nowhere (except Solaris?) because the author has his own idea of the One True Way to talk to devices that doesn't have a basis in current reality. What. ever.

All major distributions (Red Hat, Fedora, Debian, Ubuntu, SuSE, Mandriva, Gentoo) have moved years ago to cdrkit, a fork maintained by authors who aren't hostile to distributions and their needs.

06 Jul 2009 18:09 chickenandporn

v2.01.01a61. Still "alpha". :(


Project Spotlight


An open, cross-platform journaling program.


Project Spotlight


A scientific plotting package.