Update OS section and note ISO 9660 library in the history part.
This commit is contained in:
@@ -46,7 +46,7 @@ development.''
|
|||||||
|
|
||||||
@titlepage
|
@titlepage
|
||||||
@title GNU libcdio library
|
@title GNU libcdio library
|
||||||
@subtitle $Id: libcdio.texi,v 1.28 2004/11/21 09:59:44 rocky Exp $
|
@subtitle $Id: libcdio.texi,v 1.29 2004/11/21 11:36:13 rocky Exp $
|
||||||
@author Rocky Bernstein et al.
|
@author Rocky Bernstein et al.
|
||||||
@page
|
@page
|
||||||
|
|
||||||
@@ -136,6 +136,9 @@ the library really doesn't handle writing or output (the final "o" in
|
|||||||
the name). However it was felt that if I put libcdi that might be
|
the name). However it was felt that if I put libcdi that might be
|
||||||
confused with a particular CD format called CD-I.
|
confused with a particular CD format called CD-I.
|
||||||
|
|
||||||
|
Later on, the ISO-9660 filesystem handling component from
|
||||||
|
@kbd{vcdimager} was extracted, expanded and made a separate library.
|
||||||
|
|
||||||
@node Previous Work
|
@node Previous Work
|
||||||
@chapter The problem and previous work
|
@chapter The problem and previous work
|
||||||
|
|
||||||
@@ -1367,21 +1370,29 @@ interface, and has taken steps to make using ASPI more inaccessible
|
|||||||
@node Solaris
|
@node Solaris
|
||||||
@section Solaris
|
@section Solaris
|
||||||
|
|
||||||
There are two CD drive access methods on Solaris:
|
There is currently only one CD drive access methods in Solaris: SCSI
|
||||||
ATAPI and SCSI. SCSI is preferred when possible.
|
(called ``USCI'' or ``user SCSI'' in Solaris). There used to be an
|
||||||
|
ATAPI method and it could be resurrected if needed. USCSI was
|
||||||
|
preferred since on newer releases of Solaris and Solaris environments
|
||||||
|
one would needs to have root access for ATAPI.
|
||||||
|
|
||||||
@node FreeBSD
|
@node FreeBSD
|
||||||
@section FreeBSD
|
@section FreeBSD
|
||||||
|
|
||||||
There are two CD drive access methods on Solaris:
|
There are two CD drive access methods on Solaris: ioctl and CAM
|
||||||
ioctl and CAM (common access method). CAM is preferred when possible;
|
(common access method). CAM is preferred when possible, especially on
|
||||||
it is however sort of a hybrid and includes some ioctl code.
|
newer releases. However CAM is right now sort of a hybrid and includes
|
||||||
|
some ioctl code.
|
||||||
|
|
||||||
More work on this driver is needed. Volunteers?
|
More work on this driver is needed. Volunteers?
|
||||||
|
|
||||||
@node OS X
|
@node OS X
|
||||||
@section OS X
|
@section OS X
|
||||||
|
|
||||||
|
A problem with OS/X is that if the OS thinks it understands the drive
|
||||||
|
it gains exclusive access to it and thus prevents a library like this
|
||||||
|
to get non-exclusive access.
|
||||||
|
|
||||||
More work on this driver is needed. Volunteers?
|
More work on this driver is needed. Volunteers?
|
||||||
|
|
||||||
@node ISO-9660 Character Sets
|
@node ISO-9660 Character Sets
|
||||||
|
|||||||
Reference in New Issue
Block a user