Could someone please tell me how to copy cd,s. I am using 8.0 and kde3.1, I also have x-cdroast. When I check these they both have the cd-rw as reader and writer. I cannot seem to configure either to use the cd-rom as reader so that I can burn on the fly. TIA David
On Tuesday 25 March 2003 04:36, DB Troll wrote:
Could someone please tell me how to copy cd,s. I am using 8.0 and kde3.1, I also have x-cdroast. When I check these they both have the cd-rw as reader and writer. I cannot seem to configure either to use the cd-rom as reader so that I can burn on the fly.
At the moment, those programs can only see scsi devices, so to use your reader you need to set it up as a scsi emulated device Add "<device>=ide-scsi" - where <device> is something like hdc, depending on where your reader is connected in the IDE chain - to the append line in /etc/lilo.conf and run /sbin/lilo. Then you need to reboot your system. After that, your reader will be seen as /dev/sr#, where # is probably 0 or 1, so you should probably change the /dev/cdrom symlink to point to it with a command like rm /dev/cdrom ln -s /dev/sr0 /dev/cdrom look at the boot messages in /var/log/boot.msg to see which sr device is actually used on your system Then you need to make sure that you have read and write access to the generic scsi devices, with a command like chmod 666 /dev/sg* If you want to be more careful about security, set the ownership to some group and make sure your user is in that group This, very briefly, is how it's done. If you think some of the above isn't explained enough, just ask :) regards Anders
Anders Johansson wrote:
On Tuesday 25 March 2003 04:36, DB Troll wrote:
Could someone please tell me how to copy cd,s. I am using 8.0 and kde3.1, I also have x-cdroast. When I check these they both have the cd-rw as reader and writer. I cannot seem to configure either to use the cd-rom as reader so that I can burn on the fly.
At the moment, those programs can only see scsi devices, so to use your reader you need to set it up as a scsi emulated device
Add "<device>=ide-scsi" - where <device> is something like hdc, depending on where your reader is connected in the IDE chain - to the append line in /etc/lilo.conf and run /sbin/lilo. Then you need to reboot your system.
After that, your reader will be seen as /dev/sr#, where # is probably 0 or 1, so you should probably change the /dev/cdrom symlink to point to it with a command like
rm /dev/cdrom ln -s /dev/sr0 /dev/cdrom
look at the boot messages in /var/log/boot.msg to see which sr device is actually used on your system
Then you need to make sure that you have read and write access to the generic scsi devices, with a command like
chmod 666 /dev/sg*
If you want to be more careful about security, set the ownership to some group and make sure your user is in that group
This, very briefly, is how it's done. If you think some of the above isn't explained enough, just ask :)
regards Anders
Anders, Thank you very much, just followed your advice and all woks quite well. David Barrow
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 24 March 2003 23:23 pm, DB Troll wrote:
Anders Johansson wrote:
On Tuesday 25 March 2003 04:36, DB Troll wrote:
Could someone please tell me how to copy cd,s. I am using 8.0 and kde3.1, I also have x-cdroast. When I check these they both have the cd-rw as reader and writer. I cannot seem to configure either to use the cd-rom as reader so that I can burn on the fly.
At the moment, those programs can only see scsi devices, so to use your reader you need to set it up as a scsi emulated device
Add "<device>=ide-scsi" - where <device> is something like hdc, depending on where your reader is connected in the IDE chain - to the append line in /etc/lilo.conf and run /sbin/lilo. Then you need to reboot your system.
After that, your reader will be seen as /dev/sr#, where # is probably 0 or 1, so you should probably change the /dev/cdrom symlink to point to it with a command like
rm /dev/cdrom ln -s /dev/sr0 /dev/cdrom
look at the boot messages in /var/log/boot.msg to see which sr device is actually used on your system
Then you need to make sure that you have read and write access to the generic scsi devices, with a command like
chmod 666 /dev/sg*
If you want to be more careful about security, set the ownership to some group and make sure your user is in that group
This, very briefly, is how it's done. If you think some of the above isn't explained enough, just ask :)
regards Anders
Anders, Thank you very much, just followed your advice and all woks quite well. David Barrow
Just a note. In the next kernel will have "packet writing" as one of the features and will make ide cdrom burning much easier. Also, I believe there is a version of xcdroast (or perhaps it was one of the other popular cd burner apps) that has a beta of ide cdrom compatibility. I heard someone on the list mention it and also remember in the last version of SuSE (8.0) installing it. I wasn't doing a lot of burning then and for the life of me can't remember how well it worked. But I have read the changelog of 2.5 (soon to be 2.6/3.0?) and some other commentary by the devs about packet writing and better I/O for multimedia and the sort. Things are coming along steady and sure. I don't mind ide-scsi, but it would be nice to just have the cdrom/cdrecorders working out of the default interface for ide for no other reason than just installing the OS and having this functionality from the get-go, no fuss, no muss! Cheers, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+f+j97WVLiDrqeksRAkq1AJ9FONGwyNFEy9kbc0ea+5bF8auB9wCfbr2W 1l0ZITSHmjyzXDTv+A+JYFo= =FYON -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 24 March 2003 23:28 pm, Curtis Rey wrote: <snip>
Just a note. In the next kernel will have "packet writing" as one of the features and will make ide cdrom burning much easier. Also, I believe there is a version of xcdroast (or perhaps it was one of the other popular cd burner apps) that has a beta of ide cdrom compatibility. I heard someone on the list mention it and also remember in the last version of SuSE (8.0) installing it. I wasn't doing a lot of burning then and for the life of me can't remember how well it worked. But I have read the changelog of 2.5 (soon to be 2.6/3.0?) and some other commentary by the devs about packet writing and better I/O for multimedia and the sort.
Things are coming along steady and sure. I don't mind ide-scsi, but it would be nice to just have the cdrom/cdrecorders working out of the default interface for ide for no other reason than just installing the OS and having this functionality from the get-go, no fuss, no muss!
Cheers, Curtis.
I believe it was me who had written in that the beta of xcdroast worked perfectly with the latest (also new at the time) cdrecord, mkisofs, etc. I had no slow down whatsoever, though it did say on the website for cdrecord, that it was possible on some systems it could be extremely slow. I was tickled pink when it worked like it did, becaue I *didn't* have to piddle with the scsi stuff, heh. Anyway, just another heads up to let everyone know it worked very well on my system, but remember, YMMV. John -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+gFNbH5oDXyLKXKQRAscaAJ4vVXjsl35n5qWZ6ni3h8ucYEMJgQCeMaP0 a8yZgGfYTSvQgPKAe7HWUuY= =jH06 -----END PGP SIGNATURE-----
The 03.03.24 at 23:28, Curtis Rey wrote:
Just a note. In the next kernel will have "packet writing" as one of the features and will make ide cdrom burning much easier. Also, I believe there is a version of xcdroast (or perhaps it was one of the other popular cd burner apps) that has a beta of ide cdrom compatibility. I heard someone on
Yes, but it requires the new cdrtools 2.0 from Schilling to work, replacing suse mkisofs.rpm and cdrecord.rpm - and that gives dependency problems. -- Cheers, Carlos Robinson
On 03/25/2003 09:15 PM, Carlos E. R. wrote:
Yes, but it requires the new cdrtools 2.0 from Schilling to work, replacing suse mkisofs.rpm and cdrecord.rpm - and that gives dependency problems.
Just rebuild the source rpm. If I remember correctly, you need to add a -n to the package descriptions to subtract the cdrtools- prefix. It worked well for me. YMMV -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
The 03.03.25 at 22:11, Joe Morris (NTM) wrote:
Yes, but it requires the new cdrtools 2.0 from Schilling to work, replacing suse mkisofs.rpm and cdrecord.rpm - and that gives dependency problems.
Just rebuild the source rpm. If I remember correctly, you need to add a -n to the package descriptions to subtract the cdrtools- prefix. It worked well for me. YMMV
No, it is another package altogether that requires cdrecord and mkisofs, not cdrtools. Cdrtools is not a suse package: suse breaks it in the other two, and those are required by some others. I solved it by creating dummie packages cdrecord and mkisofs. The funtionality is in cdrtools. -- Cheers, Carlos Robinson
If you are asking, specifically, how to copy a CD, the best instructions come from the book "Linux Server Hacks" by Rob Flickenger (O'Reilly). Page 85: dd if=/dev/hdb | cdrecord -v speed=12 dev=0,0,0 fs=8m -data - This copies a cd from device hdb to your cdwriter on device=0,0,0 Obviously if you have only a CDRW device, you need to copy the iso image to the hard disk, first. (The book has all these steps spelled out. I really recommend this book. It has great advice on ssh setup, rsync for backups, etc. And it is relatively inexpensive. Paul Alfille On Monday 24 March 2003 22:46, Anders Johansson wrote:
On Tuesday 25 March 2003 04:36, DB Troll wrote:
Could someone please tell me how to copy cd,s. I am using 8.0 and kde3.1, I also have x-cdroast. When I check these they both have the cd-rw as reader and writer. I cannot seem to configure either to use the cd-rom as reader so that I can burn on the fly.
At the moment, those programs can only see scsi devices, so to use your reader you need to set it up as a scsi emulated device
Add "<device>=ide-scsi" - where <device> is something like hdc, depending on where your reader is connected in the IDE chain - to the append line in /etc/lilo.conf and run /sbin/lilo. Then you need to reboot your system.
After that, your reader will be seen as /dev/sr#, where # is probably 0 or 1, so you should probably change the /dev/cdrom symlink to point to it with a command like
rm /dev/cdrom ln -s /dev/sr0 /dev/cdrom
look at the boot messages in /var/log/boot.msg to see which sr device is actually used on your system
Then you need to make sure that you have read and write access to the generic scsi devices, with a command like
chmod 666 /dev/sg*
If you want to be more careful about security, set the ownership to some group and make sure your user is in that group
This, very briefly, is how it's done. If you think some of the above isn't explained enough, just ask :)
regards Anders
On Monday 24 March 2003 10:36 pm, DB Troll wrote:
Could someone please tell me how to copy cd,s. I am using 8.0 and kde3.1, I also have x-cdroast. When I check these they both have the cd-rw as reader and writer. I cannot seem to configure either to use the cd-rom as reader so that I can burn on the fly. TIA David =======================
David, Actually burning on the fly with two IDE devices, especially if they are cdrom units, is not one of the best ideas. It can be done if you have a fast machine and suspend doing any other cpu intensive task at the time. I think having DMA activated on both drives may help a bit also. Moving data from the hard drives to cdrw works best, you get fewer buffer underruns that way. The new cdrw drives have a feature called "Burn Proof" technology which helps to prevent the buffer underruns, but that still won't assure you of a good burn from cd to cd. Of course, cdrs are pretty cheap now, so turning many into coasters is not a big thing, except for the landfills they go in later. :o) No, not going to start in on ecology stuff, just making a point on burning. Of course, you still have to remember the things Anders points out in his mail. In order to use both drives in the burning programs, they both have to be scsi emulated for the moment. That is soon to disappear with the new programs coming out, but for the moment it is needed. Follow Ander's advice and if you still need help getting things working, give a yell. Patrick -- --- KMail v1.5 --- SuSE Linux Pro v8.1 --- Registered Linux User #225206 On any other day, that might seem strange...
participants (8)
-
Anders Johansson -
Carlos E. R. -
Curtis Rey -
DB Troll -
Joe Morris (NTM) -
John -
O'Smith -
Paul Alfille