diff options
Diffstat (limited to 'doc/plattforms')
| -rw-r--r-- | doc/plattforms/README.aix5l | 16 | ||||
| -rw-r--r-- | doc/plattforms/README.freebsd | 31 | ||||
| -rw-r--r-- | doc/plattforms/README.linux | 46 | ||||
| -rw-r--r-- | doc/plattforms/README.parallel | 59 | ||||
| -rw-r--r-- | doc/plattforms/README.sunos | 10 | ||||
| -rw-r--r-- | doc/plattforms/README.win32 | 31 |
6 files changed, 193 insertions, 0 deletions
diff --git a/doc/plattforms/README.aix5l b/doc/plattforms/README.aix5l new file mode 100644 index 0000000..8c697d7 --- /dev/null +++ b/doc/plattforms/README.aix5l @@ -0,0 +1,16 @@ +Cdrkit can be built on AIX 5 using the following instructions. Note that the +SCSI transport has not been tested yet because of missing hardware. + + - install cmake either from source or from binaries downloadable on cmake.org. + Make sure the cmake is in your PATH and it can find its modules. + - GCC compiler (available on gcc.org) is recommended, however the native xlc + compiler should work as well. + +Follow instructions from the INSTALL file. + +If you installed a local version of GNU libiconv and ld is confused and spews +linking errors related to .libiconv, check the linker paths with +"cmake -LA build | grep lib". Probably your local path is not listed there and +you may need to set LDFLAGS make variable. See INSTALL file for details. + + -- Eduard Bloch -- Sun, 26 Nov 2006 23:06:25 +0100 diff --git a/doc/plattforms/README.freebsd b/doc/plattforms/README.freebsd new file mode 100644 index 0000000..6e51a30 --- /dev/null +++ b/doc/plattforms/README.freebsd @@ -0,0 +1,31 @@ +These instructions have been tested with FreeBSD 6.2-PRERELEASE, but +should work on any 6.x release. If you're having trouble (with any +release, not just 6.x), please let us know. + +Building +======== + +You need to have cmake installed. It is available in the ports +collection or from cmake.org. You also need GNU make. It is also in the +ports collection, and can be alternatively obtained from gnu.org. + +Most users have libiconv installed under /usr/local. If you wish to add +support for it (used by genisoimage, and recommended), build with + + gmake CFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib + +instead of just plain + + gmake + +Short note on using wodim +========================= + +If you want to use wodim with ATAPI drives, make sure you load the +atapicam module before using wodim. Not even "wodim -scanbus" works +usually if this is not done. The command for loading the atapicam +module is (for root) + + /sbin/kldload atapicam + + -- Lorenz Minder -- Mon Nov 27 23:23:01 CET 2006 diff --git a/doc/plattforms/README.linux b/doc/plattforms/README.linux new file mode 100644 index 0000000..da8f759 --- /dev/null +++ b/doc/plattforms/README.linux @@ -0,0 +1,46 @@ + +Requirements of cdrkit on Linux: + + - Linux kernel 2.4 or newer + - Glibc 2.2 or newer + - libcap library package is required, with development files (headers) + - kernel headers useable with the combination of glibc and kernel, as approved + by the distribution. Do not blindly use random kernel headers, do not + symlink them to /usr/include/linux or /usr/include/asm*. + +Notes about support on Linux: + + - Linux kernel versions between 2.6.8 and 2.6.11 are known to have invasive + SCSI command filtering which makes the use of wodim almost inpossible or + complicated for non-root users. Avoid those kernel versions, unless they + have been patched to disable that filtering. + + - support of generic scsi was limited on 2.4, ie. not available directly with + IDE/ATAPI devices. The ide-scsi driver could be used map ATAPI devices to + SCSI ids, however this driver had other problems. See README.ATAPI for + details. Note that there also the ATAPI:... device access method which uses + deprecated funtionality of kernel 2.4. Don't use it unless it is really + neccessary. The support for it may be removed in future versions of cdrkit. + + - the DMA transfer size is limited with some device controllers and the Linux + kernel 2.6.x (2.6.19 currently) provides no method to retrieve it for + exactly one device. Wodim scans sysfs to retrieve this information, but it + needs to be mounted. Use the ts= option of wodim to limit the transfer size + on problems. + + +Additional comments moved from the wodim.1 manpage (originaly cdrecord.1): + +The sg driver on Linux has several severe bugs: + + - It cannot see if a SCSI command could not be sent at all. + - It cannot get the SCSI status byte. wodim for that reason cannot report + failing SCSI commands in some situations. + - It cannot get real DMA count of transfer. wodim cannot tell you if there is + an DMA residual count. + - It cannot get number of bytes valid in auto sense data. wodim cannot tell + you if device transfers no sense data at all. + - It fetches too few data in auto request sense (CCS/SCSI-2/SCSI-3 needs + >= 18). + + -- Reviewed by Eduard Bloch -- 12/2006 diff --git a/doc/plattforms/README.parallel b/doc/plattforms/README.parallel new file mode 100644 index 0000000..22b9e09 --- /dev/null +++ b/doc/plattforms/README.parallel @@ -0,0 +1,59 @@ +This file is intended to help with ATAPI <-> Parallel Port devices on Linux + +Before you start, read + + http://www.torque.net/parport/paride.html + +Make sure that your parallel port device is set up to EPP mode +from within the BIOS. In many cases it is best to set the PP delay to 0. + +Here is a short explanation how to make the FreeCom Traveller work +in 4x speed on a notebook: + +1.) Set BIOS for parallel port to 'EPP'. + +2.) Load drivers in default mode: + + # modprobe paride + # modprobe <driver for parallel port adaptor> + # modprobe pg + +in case of a FreeCom Traveller this is: + + # modprobe paride + # modprobe friq + # modprobe pg + +3.) Check kernel log for paride messages: + + # dmesg + ... + paride: version 1.04 installed + paride: friq registered as protocol 0 + ... + parport0: PC-style at 0x378 [SPP,PS2,EPP] + parport0: no IEEE-1284 device present. + ... + pg: pg version 1.02, major 97 + pg0: Sharing parport0 at 0x378 + pg0: friq 1.01, Freecom IQ ASIC-2 adapter at 0x378, mode 4 (EPP-32), delay 1 + pg0: CD-R/RW RW8040A, master + ... + +4.) load module again but use different parameters: + 'drive0=IO-Port,Protocol,Unit,Mode,Master/Slave,Delay drive1=...' + if you have only one drive at the parallel port + 'drive0=IO-Port,0,0,-1,-1,Delay' e.g. for Delay = 0: + + # modprobe -r pg + # modprobe pg drive0=0x378,0,0,-1,-1,0 + +5.) Check for optimum delay using for maximum speed using wodim -dummy + +6.) Use the file rc.pp and modify for your needs + +7.) Your CD drive now appears as /dev/pcd? + +Source: README.cdtext from cdrtools package +Edited for cdrkit by Christian Fromme <kaner@strace.org> + diff --git a/doc/plattforms/README.sunos b/doc/plattforms/README.sunos new file mode 100644 index 0000000..6fc3a0d --- /dev/null +++ b/doc/plattforms/README.sunos @@ -0,0 +1,10 @@ + +Cdrkit have been built and partially tested on SunOS 5.8. + +To compile, run "gmake". CMake must be installed (with its modules), the cmake +binary must available in your path. Installing GNU libiconv is also recommended. + +On linking problems with 3rd-party libraries involved, make sure that you have +matching configuration of CFLAGS and LDFLAGS vars. + + -- Eduard Bloch -- Tue, 28 Nov 2006 00:01:47 +0100 diff --git a/doc/plattforms/README.win32 b/doc/plattforms/README.win32 new file mode 100644 index 0000000..1714ed6 --- /dev/null +++ b/doc/plattforms/README.win32 @@ -0,0 +1,31 @@ + +Cdrkit suite can be compiled on Windows XP (Service Pack 2) using cygwin +environment and tools set, available on: + + http://sources.redhat.com/cygwin/ + +and many mirrors. + +To compile on Cygwin, execute setup.exe to install it. You will need to select +cmake, make, libiconv and gcc compiler in the package selection. Also choose +subversion if you wish to fetch the latest development version. + +When done, you can start the Cygwin Shell by the new icon in the Start menu or +on the desktop. Visit cdrkit.org and download a tarball of a recent version and store it under <cygwin_directory>\home\your_user_name. + +Untar the package with tar -z -x -f <tarball>, go into this directory and run +"make", followed by "make install". Ignore messages about clock skew etc. + +NOTE: with some versions of Cygwin or cmake shipped with it, the installation +fails for unknown reason. In this case, you can browse trough the build/ +directory, pick up the .exe files there and read the manpage files in +application directories with the man command ("man wodim/wodim.1"). + +Windows drives are available in paths like /cygdrive/c/, /cygdrive/d/. The +drive IDs can be detected using "wodim -scanbus". See wodim's manpage for +details. + +STANDARD WARNING: test in dummy mode before you really write data to the disks. +Report trouble to Cdrkit maintainers. + + -- Eduard Bloch <blade@debian.org> -- Tue, 12 Sep 2006 10:06:34 +0200 |