Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
cdrecord: Warning: Running on Linux-2.6.10
TOC Type: 1 = CD-ROM
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
scsidev: 'ATAPI:0,0,0'
devname: 'ATAPI'
scsibus: 0 target: 0 lun: 0
Warning: Using ATA Packet interface.
Warning: The related Linux kernel interface code seems to be unmaintained.
Warning: There is absolutely NO DMA, operations thus are slow.
cdrecord: No such file or directory. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
When I upgraded from 2.4.26 to 2.6.7 I lost the good
command line CD burning I'd had with cdrecord. I've
read a whole lot, and IMO Jörg Schilling has issues with
the kernel developers. I'm not knowledgable enough to
know (or care) who's right and who's wrong -- but we as
the users are suffering.
The issue is that Linus Torvalds decided to drop scsi
emulation for IDE devices, and Jörg Schilling didn't seem
to agree. So his app didn't keep up -- except for his
choice of distro -- Solaris.
Now that's perfectly okay, in the letter of the law, for he
owns cdrecord and can do whatever he wants with it.
IMO Linus and the other kernel devs have had their fill of
him, and I expect to see his app get forked, or something,
and a better app come along that will "play well with
others."
So now that I'm running 2.6.7 I can only get cdrecord to
burn CDs at maybe 10x with my 52x CD-RW drive. However,
I installed K3B and it works just fine using that app.
Therefore, though I loved burning at cli with cdrecord, I have
abandoned it in favor of K3B for now with 2.6.x.
I'll monitor your thread in hopes that someone with more
information and knowledge comes along. There are a lot
of technical issues that can be discussed, such as the fact
that Linus decided to deprecate scsi emulation or whatever
we used before 2.6.x.
For this and other reasons, I'm soon recompiling and using
a 2.4.29 kernel rather than any 2.6.x series -- though it's
said to be "stable" the philosophy behind stable has changed,
and 2.6.x is ever changing and actually rather unstable!
if you wish to continue with 2.6.x
recompile cdrtools
much to the kernel developers ire
cdrtools compiles against currently running kernel rather than kernel interface in glibc (i think)
at least he has the package set up to do that if it can through the old interface of /usr/src/linux
if i were compiling cdrtools against a kernel other than the one whose headers are in /usr/include
i would create the link /usr/src/linux to the current kernel build directory
as Schilling puts it -- Linux users are of the mistaken impression that the kernel can be upgraded.
in other words when you upgrade to kernel 2.6.x but still have user space headers and glibc compiled for 2.4.x you have a system that is somewhat broken as glibc and all other user space programs can no longer access the kernel correctly.
he has a point as he is trying to interface with a currently running kernel side driver.
as to who is right and who is wrong in this.
cdrtools supports some 500 devices accross 20 some different hardware architectures on many (5 or more i guess) different OS platforms. Nuf Said
if cdrtools is compiled properly the ide-scsi interface it still alot better that the ide-cd interface provided by the kernel developers
Both compiled from source, by me. The 2.6.7 kernel
was compiled a month before cdrtools -- which, btw,
is borked against many devices, kernels, and OSs...
Just like Schilling...you can argue this point, that it works
with some other OS and not Linux. And yes, it's his
app, so he can write it correctly for whichever OS he
prefers, i.e. Solaris, and not fix it for Linux - for which
he had more than a year's notice, btw. He loses, as
Linux users run something else, or at least a front-end to
make his app work properly.
He will either fix his silly little app, or someone else will
fork it and fix it and rename it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.