For more information, see the README file in the directories

cdda2wav cdrecord mkisofs and in the directory "READMEs".

Or check other directories for README files.

For CD-Recording please read the README.volmgt too.

It seems that some include files that are needed to compile
e.g. the SCSI transport stuff are only present if you install
the kernel building stuff.

If you have problems to compile because some include files are 
missing, look into /sys and verify if all files are present or
(if they are symlinks) point to present files.

There is no working mapping between the SCSI bus,target,lun
notation and device node names. To use a SCSI device, you need
to specify dev=devname:@,lun e.g. dev=/dev/rsr0a:@,0

Short overview for those who don't read manuals:

	Calling configure manually is outdated because this is a task of the
	makefile system.

	There is no 'configure', simply call 'make' on the top level
	directory.

	***** If this does not work for you, read the rest if this file   *****
	***** If you have any problem, also first read the topic specific *****
	***** README.* files (e.g. README.linux for Linux problems).	  *****

	All results in general will be placed into a directory named 
	OBJ/<arch-name>/ in the current projects leaf directory.

	You **need** either my "smake" program, the SunPRO make 
	from /usr/bin/make (SunOS 4.x) or /usr/ccs/bin/make (SunOS 5.x)
	or GNU make to compile this program. Read READMEs/README.gmake for 
	more information on gmake and a list of the most annoying bugs in gmake.

	All other make programs are either not smart enough or have bugs.

	My "smake" source is at:

	ftp://ftp.berlios.de/pub/smake/alpha/

	It is easy to compile and doesn't need a working make program
	on your machine. If you don't have a working "make" program on the
	machine where you like to compile "smake" read the file "BOOTSTRAP".

	If you have the choice between all three make programs, the
	preference would be 

		1)	smake		(preferred)
		2)	SunPRO make
		3)	GNU make	(this is the last resort)

	Important notice: "smake" that comes with SGI/IRIX will not work!!!
	This is not the Schily "smake" but a dumb make program from SGI.

	***** If you are on a platform that is not yet known by the	 *****
	***** Schily makefilesystem you cannot use GNU make.		 *****
	***** In this case, the automake features of smake are required. *****

	Please read the README's for your operating system too.

			WARNING
	Do not use 'mc' to extract the tar file!
	All mc versions before 4.0.14 cannot extract symbolic links correctly.

	The versions of WinZip that support tar archives cannot be used too.
	The reason is that they don't support symbolic links.
	Star and Gnutar do support symbolic links even on win32 systems.
	To support symbolic links on win32, you need to link with the
	Cygwin32 POSIX library.

	To unpack an archive use:

		gzip -d < some-arch.tar.gz | tar -xpf -

	Replace 'star' by the actual archive name.

	If your Platform does not support hard links or symbolic links, you
	first need to compile "star" and then call:

		star -xpz -copy-links < some-arch.tar.gz

	If your platform does not support hard links but supports
	symbolic links, you only need to call the command above once.
	If your platform does not support symbolic links, you need to call
	the command twice because a symbolic link may occur in the archive
	before the file it points to.
		


Here comes the long form:


PREFACE:

	Calling configure manually is outdated because this is a task of the
	makefile system.

	You don't have to call configure with this make file system.

	Calling	'make' or 'make all' on the top level directory will create
	all needed targets. Calling 'make install' will install all needed
	files.

	This program uses a new makefilesystem. This makefilesystem uses
	techniques and ideas from the 1980s and 1990s, is designed in a
	modular way and allows sources to be combined in a modular way.
	For mor information on the modular features read README.SSPM.

	The makefilesystem is optimized for a program called 'smake'
	Copyright 1985 by Jrg Schilling, but SunPro make (the make program
	that comes with SunOS >= 4.0 and Solaris) as well as newer versions
	of GNU make will work also. BSDmake could be made working, if it
	supports pattern matching rules correctly.

	The makefile system allows simultaneous compilation on a wide
	variety of target systems if the source tree is accessible via NFS.


Finding Compilation Results:

	To allow this, all binaries and results of a 'compilation' in any form
	are placed in sub-directories. This includes automatically generated
	include files. Results in general will be placed into
	a directory named OBJ/<arch-name>/ in the current projects
	leaf directory, libraries will be placed into a directory called
	libs/<arch-name>/ that is located in the source tree root directory.

		<arch-name> will be something like 'sparc-sunos5-cc'

	This is the main reason why simultaneous compilation is possible on
	all supported platforms if the source is mounted via NFS.


How to compile:

	To compile a system or sub-system, simply enter 'smake', 'make' or 
	'Gmake'. Compilation may be initialized at any point of the source
	tree of a system. If compilation is started in a sub tree, all objects
	in that sub tree will be made.


How to install results:

	To install the product of a compilation in your system, call:

		smake install

	at top level. The binaries will usually be installed in 
	/opt/schily/bin. The directory /opt/<vendor-name>/ has been agreed
	on by all major UNIX vendors in 1989. Unfortunately, still not all
	vendors follow this agreement.

	If you want to change the default installation directory, edit the
	appropriate (system dependent) files in the DEFAULTS directory
	(e.g. DEFAULTS/Defaults.sunos5).

	***** If "smake install" doesn't do anything, you are on a broken *****
	***** File System. Remove the file INSTALL in this case (the FS   *****
	***** does not handle upper/lower case characters correctly).	  *****
	***** This is true for all DOS based filesystems and for Apple's  *****
	***** HFS+ filesystem.						  *****


Using a different installation directory:

	If your system does not yet use the standard installation path /opt
	or if you don't like this installation directory, you can easily 
	change the installation directory. You may edit the DEFAULTS file 
	for your system and modify the macro INS_BASE.

	You may  use a different installation directory without editing the
	DEFAULTS files. If you like to install everything in /usr/local, call:


	If your make program supports to propagate make macros to sub make programs
	which is the case for recent smake releases as well as for a recent gnumake:

		smake INS_BASE=/usr/local install
	or
		gmake INS_BASE=/usr/local install

	If you make program doesn't propagate make macros (e.g. SunPRO make) call:

		env INS_BASE=/usr/local make -e install

	Note that INS_BASE=/usr/local needs to be specified for every operation
	that compiles or links programs as the path is stored inside the
	binaries.


Installing to a prototype directory to implement package creation staging:

	If you like to create a prototype directory tree that is used as an
	intermediate store for package creation, use the DESTDIR macro:

		smake INS_BASE=/usr/local DESTDIR=/tmp install

	This will create a usr/local tree below /tmp (i.e. /tmp/usr/local).

Using a different C-compiler:

	If the configured default compiler is not present on the current machine,
	the makefilesystem will try an automatic fallback to GCC. For this reason
	in most cases you will not need to manually select a compiler.

	The default C-compiler can be modified in the files in the
	DEFAULT directory. If you want to have a different compiler
	for one compilation, call:

		make CCOM=gcc
	or
		make CCOM=cc

	This works even when your make program doesn't propagate make macros.


Creating 64 bit executables on Solaris:

	Simply call:

		make CCOM=gcc64
	or
		make CCOM=cc64

	It is not clear if GCC already supports other platforms in 64 bit mode.
	As all GCC versions before 3.1 did emit hundreds of compilation
	warnings related to 64 bit bugs when compiling itself, there is little
	hope that other platforms are already supported in 64 bit mode.

Creating executables using the Sun Studio compiler on Linux:

	Simply call:

		make CCOM=suncc

	If the compilation does not work, try:

	mkdir   /opt/sunstudio12/prod/include/cc/linux 
	cp      /usr/include/linux/types.h  /opt/sunstudio12/prod/include/cc/linux

	Then edit /opt/sunstudio12/prod/include/cc/linux/types.h and remove all
	lines like: "#if defined(__GNUC__) && !defined(__STRICT_ANSI__)"
	as well as the related #endif.



Getting help from make:

	For a list of targets call:

		make .help


Getting more information on the make file system:

	The man page makefiles.4 located in man/man4/makefiles.4 contains
	the documentation on general use and for leaf makefiles.

	The man page makerules.4 located in man/man4/makerules.4 contains
	the documentation for system programmers who want to modify
	the make rules of the makefile system.

	For further information read

		ftp://ftp.berlios.de/pub/makefiles/PortableSoftware.ps.gz


Hints for compilation:

	The makefile system is optimized for 'smake'. Smake will give the
	fastest processing and best debugging output.

	SunPro make will work as is. GNU make need some special preparation.

	Read READMEs/README.gmake for more information on gmake.

	To use GNU make create a file called 'Gmake' in your search path
	that contains:

		#!/bin/sh
		MAKEPROG=gmake
		export MAKEPROG
		exec gmake "$@"

	and call 'Gmake' instead of gmake. On Linux there is no gmake, 'make'
	on Linux is really a gmake.

	'Gmake' and 'Gmake.linux' are part of this distribution.

	Some versions of gmake are very buggy. There are e.g. versions of gmake
	on some architectures that will not correctly recognize the default
	target. In this case call 'make all' or ../Gmake all'.

	Note that pseudo error messages from gmake similar to:

	gmake[1]: Entering directory `cdrtools-1.10/conf'
	../RULES/rules.cnf:58: ../incs/sparc-sunos5-cc/Inull: No such file or directory
	../RULES/rules.cnf:59: ../incs/sparc-sunos5-cc/rules.cnf: No such file or directory

	Are a result of a bug un GNU make. The make file system itself is
	correct (as you could prove by using smake).
	If your gmake version still has this bug, send a bug report to:

		"Paul D. Smith" <psmith (a] gnu.org>

	He is the current GNU make maintainer.

	If you like to use 'smake', please always compile it from source.
	The packages are located on:

		ftp://ftp.berlios.de/pub/smake/alpha/

	Smake has a -D flag to see the actual makefile source used
	and a -d flag that gives easy to read debugging info. Use smake -xM
	to get a makefile dependency list. Try smake -help


Compiling the project using engineering defaults:

	The defaults found in the directory DEFAULTS are configured to
	give minimum warnings. This is made because many people will
	be irritated by warning messages and because the GNU c-compiler
	will give warnings for perfectly correct and portable c-code.

	If you want to port code to new platforms or do engineering
	on the code, you should use the alternate set of defaults found
	in the directory DEFAULTS_ENG.
	You may do this permanently by renaming the directories or
	for one compilation by calling:

		make DEFAULTSDIR=DEFAULTS_ENG


Compiling the project to allow debugging with dbx/gdb:

	If you like to compile with debugging information for dbx or gdb,
	call:

		make clean
		make COPTX=-g LDOPTX=-g


Creting Blastwave packages:

	Call:
		.clean
		smake -f Mcsw

	You need the program "fakeroot" and will find the results
	in packages/<arch-dir>

	Note that a single program source tree will allow you to create
	packages like CSWstar but not the packages CSWschilybase and
	CSWschilyutils on which CSWstar depends.




	If you want to see an example, please have a look at the "star"
	source. It may be found on:

		ftp://ftp.berlios.de/pub/star

	Have a look at the manual page, it is included in the distribution.
	Install the manual page with 

	make install first and include /opt/schily/man in your MANPATH

	Note that some systems (e.g. Solaris 2.x) require you either to call
	/usr/lib/makewhatis /opt/schily/man or to call 

		man -F <man-page-name>


Author:

Joerg Schilling
Seestr. 110
D-13353 Berlin
Germany

Email: 	joerg (a] schily.isdn.cs.tu-berlin.de, js (a] cs.tu-berlin.de
	joerg.schilling (a] fokus.fraunhufer.de

Please mail bugs and suggestions to me.

Important notice for ATAPI support on FreeBSD:

A long time it was not possible to decently write CD's using ATAPI drives
on FreeBSD because ATAPI was not supported in an orthogonal way on FreeBSD.

These days (in the mid of november 2001) first ATAPI support for FreeBSD is
available as patch. Please read:

http://www.freebsd.org/cgi/getmsg.cgi?fetch=136602+0+/usr/local/www/db/text/2001/freebsd-current/20011111.freebsd-current

and get the FreeBSD kernel patch from:

http://www.cuivre.fr.eu.org/~thomas/atapicam/

Thanks to Thomas Quinot <thomas (a] cuivre.fr.eu.org> for the patch.

We tested the patch with a collegue today (23.11.2001), here is the result:

-	From our tests, it compiles with FreeBSD 4.x and FreeBSD current (5.0)
	but does not boot with FreeBSD current so we used 4.x for our tests
	I hope that Thomas Quinot <thomas (a] cuivre.fr.eu.org> and
	Kenneth D. Merry <ken (a] kdm.org> will help to make it work with
	FreeBSD current soon.

-	The Author of the patch, Thomas Quinot <thomas (a] cuivre.fr.eu.org>, observed
	that it runs on *some* -CURRENT machines and hangs on *some* -STABLE
	machines so you may want to test what works best for you.

-	It does not run the SCSI commands in silent mode so the ATAPI low level
	code prints unwanted kernel messages when you start cdrecord.

-	cdrecord runs without problems so far it has been tested!

You need to apply the patch, change your kernel configuration to include

options                ATAPICAM

and then recompile install and boot the new kernel.
Make enough /dev/pass* devices and start testing.....

/*--------------------------------------------------------------------------*/
From shamrock (a] cypherpunks.to Mon May  3 07:35:50 1999
Received: from pakastelohi.cypherpunks.to (pakastelohi.cypherpunks.to [212.26.192.194])
	by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id HAA18680
	for <schilling (a] fokus.gmd.de>; Mon, 3 May 1999 07:35:48 +0200 (MET DST)
Received: from localhost (shamrock@localhost)
	by pakastelohi.cypherpunks.to (8.9.1a/8.9.1) with SMTP id HAA26150
	for <schilling (a] fokus.gmd.de>; Mon, 3 May 1999 07:35:44 +0200 (CEST)
Date: Mon, 3 May 1999 07:35:44 +0200 (CEST)
From: Lucky Green <shamrock (a] cypherpunks.to>
To: schilling (a] fokus.gmd.de
Subject: Re: Cdrecord "RR-scheduler not available" (fwd)
Message-ID: <Pine.BSF.3.96.990503073330.26028A-100000 (a] pakastelohi.cypherpunks.to>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Status: R
Content-Length: 1423

Schily,
Please add the following info to your readme for FreeBSD. Enabling POSIX
scheduling as described below does in fact make the error message go away.

Thanks,
-- Lucky Green <shamrock (a] cypherpunks.to> PGP v5 encrypted email preferred.

---------- Forwarded message ----------
Date: Sun, 2 May 1999 14:46:57 +0200 (SAT)
From: Khetan Gajjar <khetan (a] link.freebsd.os.org.za>
Reply-To: Khetan Gajjar <khetan (a] os.org.za>
To: Lucky Green <shamrock (a] adsl.cypherpunks.to>
Cc: freebsd-questions (a] FreeBSD.ORG
Subject: Re: Cdrecord "RR-scheduler not available"

On Sat, 1 May 1999, Lucky Green wrote:

>Having spent a week on trying to get an ATAPI CD burner working, I saw the
>light and purchased a SCSI-based burner. It burns, but I am getting an
>error about the RR-scheduler not being available. What is an RR-scheduler
>and how do I make it available? (If I even need it....)

Enable the Posix scheduling stuff in your kernel; you'll produce
more reliable burns at higher speeds if your machine is busy
(well, that's been my experience)

options         "P1003_1B"
options         "_KPOSIX_PRIORITY_SCHEDULING"
options         "_KPOSIX_VERSION=199309L"
--- 
Khetan Gajjar       (!kg1779) * khetan (a] iafrica.com ; khetan (a] os.org.za
http://www.os.org.za/~khetan  * Talk/Finger khetan (a] chain.freebsd.os.org.za
FreeBSD enthusiast            * http://www2.za.freebsd.org/
Security-wise, NT is a OS with a "kick me" sign taped to it  

System V IPC
CONFIG_SYSVIPC
  Inter Process Communication is a suite of library functions and
  system calls which let processes (running programs) synchronize and
  exchange information. It is generally considered to be a good thing,
  and some programs won't run unless you say Y here. In particular, if
  you want to run the DOS emulator dosemu under Linux (read the
  DOSEMU-HOWTO, available from
  http://www.linuxdoc.org/docs.html#howto ), you'll need to say Y
  here.
 
  You can find documentation about IPC with "info ipc" and also in
  section 6.4 of the Linux Programmer's Guide, available from
  http://www.linuxdoc.org/docs.html#guide .
 
  Shared memory is now implemented using a new (minimal) virtual file
  system, which you need to mount before programs can use shared memory.
  To do this automatically at system startup just add the following line
  to your /etc/fstab:
 
  none  /var/shm        shm     defaults        0 0
 
  Saying Y here enlarges your kernel by about 18 KB. Just say Y.

Cdrtools carries is the official version of mkisofs.

To compile mkisofs correctly on all supported platforms (> 30) you
need to use the Schily makefilesystem to get the systematic portability
support.

Read the file README.multi to learn how to create multi-session
CD-R's with this release of cdrecord and mkisofs.

Read the file README.cdplus to learn how to create CD-plus/CD-extra
CD-R's with this release of cdrecord and mkisofs.

You definitely need this release of mkisofs to 
create multi-session CD-R's on SunOS/Solaris/SGI-IRIX OS/2 and Win32.

Jrg Schilling

NOTE: you should also read README.xxxBSD

Cdrecord now supports ATAPI drives on NetBSD

The sparc hostadapter driver software in NetBSD has a bug:

An internal copy of the SCSI status byte will never be updated.
However, this internal copy is always returned so the 
SCSI library always believes that an error occurred.

As this implementation bug makes it impossible to sense
other error/exception conditions the driver needs to be fixed.

As a workaround you can activate a hack in the file scsi-bsd.c
by using

./Gmake COPTX=-DBSD_SCSI_SENSE_BUG

to compile cdrecord

Jrg

For CD-Recording please read the README.volmgt too.

On OpenBSD releases between December 11th and December 30th 2002
there is a bug in /usr/include/ctype.h, it #defines EOF ignoring
POSIX rules. As the schily make environment relies on EOF as an
indicator to check whether stdio.h has been included, there may 
be problems to compile things. If you find compile problems,
you may try to include 

#undef EOF 

directly after #include <ctype.h>

Cdrecord has been tested and known to work on OpenBSD, however,
the current OpenBSD port will not be able to scan the SCSI bus
for a CD-Recorder as it does on other operating systems.

In other words, 'cdrecord -scanbus' most likely will not work.

Both regular SCSI and ATAPI devices are supported. For ATAPI support
you need OpenBSD-2.6 or newer.

Libscg sends Generic scsi commands that are only supported for the
"whole disk" partition.  For example, 'cdrecord dev=/dev/rcd0c -checkdrive'.
See the cd(4), atapiscsi(4), and cdrecord(1) manpages for more details.

There are at least two ways to figure out what SCSI CD devices are
on the machine:

  From /var/run/dmesg.boot:
  $ egrep "^cd.+ at scsibus" /var/run/dmesg.boot
  cd0 at scsibus0 targ 0 lun 0: <SONY, CD-RW CRX175E2, S002> SCSI0 5/cdrom removable
  cd1 at scsibus1 targ 0 lun 0: <ATAPI, CD-ROM MARY500, 1.21> SCSI0 5/cdrom removable

  From sysctl:
  $ sysctl hw.disknames
  hw.disknames = wd0,cd0,cd1,fd0

In these examples, 'cd0' and 'cd1' are the SCSI CD devices on the
system, and they should be accessed by '/dev/rcd0c' and '/dev/rcd1c',
respectively.

In December 2002 there have been reports that the atapiscsi(4) driver has
some bugs that may cause cdrecord to hang for a while.  While this is
annoying, it is harmless. The command will eventually timeout (the default
timeout is 40 seconds, but can be changed with timeout=%d).  Trying to kill
the "hung" process may leave the device unusable until the system is rebooted
(which would be another bug of the atapiscsi(4) driver as killing a process
should do all necessary housekeeping for the dead process), so just be patient.

CDRTOOLS compiles without changes on any SCO OpenServer 5.0.4
or later installation having the SCO DevSys or GCC-2.95 and 
smake-1.2a04 or later installed. 

You can get pre-packaged, custom installable binaries from:
 
   http://www.sco.com/skunkware/cdrtools
   
Some general notes on CDRTOOLS are available from:

   http://www.sco.com/skunkware/cdrtools/SCO-NOTES.html


Limitations for CDRTOOLS-1.8 on SCO OpenServer 5:

1) SCO OpenServer 5.0.0 and 5.0.2 are unsupported!
  
2) There is only support for SCSI devices

3) There no support for AHA 154X scsi controllers

===================================================================
NOTE: cdrecord now supports the -scanbus option. Therefore the 
      old addressing methods are NO LONGER AVAILABLE !!!
===================================================================
      
As there is no real generic SCSI driver, cdrecord uses the pass through
ioctl of the cdrom target driver (Srom).

The correct dev= syntax on SCO Openserver 5 is:

    dev=scsibus,target,lun	(and scsibus is scsibus now!!!)

A sample output from cdrecord -scanbus looks like:

#cdrecord -scanbus
Cdrecord 1.8 (i686-pc-sco3.2v5.0.5) Copyright (C) 1995-2000 Jrg Schilling
Using libscg version 'schily-0.1'
scsibus0:
        0,0,0     0) 'SEAGATE ' 'ST34573LC       ' '5960' Disk
        0,1,0     1) 'SEAGATE ' 'ST34573LC       ' '5960' Disk
        0,2,0     2) 'SEAGATE ' 'ST34573LC       ' '5960' Disk
        0,3,0     3) *
        0,4,0     4) *
        0,5,0     5) 'PIONEER ' 'CD-ROM DR-U06S  ' '1.05' Removable CD-ROM
        0,6,0     6) 'TEAC    ' 'CD-R56S         ' '1.0E' Removable CD-ROM
        0,7,0     7) *

The first column showing the triple x,y,z tells you the address to use.

As you can see the TEAC CD-R56S CD-Writer does have the following address:

     dev=0,6,0
     
===================================================================
           THE OLD ADDRESSING IS NO LONGER AVAILABLE!
	    
         PLEASE ADJUST YOUR /etc/default/cdrecord FILES!
===================================================================

Running cdrecord with the old address method will result in an error!

#cdrecord dev=/dev/rcd1:6,0 -inq
Cdrecord 1.8 (i386-pc-sco3.2v5.0.5) Copyright (C) 1995-2000 Jrg Schilling
scsidev: '/dev/rcd1:6,0'
devname: '/dev/rcd1'
scsibus: 0 target: 6 lun: 0
cdrecord: Invalid argument. Open by 'devname' no longer supported on this OS. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.


MAKE SURE YOU HAVE MEDIA IN YOUR CD-ROM DEVICES, SO THAT CDRECORD CAN 
OPEN THE DEVICE FOR PASS-THROUGH ACCESS!


To compile cdrtools, you need 'smake' version 1.2a04 or later from:

   ftp://ftp.sco.com/skunkware/osr5/vols


Please make sure you use smake-1.2a04 or later, cause smake-1.2 versions
before a04 will coredump on the compilation of cdrtools on OpenServer.

Compiling on OS/2:

1)	Install EMX

2)	You need /bin/sh, /bin/rm, /bin/mv

	Create a directory /bin and put /bin/sh into this directory
	mkdir /bin
	cp -p d:/emx/bin/sh.exe /bin
	cp -p d:/emx/bin/rm.exe /bin
	cp -p d:/emx/bin/mv.exe /bin




/*--------------------------------------------------------------------------*/
Note that the Joliet implementation on OS/2 is buggy:

It expects the file in the directories in the wrong order.
While Microsoft wants the files to be in ASCII (binary) order,
OS/2 likes to have the files in lexical order (uppercase and
lowercase together). This makes CD's with Joliet attributes
unreadable on OS/2 if there are files that start the same way
but differ in case.
/*--------------------------------------------------------------------------*/

To compile on QNX you will need smake-1.2a3 or later.
It looks like GNUmake has a bug that prevents a compilation
using GNUmake.

On IRIX there is a program from SGI which is called 'smake' too.
Be sure to call the Schily smake when compiling. The IRIX smake
is too dumb.

SGI apearantly has a bug in its mlock*() implementation.

This shows up as a total system freeze for approx. 60 sec at the startup of cdrecord
if cdrecord uses the FIFO.

It can be fixed by:

-	IRIX 6.2: applying patches  (see  freeware.sgi.com/Installable/cdrecord-1.8.html)

-	IRIX 6.5: Using 6.5.7m or above.

/*--------------------------------------------------------------------------*/
Note:	IRIX 6.2 requires the latest rollup patches for mlockall and for
	POSIX 1003.1b scheduling (patches 3771 and 3704 or their successors).
/*--------------------------------------------------------------------------*/

I am using my SCSI library, you don't need to link the program with -lds

This cdrecord distribution contains a mkisofs that runs on SGI
and allows you th read a filesystem from a CD-R device with 2048 bytes 
sector size. This is done with the SCSI user level library.


*** Important: IRIX has problems with drives that do disconnects on the SCSI
after an odd number of transferred bytes. It seems that there is a patch for this
problem. Search google for "wd93" to find pointers.

     A new milestone in modular portable programming is ready!

The "Slottable Source Plugin Module" system (SSPM) is an idea that
really is more than 3 years old but I was hesitating to announce it
earlier. Now I can tell you that the new makefile system has been
under test during the last 6 months and nobody complained about any 
problem caused by the SSPM.

The portability overhead is currently about 2 MB. This turns a medium
sized application like 'star' which is about 500 kB of pure source
into a packet that is 5x as big as the pure source size.

As all my applications are based on the Schily SING makefile system
and share a common portability base it makes sense to share the
advantages of the Schily makefile system with all users.

Simple ideas like the SSPM are usually hard to understand by people
from outside, so I try to describe the new system by giving you an
example on how it is used:

--------------------
You may test the new system by first downloading the latest
cdrtools package 

	ftp://ftp.berlios.de/pub/cdrecord/alpha/cdrtools-1.11a11.tar.gz

or newer. Then unpack the source tarball, chdir into the top level
directory of the cdrtools package. Run 'make' and wait until the 
compilation has finished.

So far, there is nothing new (except that some people may recognize
that this is a 'smooth' fully integrated compilation and you don't need
to call 'configure'.

Now, to understand what a "Slottable Source Plugin Module" is, fetch
another source. There is currently only one demo source that is ready
for testing:

	ftp://ftp.berlios.de/pub/star/alpha/star-1.4a08-sspm.tar.gz

Unpack this tarball in the top level directory of cdrtools and
call 'make' again. The Schily makefile system does recognize that there
is additional (uncompiled) source and will compile these new parts.
As there is no need to run 'configure' again, compilation of the 
additional 'star' sources is much faster than the compilation of the
complete 'star' source package would take.

To understand how the "Slottable Source Plugin Module" system works,
have a look into the TARGETS directory.....

-------------------

CDRTOOLS compiles without changes on any UnixWare 7.0.1 or later installation 
having the UnixWare/OpenServer DevKit (UODK) or GCC-2.95 and smake-1.2 
installed.

You can get pre-packaged, pkgadd installable binaries from:
 
   http://www.sco.com/skunkware/cdrtools
   
Some general notes on CDRTOOLS are available from:

   http://www.sco.com/skunkware/cdrtools/SCO-NOTES.html


Limitations for CDRTOOLS-1.8 on UnixWare:

1) SCO UnixWare 2.1.X and UnixWare 7.0.0 are not supported
   - UW2.1.X will compile/work with little changes
   - UW7.0.0 wasn't tested at all 

2) There is only support for SCSI devices

3) UnixWare 7.0.1 requires additional PTF's to enable some
   host bus adapters to work with a logical block size of more than
   512 bytes. (Please see the above SCO_NOTES document for details!)

===================================================================
NOTE: cdrecord now supports the -scanbus option. Therefore the 
      old addressing methods are NO LONGER AVAILABLE !!!
      
      As UnixWare 7.1.1 doesn't allow to open the passthrough
      interface for disks, this is disabled by default. 
      cdrecord -scanbus will therefore only list devices other
      than disks. To enable the scanning of disks, you need to
      set an environment variable "LIBSCG_SCAN_ALL".
      
      Be warned, doing so might lock your disk subsystem!
===================================================================

The correct dev= syntax on UnixWare 7 is:

    dev=scsibus,target,lun	(and scsibus is scsibus now!!!)

A sample output from cdrecord -scanbus looks like:

#cdrecord -scanbus
Cdrecord 1.8 (i586-sco-sysv5uw7.0.1) Copyright (C) 1995-2000 Jrg Schilling
Using libscg version 'schily-0.1'
scsibus0:
        0,0,0     0) 'SEAGATE ' 'ST34573LC       ' '5960' Disk
        0,1,0     1) 'SEAGATE ' 'ST34573LC       ' '5960' Disk
        0,2,0     2) 'SEAGATE ' 'ST34573LC       ' '5960' Disk
        0,3,0     3) *
        0,4,0     4) *
        0,5,0     5) 'PIONEER ' 'CD-ROM DR-U06S  ' '1.05' Removable CD-ROM
        0,6,0     6) 'TEAC    ' 'CD-R56S         ' '1.0E' Removable CD-ROM
        0,7,0     7) *

The first column showing the triple x,y,z tells you the address to use.

As you can see the TEAC CD-R56S CD-Writer does have the following address:

     dev=0,6,0
     
===================================================================
           THE OLD ADDRESSING IS NO LONGER AVAILABLE!
	    
         PLEASE ADJUST YOUR /etc/default/cdrecord FILES!
===================================================================

Running cdrecord with the old address method will result in an error!

#cdrecord dev=/dev/rcdrom/cdrom1:6,0 -inq
Cdrecord 1.8 (i386-pc-sco3.2v5.0.5) Copyright (C) 1995-2000 Jrg Schilling
scsidev: '/dev/rcd1:6,0'
devname: '/dev/rcd1'
scsibus: 0 target: 6 lun: 0
cdrecord: Invalid argument. Open by 'devname' no longer supported on this OS. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.


To compile cdrtools, you need 'smake' from:

   ftp://ftp.sco.com/skunkware/uw7/Packages


or 'gmake'. Smake is preferred as gmake bugs will cause bogus warnings
and may confuse about the state of the make run.

This README was written by Dr. Eberhard Heuser-Hofmann
	vaxinf (a] chclu.chemie.uni-konstanz.de

If you are looking for a *.zip file instead of the tar archive,
check this address:

ftp://v36.chemie.uni-konstanz.de/cdrecord_vms/
 
/*--------------------------------------------------------------------------*/
Hi,

this is the OpenVMS Version of J.Schilling's cdrecord-program.

There is a command-procedure called build_all.com in the [.cdrecord] subdir,
that compiles and links the code. The cdrecord-program is been produced in
[.cdrecord.vms] subdirectory.

Define this program as a symbol via

$ cdrecord:==$disk:[dir]cdrecord.exe

$ cdrecord -help gives an idea about the options, that are possible:

cdrecord -help
Usage: cdrecord.exe [options] track1...trackn
Options:
        -version        print version information and exit
        dev=target      SCSI target to use as CD/DVD-Recorder
        gracetime=#     set the grace time before starting to write to #.
        timeout=#       set the default SCSI command timeout to #.
        debug=#,-d      Set to # or increment misc debug level
        kdebug=#,kd=#   do Kernel debugging
        -verbose,-v     increment general verbose level by one
        -Verbose,-V     increment SCSI command transport verbose level by one
        -silent,-s      do not print status of failed SCSI commands
        driver=name     user supplied driver name, use with extreme care
        driveropts=opt  a comma separated list of driver specific options
        -checkdrive     check if a driver for the drive is present
        -prcap          print drive capabilities for MMC compliant drives
        -inq            do an inquiry for the drive and exit
        -scanbus        scan the SCSI bus and exit
        -reset          reset the SCSI bus with the cdrecorder (if possible)
        -overburn       allow to write more than the official size of a medium
        -ignsize        ignore the known size of a medium (may cause problems)
        -useinfo        use *.inf files to overwrite audio options.
        speed=#         set speed of drive
        blank=type      blank a CD-RW disc (see blank=help)
        -load           load the disk and exit (works only with tray loader)
        -eject          eject the disk after doing the work
        -dummy          do everything with laser turned off
        -msinfo         retrieve multi-session info for mkisofs >= 1.10
        -toc            retrieve and print TOC/PMA data
        -atip           retrieve and print ATIP data
        -multi          generate a TOC that allows multi session
                        In this case default track type is CD-ROM XA2
        -fix            fixate a corrupt or unfixated disk (generate a TOC)
        -nofix          do not fixate disk after writing tracks
        -waiti          wait until input is available before opening SCSI
        -immed          Try to use the SCSI IMMED flag with certain long lasting commands
        -force          force to continue on some errors to allow blanking bad disks
        -dao            Write disk in SAO mode. This option will be replaced in the future.
        -raw            Write disk in RAW mode. This option will be replaced in the future.
        -raw96r         Write disk in RAW/RAW96R mode. This option will be replaced in the future.
        -raw96p         Write disk in RAW/RAW96P mode. This option will be replaced in the future.
        -raw16          Write disk in RAW/RAW16 mode. This option will be replaced in the future.
        tsize=#         Length of valid data in next track
        padsize=#       Amount of padding for next track
        pregap=#        Amount of pre-gap sectors before next track
        defpregap=#     Amount of pre-gap sectors for all but track #1
        mcn=text        Set the media catalog number for this CD to 'text'
        isrc=text       Set the ISRC number for the next track to 'text'
        index=list      Set the index list for the next track to 'list'
        -text           Write CD-Text from information from *.inf files
        textfile=name   Set the file with CD-Text data to 'name'
        -audio          Subsequent tracks are CD-DA audio tracks
        -data           Subsequent tracks are CD-ROM data mode 1 (default)
        -mode2          Subsequent tracks are CD-ROM data mode 2
        -xa1            Subsequent tracks are CD-ROM XA mode 1
        -xa2            Subsequent tracks are CD-ROM XA mode 2
        -cdi            Subsequent tracks are CDI tracks
        -isosize        Use iso9660 file system size for next data track
        -preemp         Audio tracks are mastered with 50/15 s preemphasis
        -nopreemp       Audio tracks are mastered with no preemphasis (default)
        -copy           Audio tracks have unlimited copy permission
        -nocopy         Audio tracks may only be copied once for personal use (default)
        -scms           Audio tracks will not have any copy permission at all
        -pad            Pad data tracks with 15 zeroed sectors
                        Pad audio tracks to a multiple of 2352 bytes
        -nopad          Do not pad data tracks (default)
        -shorttrack     Subsequent tracks may be non Red Book < 4 seconds if in SAO or RAW mode
        -noshorttrack   Subsequent tracks must be >= 4 seconds
        -swab           Audio data source is byte-swapped (little-endian/Intel)
The type of the first track is used for the toc type.
Currently only form 1 tracks are supported.

One important point is how the CDR-device is being selected:

dev=i,j,k

where:
i: 0   1   2   3   4   5   6   7   8   9    ...  32  33
   dka dkb dkc dkd gka gkb gkc gkd dqa dqb  ...  dqy dqz

j: scsi-id
k: sub-lun (usually 0)

As an example:

dev=1,5,2 selects dkb502:

An typical example how to put virtual disk data onto a cd-rom is given here:

$ cdrecord -speed 2 dev=0,4,0 dka200:[000000]vda0.dsk

Additional hints:

1. Due to timeout problems use -immed switch for IDE-burners under OpenVMS 7.3
   or modify the timeout value in the dqdriver source.

2. HP has written a command procedure, that calls cdrecord. You should
   modify this com-file to activate the cdrecord burnproof option:
   "driveropts=burnproof".

Be aware that cdrecord has copyright on it.

Eberhard

===============================================================================

Dr. Eberhard Heuser-Hofmann
Univ. Konstanz
Fakultaet fuer Chemie
Universitaets-Strasse 10
D-78464 Konstanz
Germany
Phone: +49-7531-88-2026, FAX: +49-7531-88-3139
email: vaxinf (a] chclu.chemie.uni-konstanz.de

===============================================================================

The current *BSD port will not yet be able to scan the SCSI bus
for a CD-Recorder as it is on other architectures.

User level SCSI seems not be be well tested on *BSD

It would be nice if the kernel hackers of all *BSD flavors could agree in
adding decent and useful SCSI user land transport support.
This would cause the following changes:

	-	Add a driver that is present by default and offeres an
		easy to address interface to the /dev/ namespace.
	-	Create device file entries for this driver by default.
	-	allow to send all commands on this driver even if the main
		driver entry is in use, At least allow:
			INQUIRY
			TEST_UNIT_READY
			REQUEST_SENSE
		to be able to scan the SCSI bus for drives.

NOTE: This changed with FreeBSD/cam cdrecord -scanbus works on FreeBSD/cam

Workaround:

If /dev/su0-0-0 ... does not exist on your system, you may try
to create the devices with the MAKEDEV.su script below.

If /dev/su0-0-0 ... do not work on your system, you may try
use dev=/dev/rcd0a:@,0 od dev=/dev/rcd0a:@
If the CD-Recorder is on /dev/cd0a

Read the man page for more information.

There is no way to get the device node entry from the numerical target
specification on *BSD. You must specify the appropriate device node name:
e.g. dev=/dev/cd0.ctl:6,0 together with the numerical target specification.
A short form is:

	dev=/dev/cd0.ctl:@

But this syntax may not work on all *BSD flavours as not all *BSD flavours
support mapping back the target/lun numbers from a device.

In any case: read the cdrecord man page and try to find the /dev/* entry for
your CD-recorder that allows to be used with ioctl's.

On FreeBSD/cam, you will be able to access the CD-Recorder as on other
systems. If your CD-Recorder is on SCSI Bus 0, Target 2, lun 0
type:

cdrecord dev=0,2,0 .....

Jrg

------------------------- MAKEDEV.su------------------
#!/bin/sh

#
# You must check which minor base is really needed for your system
# The su driver seems not to be well tested on *BSD
#
# If nothing else helps, create a link /dev/scgx to the right
# /dev/ entry (an entry that responds right with /sbin/scsi)
# for your needed device.
#
minorbase="536870912 + 2"
#minorbase="0"
#minorbase="0 + 2"
#minorbase="0 + 3"

mknod /dev/su0-0-0 c 18 `expr $minorbase + 0 '*' 8`
mknod /dev/su0-1-0 c 18 `expr $minorbase + 1 '*' 8`
mknod /dev/su0-2-0 c 18 `expr $minorbase + 2 '*' 8`
mknod /dev/su0-3-0 c 18 `expr $minorbase + 3 '*' 8`
mknod /dev/su0-4-0 c 18 `expr $minorbase + 4 '*' 8`
mknod /dev/su0-5-0 c 18 `expr $minorbase + 5 '*' 8`
mknod /dev/su0-6-0 c 18 `expr $minorbase + 6 '*' 8`
mknod /dev/su0-7-0 c 18 `expr $minorbase + 7 '*' 8`

mknod /dev/su1-0-0 c 18 `expr $minorbase + 1 '*' 64 + 0 '*' 8`
mknod /dev/su1-1-0 c 18 `expr $minorbase + 1 '*' 64 + 1 '*' 8`
mknod /dev/su1-2-0 c 18 `expr $minorbase + 1 '*' 64 + 2 '*' 8`
mknod /dev/su1-3-0 c 18 `expr $minorbase + 1 '*' 64 + 3 '*' 8`
mknod /dev/su1-4-0 c 18 `expr $minorbase + 1 '*' 64 + 4 '*' 8`
mknod /dev/su1-5-0 c 18 `expr $minorbase + 1 '*' 64 + 5 '*' 8`
mknod /dev/su1-6-0 c 18 `expr $minorbase + 1 '*' 64 + 6 '*' 8`
mknod /dev/su1-7-0 c 18 `expr $minorbase + 1 '*' 64 + 7 '*' 8`

Indexes created Wed Nov 25 03:48:49 UTC 2009

Terms of Use | Privacy | Trademarks | Copyright Policy | Site Guidelines | Help
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Use.
Copyright © 1995-2008 Sun Microsystems, Inc.