Difference: CdWriter (1 vs. 14)

Revision 1418 Sep 2010 - TobyCabot

Line: 1 to 1
 HP 9350i 10x4x32 IDE, slave on ide0

As of Linux 2.6 you don't seem to need to use SCSI emulation anymore as long as you tell cdrecord what to do using dev=ATAPI on the command line.

Line: 83 to 83
 Some CD's are a little more challenging. They use the same trick that they used to use back in the C64 days: they put deliberate errors on the DVD in the hopes that they will confuse the software that people use to play them. For those disks you need to ddrescue them (dd_help helps greatly with this), then dvdbackup the vobs that you want to keep.

Some tips: http://gentoo-wiki.com/HOWTO_Backup_a_DVD

Added:
>
>
Rip audio (e.g. title 9): $ transcode -i /dev/dvd -x dvd -T 9,-1 -a 0 -y null,raw -m tune.mp3

Revision 1311 Jan 2009 - TobyCabot

Line: 1 to 1
 HP 9350i 10x4x32 IDE, slave on ide0

As of Linux 2.6 you don't seem to need to use SCSI emulation anymore as long as you tell cdrecord what to do using dev=ATAPI on the command line.

Line: 6 to 6
 Also make sure that the ide_generic and ide_cd modules are loaded.


Changed:
<
<
tobyc@dickless:~$ cdrecord -scanbus dev=ATAPI
>
>
$ cdrecord -scanbus dev=ATAPI
 Cdrecord-Clone 2.01a27 (i686-pc-linux-gnu) Copyright (C) 1995-2004 J�rg Schilling NOTE: this version of cdrecord is an inofficial (modified) release of cdrecord and thus may have bugs that are not present in the original version.
Line: 29 to 29
  0,5,0 5) * 0,6,0 6) * 0,7,0 7) *
Changed:
<
<
tobyc@dickless:~$
>
>
 


Line: 71 to 71
  On the other hand, burning is pretty easy if you've got the wav files handy:

Changed:
<
<
cdrecord -v -pad speed=8 dev=ATAPI:0,0,0 -dao -audio -swab *.wav

>
>
wodim -v *.wav

DVD's

DVD's are very sensitive to scratches, fingerprints, etc. If you let your kids handle DVD's then it's a very good idea to make a copy and have them watch that so when they inevitably scratch it you've got the original someplace safe.

For many CD's you can use vobcopy to pull the vobs from the original disk and stash them someplace safe.

Some CD's are a little more challenging. They use the same trick that they used to use back in the C64 days: they put deliberate errors on the DVD in the hopes that they will confuse the software that people use to play them. For those disks you need to ddrescue them (dd_help helps greatly with this), then dvdbackup the vobs that you want to keep.

 
Added:
>
>
Some tips: http://gentoo-wiki.com/HOWTO_Backup_a_DVD

Revision 1211 Dec 2004 - TobyCabot

Line: 1 to 1
 HP 9350i 10x4x32 IDE, slave on ide0

As of Linux 2.6 you don't seem to need to use SCSI emulation anymore as long as you tell cdrecord what to do using dev=ATAPI on the command line.

Changed:
<
<
Also make sure that the ide_generic module is loaded.
>
>
Also make sure that the ide_generic and ide_cd modules are loaded.
 
tobyc@dickless:~$ cdrecord -scanbus dev=ATAPI

Revision 1107 Nov 2004 - TobyCabot

Line: 1 to 1
 HP 9350i 10x4x32 IDE, slave on ide0

As of Linux 2.6 you don't seem to need to use SCSI emulation anymore as long as you tell cdrecord what to do using dev=ATAPI on the command line.

Line: 49 to 49
 Then you can burn a CD with the image (note that the blank=fast flag tells cdrecord to erase the media first - this only works with cd/rw media, also note that the "0,0,0" matches what cdrecord -scanbus output above):


Changed:
<
<
# cdrecord -v speed=4 dev=ATAPI:0,0,0 blank=fast -data /mnt/test/cd_image
>
>
# cdrecord -v speed=8 dev=ATAPI:0,0,0 -data /mnt/test/cd_image
 
Added:
>
>
If you're burning a rewriteable CD you can use blank=fast just before -data.
 Alternatively you can pipe the output of mkisofs into cdrecord. This doesn't chew up a lot of temporary disk storage, but you don't get to look at the results before you burn them. This is probably OK if you're using cd/rw media or if you're running the same script over and over (e.g. backups):


Revision 1021 Aug 2004 - TobyCabot

Line: 1 to 1
 HP 9350i 10x4x32 IDE, slave on ide0

As of Linux 2.6 you don't seem to need to use SCSI emulation anymore as long as you tell cdrecord what to do using dev=ATAPI on the command line.

Line: 69 to 69
  On the other hand, burning is pretty easy if you've got the wav files handy:

Changed:
<
<
cdrecord -v -pad speed=1 dev=ATAPI:0,0,0 -dao -audio -swab *.wav
>
>
cdrecord -v -pad speed=8 dev=ATAPI:0,0,0 -dao -audio -swab *.wav
 

Revision 904 May 2004 - TobyCabot

Line: 1 to 1
 HP 9350i 10x4x32 IDE, slave on ide0
Changed:
<
<
Read CD-writing HOWTO at LDP ( http://en.tldp.org/HOWTO/CD-Writing-HOWTO.html ).
>
>
As of Linux 2.6 you don't seem to need to use SCSI emulation anymore as long as you tell cdrecord what to do using dev=ATAPI on the command line.
 
Changed:
<
<
In a nutshell you need to configure the ide-scsi module so that the cdrecord tool thinks it's writing to a scsi burner. Note that the device shows up as /dev/scd0, not /dev/hdd.

Using modules you need to load ide-scsi before ide-cd so that it grabs the cdrom, or else tell ide-cd not to use one of the cdrom drives.

If you want to let people other than root use the CD drive you'll need to chmod both /dev/scd0 and /dev/sg0.

>
>
Also make sure that the ide_generic module is loaded.
 

Changed:
<
<
poohpa:~# cdrecord -scanbus Cdrecord 1.8 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling Using libscg version 'schily-0.1'
>
>
tobyc@dickless:~$ cdrecord -scanbus dev=ATAPI Cdrecord-Clone 2.01a27 (i686-pc-linux-gnu) Copyright (C) 1995-2004 J�rg Schilling NOTE: this version of cdrecord is an inofficial (modified) release of cdrecord and thus may have bugs that are not present in the original version. Please send bug reports and support requests to <cdrtools@packages.debian.org>. The original author should not be bothered with problems of this version.

scsidev: 'ATAPI' devname: 'ATAPI' scsibus: -2 target: -2 lun: -2 Warning: Using ATA Packet interface. Warning: The related libscg interface code is in pre alpha. Warning: There may be fatal problems. Using libscg version 'schily-0.8'.

 scsibus0: 0,0,0 0) 'HP ' 'CD-Writer+ 9300 ' '1.0b' Removable CD-ROM 0,1,0 1) *
Line: 22 to 29
  0,5,0 5) * 0,6,0 6) * 0,7,0 7) *
Changed:
<
<
poohpa:~#
>
>
tobyc@dickless:~$
 
Deleted:
<
<
http://www.torque.net/scsi/SCSI-2.4-HOWTO/ - the The Linux 2.4 SCSI subsystem HOWTO is helpful in figuring out which modules need to be loaded and in what order.
 
You use mkisofs to make the iso 9660 filesystem image and then cdrecord to write it to the disk (both packages can be dselected). For example, this will build a filesystem image called /mnt/test/cd_image with /home/cvs as /cvs, /home/www as /www, and /home/postgres as /postgres:
Line: 44 to 49
 Then you can burn a CD with the image (note that the blank=fast flag tells cdrecord to erase the media first - this only works with cd/rw media, also note that the "0,0,0" matches what cdrecord -scanbus output above):


Changed:
<
<
# cdrecord -v speed=4 dev=0,0,0 blank=fast -data /mnt/test/cd_image
>
>
# cdrecord -v speed=4 dev=ATAPI:0,0,0 blank=fast -data /mnt/test/cd_image
 

Alternatively you can pipe the output of mkisofs into cdrecord. This doesn't chew up a lot of temporary disk storage, but you don't get to look at the results before you burn them. This is probably OK if you're using cd/rw media or if you're running the same script over and over (e.g. backups):

# cd /home

Changed:
<
<
# mkisofs -r cvs/=cvs www/=www postgres/=postgres | cdrecord -v speed=4 dev=0,0,0 blank=fast -data -
>
>
# mkisofs -r cvs/=cvs www/=www postgres/=postgres | cdrecord -v speed=4 dev=ATAPI:0,0,0 blank=fast -data -
 

The HOWTO talks about having to do a pro-forma mkisofs run to find out how big the image will be but it appears that the HP 9350i doesn't require this.

Line: 64 to 69
  On the other hand, burning is pretty easy if you've got the wav files handy:

Changed:
<
<
cdrecord -v -pad speed=1 dev=0,0,0 -dao -audio -swab *.wav
>
>
cdrecord -v -pad speed=1 dev=ATAPI:0,0,0 -dao -audio -swab *.wav
 

Revision 811 Oct 2003 - TobyCabot

Line: 1 to 1
 HP 9350i 10x4x32 IDE, slave on ide0

Read CD-writing HOWTO at LDP ( http://en.tldp.org/HOWTO/CD-Writing-HOWTO.html ).

Line: 60 to 60
  Of the tools that you can "dselect" only cdrtoaster appears to be able to take mp3's as input and burn them onto an audio disc.
Added:
>
>
I tried two KDE programs - arson and k3d and neither was capable of actually burning a disc.

On the other hand, burning is pretty easy if you've got the wav files handy:

cdrecord -v -pad speed=1 dev=0,0,0 -dao -audio  -swab *.wav

Revision 731 Dec 2002 - TobyCabot

Line: 1 to 1
 HP 9350i 10x4x32 IDE, slave on ide0

Read CD-writing HOWTO at LDP ( http://en.tldp.org/HOWTO/CD-Writing-HOWTO.html ).

In a nutshell you need to configure the ide-scsi module so that the cdrecord tool thinks it's writing to a scsi burner. Note that the device shows up as /dev/scd0, not /dev/hdd.

Added:
>
>
Using modules you need to load ide-scsi before ide-cd so that it grabs the cdrom, or else tell ide-cd not to use one of the cdrom drives.
 If you want to let people other than root use the CD drive you'll need to chmod both /dev/scd0 and /dev/sg0.


Line: 23 to 25
 poohpa:~#
Added:
>
>
http://www.torque.net/scsi/SCSI-2.4-HOWTO/ - the The Linux 2.4 SCSI subsystem HOWTO is helpful in figuring out which modules need to be loaded and in what order.


 You use mkisofs to make the iso 9660 filesystem image and then cdrecord to write it to the disk (both packages can be dselected). For example, this will build a filesystem image called /mnt/test/cd_image with /home/cvs as /cvs, /home/www as /www, and /home/postgres as /postgres:


Revision 629 Dec 2002 - TobyCabot

Line: 1 to 1
 HP 9350i 10x4x32 IDE, slave on ide0
Changed:
<
<
Read CD-writing HOWTO at LDP ( http://www.linuxdoc.org/HOWTO/CD-Writing-HOWTO.html ).
>
>
Read CD-writing HOWTO at LDP ( http://en.tldp.org/HOWTO/CD-Writing-HOWTO.html ).
  In a nutshell you need to configure the ide-scsi module so that the cdrecord tool thinks it's writing to a scsi burner. Note that the device shows up as /dev/scd0, not /dev/hdd.

Revision 510 Feb 2001 - TobyCabot

Line: 50 to 50
  The HOWTO talks about having to do a pro-forma mkisofs run to find out how big the image will be but it appears that the HP 9350i doesn't require this.
Added:
>
>
Audio CD's
 
Added:
>
>
Of the tools that you can "dselect" only cdrtoaster appears to be able to take mp3's as input and burn them onto an audio disc.
 
Deleted:
<
<
-- TobyCabot - 03 Jan 2001

Revision 410 Feb 2001 - TobyCabot

Line: 4 to 4
  In a nutshell you need to configure the ide-scsi module so that the cdrecord tool thinks it's writing to a scsi burner. Note that the device shows up as /dev/scd0, not /dev/hdd.
Added:
>
>
If you want to let people other than root use the CD drive you'll need to chmod both /dev/scd0 and /dev/sg0.
 
poohpa:~# cdrecord -scanbus
Cdrecord 1.8 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling

Revision 323 Jan 2001 - TobyCabot

Revision 216 Jan 2001 - TobyCabot

Line: 1 to 1
 HP 9350i 10x4x32 IDE, slave on ide0
Changed:
<
<
Read CD-writing HOWTO at LDP.
>
>
Read CD-writing HOWTO at LDP (http://www.linuxdoc.org/HOWTO/CD-Writing-HOWTO.html).
 
Changed:
<
<
In a nutshell you need to configure the ide-scsi module so that the cdrecord tool thinks it's writing to a scsi burner. Note that the device shows up as /dev/scd0, not /dev/hdb.
>
>
In a nutshell you need to configure the ide-scsi module so that the cdrecord tool thinks it's writing to a scsi burner. Note that the device shows up as /dev/scd0, not /dev/hdd.
 
poohpa:~# cdrecord -scanbus

Line: 42 to 42
 Alternatively you can pipe the output of mkisofs into cdrecord. This doesn't chew up a lot of temporary disk storage, but you don't get to look at the results before you burn them. This is probably OK if you're using cd/rw media or if you're running the same script over and over (e.g. backups):


Changed:
<
<
mkisofs -r cvs/=cvs www/=www postgres/=postgres | cdrecord -v speed=4 dev=0,0,0 blank=fast -data -
>
>
# cd /home # mkisofs -r cvs/=cvs www/=www postgres/=postgres | cdrecord -v speed=4 dev=0,0,0 blank=fast -data -
 

The HOWTO talks about having to do a pro-forma mkisofs run to find out how big the image will be but it appears that the HP 9350i doesn't require this.

Revision 103 Jan 2001 - TobyCabot

Line: 1 to 1
Added:
>
>
HP 9350i 10x4x32 IDE, slave on ide0

Read CD-writing HOWTO at LDP.

In a nutshell you need to configure the ide-scsi module so that the cdrecord tool thinks it's writing to a scsi burner. Note that the device shows up as /dev/scd0, not /dev/hdb.

poohpa:~# cdrecord -scanbus
Cdrecord 1.8 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling
Using libscg version 'schily-0.1'
scsibus0:
		  0,0,0	  0) 'HP		' 'CD-Writer+ 9300 ' '1.0b' Removable CD-ROM
		  0,1,0	  1) *
		  0,2,0	  2) *
		  0,3,0	  3) *
		  0,4,0	  4) *
		  0,5,0	  5) *
		  0,6,0	  6) *
		  0,7,0	  7) *
poohpa:~# 

You use mkisofs to make the iso 9660 filesystem image and then cdrecord to write it to the disk (both packages can be dselected). For example, this will build a filesystem image called /mnt/test/cd_image with /home/cvs as /cvs, /home/www as /www, and /home/postgres as /postgres:

# cd /home
# mkisofs -r -o /mnt/test/cd_image cvs/=cvs www/=www postgres/=postgres

You can mount the image via loopback to see if it's what you want:

# mount -t iso9660 -o ro,loop=/dev/loop0 /mnt/test/cd_image /mnt/cdrom

Then you can burn a CD with the image (note that the blank=fast flag tells cdrecord to erase the media first - this only works with cd/rw media, also note that the "0,0,0" matches what cdrecord -scanbus output above):

# cdrecord -v speed=4 dev=0,0,0 blank=fast -data /mnt/test/cd_image 

Alternatively you can pipe the output of mkisofs into cdrecord. This doesn't chew up a lot of temporary disk storage, but you don't get to look at the results before you burn them. This is probably OK if you're using cd/rw media or if you're running the same script over and over (e.g. backups):

mkisofs -r cvs/=cvs www/=www postgres/=postgres | cdrecord -v speed=4 dev=0,0,0 blank=fast -data -

The HOWTO talks about having to do a pro-forma mkisofs run to find out how big the image will be but it appears that the HP 9350i doesn't require this.

-- TobyCabot - 03 Jan 2001

View topic | History: r14 < r13 < r12 < r11 | More topic actions...
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding The Caboteria? Send feedback