[Debburn-changes] r440 - cdrkit/trunk/doc/READMEs
Eduard Bloch
blade at alioth.debian.org
Thu Nov 23 20:55:19 CET 2006
Author: blade
Date: 2006-11-23 20:55:19 +0100 (Thu, 23 Nov 2006)
New Revision: 440
Added:
cdrkit/trunk/doc/READMEs/README.netscsid
Removed:
cdrkit/trunk/doc/READMEs/README.rscsi
Modified:
cdrkit/trunk/doc/READMEs/README.ATAPI
cdrkit/trunk/doc/READMEs/README.audio
cdrkit/trunk/doc/READMEs/README.copy
cdrkit/trunk/doc/READMEs/README.sony
Log:
documentation update of readmes, more cdrecord -> wodim
Modified: cdrkit/trunk/doc/READMEs/README.ATAPI
===================================================================
--- cdrkit/trunk/doc/READMEs/README.ATAPI 2006-11-23 19:44:13 UTC (rev 439)
+++ cdrkit/trunk/doc/READMEs/README.ATAPI 2006-11-23 19:55:19 UTC (rev 440)
@@ -293,7 +293,7 @@
yet to be officially incorporated into cdwrite and the kernel. In order to
get your drive supported under Linux, you will have to do the following:
-1. Get the proper version of wodim.
+1. Get the proper version of cdrecord.
As of this writing, I am just getting ready to test Joerg's new cdrecord.
I am currently operational on cdrecord-1.5, so I know that works, and I
Modified: cdrkit/trunk/doc/READMEs/README.audio
===================================================================
--- cdrkit/trunk/doc/READMEs/README.audio 2006-11-23 19:44:13 UTC (rev 439)
+++ cdrkit/trunk/doc/READMEs/README.audio 2006-11-23 19:55:19 UTC (rev 440)
@@ -1,22 +1,22 @@
Why do I hear only noise from my first audio CD?
-You may have a byte swapping problem, try cdrecord -swab
+You may have a byte swapping problem, try wodim -swab
but note that is is most unlikely that you need to use the -swab
-option from cdrecord unless your input files are broken.
+option from wodim unless your input files are broken.
It makes more sense to find out why the inout files are not OK.
-Cdrecord assumes Motorola/Network byte order (big-endian) on input
-regardless of the byte order of the CD-Recorder. If Cdrecord
+wodim assumes Motorola/Network byte order (big-endian) on input
+regardless of the byte order of the CD-Recorder. If wodim
encounters a .wav file, byte order is corrected to match the byte order
of the .wav file.
-Cdrecord by default uses Track at once. This always gives 2 seconds
+wodim by default uses Track at once. This always gives 2 seconds
pause between two audio tracks and loweres the audio quality.
-For best audio CD quality, use cdrecord -dao (to write in Session At Once)
-ot cdrecord -raw (to write in RAW mode). Note that there are a lot of drives
+For best audio CD quality, use wodim -dao (to write in Session At Once)
+ot wodim -raw (to write in RAW mode). Note that there are a lot of drives
notably from Lite-ON that have defective firmware and will write defective
-CDs if you use either TAO or SAO mode. In RAW mode, cdrecord has the
+CDs if you use either TAO or SAO mode. In RAW mode, wodim has the
full control over the complete CD and the chance that the CD is OK
is much higher.
@@ -47,4 +47,4 @@
pre-gap (usually holding 2 seconds of pause) at the end of the previous
track.
-Joerg Schilling
+Eduard Bloch, based on documentation from Joerg Schilling
Modified: cdrkit/trunk/doc/READMEs/README.copy
===================================================================
--- cdrkit/trunk/doc/READMEs/README.copy 2006-11-23 19:44:13 UTC (rev 439)
+++ cdrkit/trunk/doc/READMEs/README.copy 2006-11-23 19:55:19 UTC (rev 440)
@@ -2,14 +2,14 @@
Copying audio CD's:
-If you want to copy audio CD's, look for 'cdda2wav'. Be sure tu use use
+If you want to copy audio CD's, look for 'icedax'. Be sure tu use use
at least a cdda2wav-0.95beta or later. Older releases will not read correctly
from SCSI-3/mmc compliant drives.
Copying data CD's:
The best way to copy a data disk is to copy the raw data on the master CD.
-This may be done by reading the data from the raw device by using 'readcd'.
+This may be done by reading the data from the raw device by using 'readom'.
NOTE: All CD-R's written in Track At Once mode end in two unreadable
@@ -24,21 +24,21 @@
If you want to copy such a CD directly with wodim, you may call:
- wodim -v dev=... -isosize /dev/rdsk/c0t6d0s0
+ wodim -v dev=... -isosize /dev/cdrw
But this may fail if the master gives read errors. To copy such a CD to a file
-you may use the program 'readcd' from this package
+you may use the program 'readom' from this package
-Call 'readcd [target] [lun] [scsibusno]' and select function 11.
-Or call readcd -help to get alternate usage.
-To prevent readcd from reading the run-out sectors, reduce the
+Call 'readom [target] [lun] [scsibusno]' and select function 11.
+Or call readom -help to get alternate usage.
+To prevent readom from reading the run-out sectors, reduce the
number of sectors to copy by 2.
-Recent readcd versions may be called: readcd dev=b,t,l f=outfile
+Recent readom versions may be called: readom dev=b,t,l f=outfile
To reduce the numbers of sectors to copy you may use the sectors= option.
If the master disk is made of several partitions (like a Solaris boot CD),
-the best way to copy a CD is to use the program 'readcd'. It ignores
+the best way to copy a CD is to use the program 'readom'. It ignores
the partition info and does raw SCSI reads.
If you like to copy audio CD's in a way that preserves as much accuracy as
@@ -50,6 +50,6 @@
This will preserve pre-gap sizes, indices ...
-Source: README.copy from cdrtools package
-Edited for cdrkit by Christian Fromme <kaner at strace.org>
+Source: README.copy from cdrtools package, version 2.01.01a08
+Edited for cdrkit by Christian Fromme <kaner at strace.org> and Eduard Bloch <blade at debian.org>
Copied: cdrkit/trunk/doc/READMEs/README.netscsid (from rev 435, cdrkit/trunk/doc/READMEs/README.rscsi)
===================================================================
--- cdrkit/trunk/doc/READMEs/README.rscsi 2006-11-23 19:19:33 UTC (rev 435)
+++ cdrkit/trunk/doc/READMEs/README.netscsid 2006-11-23 19:55:19 UTC (rev 440)
@@ -0,0 +1,131 @@
+The Remote-SCSI protocol gives you SCSI-Anywhere features.
+
+The protocol used by netscsid is based on rscsi from the cdrtools, developed by
+Joerg Schilling. However, no guarantee for the compatibility or reliability can
+be made. This documentation is based on rscsi documentation from Joerg
+Schilling, but is not identical to the original.
+
+There are three possible ways to control access to the remote users:
+
+ - Let the remote scsi lib log in as a standard user.
+ In this case netscsid will be called via sh -c netscsid /usr/sbin/netscsid
+ NOTE: In this case, netscsid must be installed suid root.
+ --- This would need to allow any valid local user to access SCSI ----
+ It could be a security problem.
+
+ - Log in as root and call netscsid via sh -c netscsid
+ NOTE that this will fore you to allow remote logins as root
+ which is considered to be a security hole.
+
+ - Create one or more special user(s) that have netscsid
+ as login shell with their own home directory.
+ You then may create special .rhosts files for each user.
+ NOTE: In this case, netscsid must be installed suid root.
+ **** This is the preferred method ****
+
+To enable remote SCSI via the login shell method you should do the following:
+
+ - Add an entry to /etc/passwd in the form:
+
+ netscsid:x:1999:1000:Tape:/export/home/netscsid:/usr/sbin/netscsid
+
+ (modify this according to your OS). And don't forget to
+ modify /etc/shadow the way it needs to be on your OS.
+
+ - Create a home directory for this user and add a .rhosts file
+ to allow access to all users you like.
+
+ - Install netscsid suid root into /usr/sbin
+
+ - Install a file /etc/netscsid.conf and define access rights.
+ Without this file, netscsid will not work at all.
+
+ The template for this file is: netscsid/netscsid.dfl
+
+NETSCSID Security:
+
+- When netscsid starts, it checks if /etc/netscsid.conf exists.
+ If not, it dies.
+
+- If netscsid is not called by a user listed in /etc/netscsid.conf
+ it dies.
+
+- To access a SCSI target there must be an entry that lists the user
+ rcsi hast been started from, the hostname and the SCSI target.
+
+ netscsid compares the hostname field in /etc/netscsid.conf
+ to the peername retrived from STDIN:
+
+ - legal host name IP connection
+ - "ILLEGAL_SOCKET" Not an IP socket
+ - "NOT_IP" Not a socket
+
+NETSCSID Security hints:
+
+- Do not generally allow other users to see your boot disk via NETSCSID.
+ All people who see this disk may edit your passwd file.
+
+- If you are in doubt, only export CD-ROM drives, scanners and similar
+ devices that are not directly security sensitive.
+
+If anybody sees a security hole in my security precautions, please send me a mail!
+
+NETSCSID usage:
+
+- To use remote SCSI devices you need to know how to access a specific remote
+ SCSI target.
+
+ - dev=REMOTE:host: or dev=REMOTE:host
+ will allow you to do SCSI bus scanning while you log in as yourself
+
+ - dev=REMOTE:user at host: or dev=REMOTE:user at host
+ will allow you to do SCSI bus scanning while you log in as "user"
+
+ If you use the setup described above, you should use:
+
+ dev=REMOTE:netscsid at babbel:
+
+ to do SCSI Bus scanning on host babbel
+
+ - To access a specific SCSI device, you must specify
+ dev=REMOTE:host:<target spec> or dev=REMOTE:user at host:<target spec>
+ <target spec> is the SCSI target specification as it is needed
+ on the remote host
+
+ dev=REMOTE:netscsid at babbel:1,3,0
+
+ Will let you log in as netscsid on host babbel and open Target 3 lun 0
+ on SCSI bus #1
+
+ - If you use wodim -vv ...., wodim will on startup print some
+ information about the remote libscg version used for the connection.
+
+- To be able to use the remote SCSI client code from win32 you need to create
+ a file /etc/passwd with a correct entry for the user you are on win32.
+ Call 'id' to get the right user id.
+ Note that remote SCSI has not yet been tested on Win32.
+
+NETSCSID speed:
+
+- On a Ultra-10 running Solaris 8, the command overhead time is 400 usec.
+ You may achieve up to 9900 kB/s via a 100MB/s ethernet connection
+ between two of such machines.
+
+- With 100 MB/s, 12x recording should be no problem.
+
+- With 10 MB/s, 4x recording is the maximum. Do tests before!
+
+- Logging into a remote machine and running wodim on the remote machine
+ causes the buffer cache on that machine to be trashed. The main user
+ is disturbed.
+
+- Doing cdrecording via Remote SCSI causes only the netscsid command with less
+ than 200kB to be needed on the remote machine hosting the CD recorder.
+ The main user on that machine is not disturbed.
+ The buffer cache of the machine running wodim is trashed.
+
+- It is desirable to use a Burn-Proof recorder to make sure that network
+ load will not cause buffer underruns.
+
+
+- USER= test and test for hostname are using a pattern matcher.
Deleted: cdrkit/trunk/doc/READMEs/README.rscsi
===================================================================
--- cdrkit/trunk/doc/READMEs/README.rscsi 2006-11-23 19:44:13 UTC (rev 439)
+++ cdrkit/trunk/doc/READMEs/README.rscsi 2006-11-23 19:55:19 UTC (rev 440)
@@ -1,126 +0,0 @@
-The Remote-SCSI protocol gives you SCSI-Anywhere features.
-
-There are three possible ways to control access to the remote users:
-
- - Let the remote scsi lib log in as a standard user.
- In this case rscsi will be called via sh -c /opt/schily/sbin/rscsi
- NOTE: In this case, rscsi must be installed suid root.
- --- This would need to allow any valid local user to access SCSI ----
- It could be a security problem.
-
- - Log in as root and call rscsi via sh -c /opt/schily/sbin/rscsi
- NOTE that this will fore you to allow remote logins as root
- which is considered to be a security hole.
-
- - Create one or more special user(s) that have /opt/schily/sbin/rscsi
- as login shell with their own home directory.
- You then may create special .rhosts files for each user.
- NOTE: In this case, rscsi must be installed suid root.
- **** This is the preferred method ****
-
-To enable remote SCSI via the login shell method you should do the following:
-
- - Add an entry to /etc/passwd in the form:
-
- rscsi:x:1999:1000:Tape:/export/home/rscsi:/opt/schily/sbin/rscsi
-
- (modify this according to your OS). And don't forget to
- modify /etc/shadow the way it needs to be on your OS.
-
- - Create a home directory for this user and add a .rhosts file
- to allow access to all users you like.
-
- - Install rscsi suid root into /opt/schily/sbin
-
- - Install a file /etc/rscsi.conf and define access rights.
- Without this file, rscsi will not work at all.
-
- The template for this file is: rscsi/rscsi.dfl
-
-RSCSI Security:
-
-- When rscsi starts, it checks if /etc/rscsi.conf exists.
- If not, it dies.
-
-- If rscsi is not called by a user listed in /etc/rscsi.conf
- it dies.
-
-- To access a SCSI target there must be an entry that lists the user
- rcsi hast been started from, the hostname and the SCSI target.
-
- rscsi compares the hostname field in /etc/rscsi.conf
- to the peername retrived from STDIN:
-
- - legal host name IP connection
- - "ILLEGAL_SOCKET" Not an IP socket
- - "NOT_IP" Not a socket
-
-RSCSI Security hints:
-
-- Do not generally allow other users to see your boot disk via RSCSI.
- All people who see this disk may edit your passwd file.
-
-- If you are in doubt, only export CD-ROM drives, scanners and similar
- devices that are not directly security sensitive.
-
-If anybody sees a security hole in my security precautions, please send me a mail!
-
-RSCSI usage:
-
-- To use remote SCSI devices you need to know how to access a specific remote
- SCSI target.
-
- - dev=REMOTE:host: or dev=REMOTE:host
- will allow you to do SCSI bus scanning while you log in as yourself
-
- - dev=REMOTE:user at host: or dev=REMOTE:user at host
- will allow you to do SCSI bus scanning while you log in as "user"
-
- If you use the setup described above, you should use:
-
- dev=REMOTE:rscsi at babbel:
-
- to do SCSI Bus scanning on host babbel
-
- - To access a specific SCSI device, you must specify
- dev=REMOTE:host:<target spec> or dev=REMOTE:user at host:<target spec>
- <target spec> is the SCSI target specification as it is needed
- on the remote host
-
- dev=REMOTE:rscsi at babbel:1,3,0
-
- Will let you log in as rscsi on host babbel and open Target 3 lun 0
- on SCSI bus #1
-
- - If you use wodim -vv ...., wodim will on startup print some
- information about the remote libscg version used for the connection.
-
-- To be able to use the remote SCSI client code from win32 you need to create
- a file /etc/passwd with a correct entry for the user you are on win32.
- Call 'id' to get the right user id.
- Note that remote SCSI has not yet been tested on Win32.
-
-RSCSI speed:
-
-- On a Ultra-10 running Solaris 8, the command overhead time is 400 usec.
- You may achieve up to 9900 kB/s via a 100MB/s ethernet connection
- between two of such machines.
-
-- With 100 MB/s, 12x recording should be no problem.
-
-- With 10 MB/s, 4x recording is the maximum. Do tests before!
-
-- Logging into a remote machine and running wodim on the remote machine
- causes the buffer cache on that machine to be trashed. The main user
- is disturbed.
-
-- Doing cdrecording via Remote SCSI causes only the rscsi command with less
- than 200kB to be needed on the remote machine hosting the CD recorder.
- The main user on that machine is not disturbed.
- The buffer cache of the machine running wodim is trashed.
-
-- It is desirable to use a Burn-Proof recorder to make sure that network
- load will not cause buffer underruns.
-
-
-- USER= test and test for hostname are using a pattern matcher.
Modified: cdrkit/trunk/doc/READMEs/README.sony
===================================================================
--- cdrkit/trunk/doc/READMEs/README.sony 2006-11-23 19:44:13 UTC (rev 439)
+++ cdrkit/trunk/doc/READMEs/README.sony 2006-11-23 19:55:19 UTC (rev 440)
@@ -5,14 +5,14 @@
If you have a Sony drive that gives you problems with multi session disks,
please always check the following:
- For some Sony drives you may need to call cdrecord -multi -data
+ For some Sony drives you may need to call wodim -multi -data
if you like to create multi-session CD's.
Some Sony drives do not allow to write XA2 tracks with
hardware support of the drive.
There is currently a bug in the Sony code (for _old_ non MMC drives)
-of cdrecord that does not allow you to have different track types
+of wodim that does not allow you to have different track types
in one session.
All Sony drives that have CDUxxx type names are _old_ non MMC drives.
@@ -24,6 +24,8 @@
NOTE: many HP CD-writers are nased on Sony OEM drives.
-NOTE: As for 18.5.2001, a fix was introduced that prevented cdrecord
+NOTE: As for 18.5.2001, a fix was introduced that prevented wodim
to do multi session with new MMC compliant Sony drives.
+---
+Eduard Bloch, based on documentation from Joerg Schilling, cdrtools package 2.01.01a08
More information about the Debburn-changes
mailing list