[Debburn-changes] r262 - nonameyet/trunk/mkisofs
Eduard Bloch
blade at costa.debian.org
Mon Sep 11 21:47:22 UTC 2006
Author: blade
Date: 2006-09-11 21:47:22 +0000 (Mon, 11 Sep 2006)
New Revision: 262
Modified:
nonameyet/trunk/mkisofs/mkisofs.8
Log:
More spelling/grammar/typo fixes by Tollef
Modified: nonameyet/trunk/mkisofs/mkisofs.8
===================================================================
--- nonameyet/trunk/mkisofs/mkisofs.8 2006-09-11 21:40:33 UTC (rev 261)
+++ nonameyet/trunk/mkisofs/mkisofs.8 2006-09-11 21:47:22 UTC (rev 262)
@@ -82,7 +82,7 @@
the Rock Ridge extensions (such as MS-DOS), and each filename in each directory
must be different from the other filenames in the same directory.
.B mkisofs
-generally tries to form correct names by forcing the unix filename to upper
+generally tries to form correct names by forcing the UNIX filename to upper
case and truncating as required, but often times this yields unsatisfactory
results when there are cases where the
truncated names are not all unique.
@@ -125,7 +125,7 @@
for the entire time that the disc is being written.
.PP
.B pathspec
-is the path of the directory tree to be copied into the iso9660 filesystem.
+is the path of the directory tree to be copied into the ISO9660 filesystem.
Multiple paths can be specified, and
.B
mkisofs
@@ -403,7 +403,7 @@
.BI \-sparc\-boot " img_sun4,img_sun4c,img_sun4m,img_sun4d,img_sun4e
Specifies a comma separated list of boot images that are needed to make
a bootable CD for sparc systems.
-Partition 0 is used for the ISO-9660 image, the first image file is mapped
+Partition 0 is used for the ISO9660 image, the first image file is mapped
to partition 1.
There may be empty fields in the comma separated list.
The maximum number of possible partitions is 8 so it is impossible to specify
@@ -415,7 +415,7 @@
.B \-sparc\-boot
option has been specified, the first sector of the resulting image will
contain a Sun disk label. This disk label specifies slice 0 for the
-iso9660 image and slice 1 .\|.\|. slice 7 for the boot images that
+ISO9660 image and slice 1 .\|.\|. slice 7 for the boot images that
have been specified with this option. Byte offset 512 .\|.\|. 8191
within each of the additional boot images must contain a primary boot
that works for the appropriate sparc architecture. The rest of each
@@ -438,7 +438,7 @@
.B mkisofs
is called with
.BI "\-G " image " \-B " ...
-all boot partitions are mapped to the partition that contains the iso9660
+all boot partitions are mapped to the partition that contains the ISO9660
filesystem image and the generic boot image that is located in the first
16 sectors of the disk is used for all architectures.
.TP
@@ -448,7 +448,7 @@
The
.B generic_boot_image
will be placed on the first 16 sectors of the CD. The first 16 sectors
-are the sectors that are located before the iso9660 primary volume descriptor.
+are the sectors that are located before the ISO9660 primary volume descriptor.
If this option is used together with the
.B \-sparc\-boot
option, the Sun disk label will overlay the first 512 bytes of the generic
@@ -490,7 +490,7 @@
.BI \-C " last_sess_start,next_sess_start
This option is needed when
.B mkisofs
-is used to create a CDextra or the image of a second session or a
+is used to create a CD Extra or the image of a second session or a
higher level session for a multi session disk.
The option
.B \-C
@@ -515,7 +515,7 @@
option,
.B mkisofs
will create a filesystem image that is intended to be used for a second
-session on a CDextra. This is a multi session CD that holds audio data
+session on a CD Extra. This is a multi session CD that holds audio data
in the first session and a ISO9660 filesystem in the second session.
.TP
.BI \-c " boot_catalog
@@ -540,15 +540,15 @@
Check all filenames imported from old session for compliance with
actual
.B mkisofs
-iso9660 file naming rules.
+ISO9660 file naming rules.
It his option is not present, only names with a length > 31 are checked
-as these files are a hard violation of the iso9660 standard.
+as these files are a hard violation of the ISO9660 standard.
.TP
.BI \-check\-session " FILE
Check all old sessions for compliance with
actual
.B mkisofs
-iso9660 file naming rules.
+ISO9660 file naming rules.
This is a high level option that is a combination of the options:
.BI \-M " FILE " "\-C 0,0 \-check\-oldnames
For the parameter
@@ -558,7 +558,7 @@
option.
.TP
.BI \-copyright " FILE
-Specifies the Copyright file name.
+Specifies the copyright file name.
There is space on the disc for 37 characters of information.
This parameter can also be set in the file
.B \&.m\&kisofsrc
@@ -585,7 +585,7 @@
Specifying this option automatically enables Rock Ridge extensions.
.TP
.B \-dvd\-video
-Generate DVD-Video compliant UDF file system. This is done by sorting the
+Generate a DVD-Video compliant UDF file system. This is done by sorting the
order of the content of the appropriate files and by adding padding
between the files if needed.
Note that the sorting only works if the DVD-Video filenames include upper case
@@ -745,7 +745,7 @@
section below for more details.
.TP
.BI \-iso\-level " level
-Set the iso9660 conformance level. Valid numbers are 1..3 and 4.
+Set the ISO9660 conformance level. Valid numbers are 1..3 and 4.
.sp
With level 1, files may only consist of one section and filenames are
restricted to 8.3 characters.
@@ -754,14 +754,14 @@
.sp
With level 3, no restrictions (other than ISO-9660:1988) do apply.
.sp
-With all iso9660 levels from 1..3, all filenames are restricted to upper
+With all ISO9660 levels from 1..3, all filenames are restricted to upper
case letters, numbers and the underscore (_). The maximum filename
length is restricted to 31 characters, the directory nesting level
is restricted to 8 and the maximum path length is limited to 255 characters.
.sp
Level 4 officially does not exists but
.B mkisofs
-maps it to ISO-9660:1999 which is ISO-9660 version 2.
+maps it to ISO-9660:1999 which is ISO9660 version 2.
.sp
With level 4, an enhanced volume descriptor with version number
and file structure version number set to 2 is emitted.
@@ -773,21 +773,21 @@
.\" specified to be characters is subject to agreement between the
.\" originator and the recipient of the volume),
the maximum length for files and directory is raised to 207.
-If Rock Ridge is used, the maximum ISO-9660 name length is reduced to 197.
+If Rock Ridge is used, the maximum ISO9660 name length is reduced to 197.
.sp
When creating Version 2 images,
.B mkisofs
emits an enhanced volume descriptor which looks similar to a primary volume
descriptor but is slightly different. Be careful not to use broken software
-to make ISO-9660 images bootable by assuming a second PVD copy and patching
+to make ISO9660 images bootable by assuming a second PVD copy and patching
this putative PVD copy into an El Torito VD.
.TP
.B \-J
-Generate Joliet directory records in addition to regular iso9660 file
-names. This is primarily useful when the discs are to be used on Windows-NT
-or Windows-95 machines. The Joliet filenames are specified in Unicode and
+Generate Joliet directory records in addition to regular ISO9660 file
+names. This is primarily useful when the discs are to be used on Windows
+machines. The Joliet filenames are specified in Unicode and
each path component can be up to 64 Unicode characters long.
-Note that Joliet is no standard - CD's that use only Joliet extensions but no
+Note that Joliet is not a standard - CDs that use only Joliet extensions but no
standard Rock Ridge extensions may usually only be used on Microsoft Win32
systems. Furthermore, the fact that the filenames are limited to 64 characters
and the fact that Joliet uses the UTF-16 coding for Unicode characters causes
@@ -872,7 +872,7 @@
.BI \-m " glob
Exclude
.I glob
-from being written to CDROM.
+from being written to CD-ROM.
.I glob
is a shell wild-card-style pattern that must match part of the filename (not
the path as with option
@@ -888,7 +888,7 @@
mkisofs \-o rom \-m '*.o' \-m core \-m foobar
would exclude all files ending in ".o", called "core" or "foobar" to be
-copied to CDROM. Note that if you had a directory called "foobar" it too (and
+copied to CD-ROM. Note that if you had a directory called "foobar" it too (and
of course all its descendants) would be excluded.
.sp
NOTE: The
@@ -905,11 +905,11 @@
to be exclude as above.
.TP
.B \-max\-iso9660\-filenames
-Allow 37 chars in iso9660 filenames.
+Allow 37 chars in ISO9660 filenames.
This option forces the
.B \-N
option as the extra name space is taken from the space reserved for
-ISO-9660 version numbers.
+ISO9660 version numbers.
.br
This violates the ISO9660 standard, but it happens to work on many systems.
Although a conforming application needs to provide a buffer space of at
@@ -923,7 +923,7 @@
or
.TP
.BI \-dev " device
-Specifies path to existing iso9660 image to be merged. The alternate form
+Specifies path to existing ISO9660 image to be merged. The alternate form
takes a SCSI device specifier that uses the same syntax as the
.B "dev=
parameter of
@@ -946,22 +946,22 @@
Use with caution.
.TP
.BI \-new\-dir\-mode " mode
-Mode to use when creating new directories in the iso fs image. The default
+Mode to use when creating new directories in the filesystem image. The default
mode is 0555.
.TP
.B \-nobak
.TP
.B \-no\-bak
-Do not include backup files files on the iso9660 filesystem.
+Do not include backup files files on the ISO9660 filesystem.
If the
.B \-no\-bak
option is specified, files that contain the characters '~' or '#'
or end in '.bak' will not be included (these are typically backup files
-for editors under unix).
+for editors under UNIX).
.TP
.B \-force\-rr
Do not use the automatic Rock Ridge attributes recognition for previous sessions.
-This helps to show rotten iso9660 extension records as e.g. created by NERO burning ROM.
+This helps to show rotten ISO9660 extension records as e.g. created by NERO burning ROM.
.TP
.B \-no\-rr
Do not use the Rock Ridge attributes from previous sessions.
@@ -1002,7 +1002,7 @@
has been fixed in May 2003.
.TP
.BI \-o " filename
-is the name of the file to which the iso9660 filesystem image should be
+is the name of the file to which the ISO9660 filesystem image should be
written. This can be a disk file, a tape drive, or it can correspond directly
to the device name of the optical disc writer. If not specified, stdout is
used. Note that the output can also be a block special device for a regular
@@ -1013,7 +1013,7 @@
Pad the end of the whole image by 150 sectors (300 kB).
If the option
.B \-B
-is used, then there is a padding at the end of the iso9660 partition
+is used, then there is a padding at the end of the ISO9660 partition
and before the beginning of the boot partitions.
The size of this padding is chosen to make the first boot partition start
on a sector number that is a multiple of 16.
@@ -1051,7 +1051,7 @@
.TP
.BI \-publisher " publisher_id
Specifies a text string that will be written into the volume header.
-This should describe the publisher of the CDROM, usually with a
+This should describe the publisher of the CD-ROM, usually with a
mailing address and phone number. There is space on the disc for 128
characters of information. This parameter can also be set in the file
.B \&.m\&kisofsrc
@@ -1060,7 +1060,7 @@
.TP
.BI \-p " preparer_id
Specifies a text string that will be written into the volume header.
-This should describe the preparer of the CDROM, usually with a mailing
+This should describe the preparer of the CD-ROM, usually with a mailing
address and phone number. There is space on the disc for 128
characters of information. This parameter can also be set in the file
.B \&.m\&kisofsrc
@@ -1073,7 +1073,7 @@
Disk At Once mode and with some CD-R drives when piping directly into
.B wodim.
In this case it is needed to know the size of the filesystem before the
-actual CD-creation is done.
+actual CD creation is done.
The option \-print\-size allows to get this size from a "dry-run" before
the CD is actually written.
Old versions of
@@ -1101,7 +1101,7 @@
.TP
.B \-R
Generate SUSP and RR records using the Rock Ridge protocol to further describe
-the files on the iso9660 filesystem.
+the files on the ISO9660 filesystem.
.TP
.B \-r
This is like the \-R option, but file ownership and modes are set to
@@ -1113,7 +1113,7 @@
globally executable on the client. If any search bit is set for a
directory, set all of the search bits, so that directories are globally
searchable on the client. All write bits are cleared, because the
-CD-Rom will be mounted read-only in any case. If any of the special
+filesystem will be mounted read-only in any case. If any of the special
mode bits are set, clear them, because file locks are not useful on a
read-only file system, and set-id bits are not desirable for uid 0 or
gid 0.
@@ -1215,7 +1215,7 @@
.TP
.B \-split\-output
Split the output image into several files of approximately 1 GB.
-This helps to create DVD sized iso9660 images on operating systems without
+This helps to create DVD sized ISO9660 images on operating systems without
large file support.
Wodim will concatenate more than one file into a single track if writing
to a DVD.
@@ -1229,7 +1229,7 @@
.BI \-stream\-media\-size " #
Select streaming operation and set the media size to # sectors.
This allows you to pipe the output of the tar program into mkisofs
-and to create a iso9660 filesystem without the need of an intermediate
+and to create a ISO9660 filesystem without the need of an intermediate
tar archive file.
If this option has been specified,
.B mkisofs
@@ -1245,7 +1245,7 @@
.sp
The option
.B \-stream\-media\-size
-creates simple iso9660 filesystems only and may not used together with multi-session
+creates simple ISO9660 filesystems only and may not used together with multi-session
or hybrid filesystem options.
.TP
.BI \-stream\-file\-name " name
@@ -1255,7 +1255,7 @@
Specifies a comma separated list of filesystem images that are needed to make
a bootable CD for Solaris x86 systems.
.sp
-Note that partition 1 is used for the ISO-9660 image and that partition 2 is
+Note that partition 1 is used for the ISO9660 image and that partition 2 is
the whole disk, so partition 1 and 2 may not be used by external partition data.
The first image file is mapped to partition 0.
There may be empty fields in the comma separated list,
@@ -1274,7 +1274,7 @@
SVr4 disk label at offset 1024 in the first sector of the CD.
This disk label specifies slice 0 for the first (usually UFS type)
filesystem image that is used to boot the PC and slice 1 for
-the iso9660 image.
+the ISO9660 image.
Slice 2 spans the whole CD slice 3 .\|.\|. slice 7 may be used for additional
filesystem images that have been specified with this option.
.sp
@@ -1301,7 +1301,7 @@
If specified in both places, the command line version is used.
.TP
.B \-T
-Generate a file TRANS.TBL in each directory on the CDROM, which can be used
+Generate a file TRANS.TBL in each directory on the CD-ROM, which can be used
on non-Rock Ridge capable systems to help establish the correct file names.
There is also information present in the file that indicates the major and
minor numbers for block and character devices, and each symlink has the name of
@@ -1332,7 +1332,7 @@
Note that
.B UDF
wastes the space from sector ~20 to sector 256 at the beginning of the disk
-in addition to the spcae needed for real
+in addition to the space needed for real
.B UDF
data structures.
.TP
@@ -1355,7 +1355,7 @@
This option is the default on VMS.
.TP
.B \-U
-Allows "Untranslated" filenames, completely violating the iso9660 standards
+Allows "Untranslated" filenames, completely violating the ISO9660 standards
described above. Forces on the \-d, \-l, \-N, \-allow\-leading\-dots,
\-relaxed\-filenames,
\-allow\-lowercase, \-allow\-multidot and \-no\-iso\-translate
@@ -1365,7 +1365,7 @@
not recognize ANY extensions. Use with extreme caution.
.TP
.B \-no\-iso\-translate
-Do not translate the characters '#' and '~' which are invalid for iso9660 filenames.
+Do not translate the characters '#' and '~' which are invalid for ISO9660 filenames.
These characters are though invalid often used by Microsoft systems.
.br
This violates the ISO9660 standard, but it happens to work on many systems.
@@ -1393,12 +1393,12 @@
.TP
.BI \-volset\-size " #
Sets the volume set size to #.
-The volume set size is the number of CD's that are in a CD volume set.
+The volume set size is the number of CDs that are in a CD volume set.
A volume set is a collection of one or more volumes, on which a set of
files is recorded.
.sp
-Volume Sets are not intended to be used to create a set numbered CD's
-that are part of e.g. a Operation System installation set of CD's.
+Volume Sets are not intended to be used to create a set numbered CDs
+that are part of e.g. a Operation System installation set of CDs.
Volume Sets are rather used to record a big directory tree that would not
fit on a single volume.
Each volume of a Volume Set contains a description of all the directories
@@ -1406,7 +1406,7 @@
are less than, or equal to, the assigned Volume Set Size of the current
volume.
.sp
-.B Mkisofs
+.B mkisofs
currently does not support a
.B \-volset\-size
that is larger than 1.
@@ -1434,7 +1434,7 @@
.BI \-x " path
Exclude
.I path
-from being written to CDROM.
+from being written to CD-ROM.
.I path
must be the complete pathname that results from concatenating the pathname
given as command line argument and the path relative to this directory.
@@ -1458,7 +1458,7 @@
.B \-R
or
.B \-r
-options to enable RockRidge, and generate compressed files using the
+options to enable Rock Ridge, and generate compressed files using the
.B mkzftree
utility before running
.BR mkisofs .
@@ -1498,7 +1498,7 @@
.I mapping_file
to set the CREATOR and TYPE information for a file based on the
filename's extension. A filename is
-mapped only if it is not one of the know Apple/Unix file formats. See the
+mapped only if it is not one of the know Apple/UNIX file formats. See the
.B "HFS CREATOR/TYPE
section below.
.TP
@@ -1507,7 +1507,7 @@
.I magic number
(usually the first few bytes of a file). The
.I magic_file
-is only used if a file is not one of the known Apple/Unix file formats, or
+is only used if a file is not one of the known Apple/UNIX file formats, or
the filename extension has not been mapped using the
.B \-map
option. See the
@@ -1525,7 +1525,7 @@
section below for more details.
.TP
.B \-probe
-Search the contents of files for all the known Apple/Unix file formats.
+Search the contents of files for all the known Apple/UNIX file formats.
See the
.B HFS MACINTOSH FILE FORMATS
section below for more about these formats.
@@ -1537,7 +1537,7 @@
.I may
increase processing time. It is better to use one or more
.I double dash
-options given below if the Apple/Unix formats in use are known.
+options given below if the Apple/UNIX formats in use are known.
.TP
.B \-no\-desktop
Do not create (empty) Desktop files. New HFS Desktop files will be created
@@ -1561,8 +1561,8 @@
.TP
.B \-part
Generate an HFS partition table. By default, no partition table is generated,
-but some older Macintosh CDROM drivers need an HFS partition table on the
-CDROM to be able to recognize a hybrid CDROM.
+but some older Macintosh CD-ROM drivers need an HFS partition table on the
+CD-ROM to be able to recognize a hybrid CD-ROM.
.TP
.BI \-auto " AutoStart_file
Make the HFS CD use the QuickTime 2.0 Autostart feature to launch an
@@ -1625,7 +1625,7 @@
option
.TP
.B \-icon\-position
-Use the icon position information, if it exists, from the Apple/Unix file.
+Use the icon position information, if it exists, from the Apple/UNIX file.
The icons will appear in the same position as they would on a Macintosh
desktop. Folder location and size on screen, its scroll positions, folder
View (view as Icons, Small Icons, etc.) are also preserved.
@@ -1686,8 +1686,8 @@
details.
.TP
.B \-\-cap
-Look for AUFS CAP Macintosh files. Search for CAP Apple/Unix file formats
-only. Searching for the other possible Apple/Unix file formats is disabled,
+Look for AUFS CAP Macintosh files. Search for CAP Apple/UNIX file formats
+only. Searching for the other possible Apple/UNIX file formats is disabled,
unless other
.I double dash
options are given.
@@ -1759,7 +1759,7 @@
coded Unicode character.
If a character is coded in
.B "7-Bit ASCII
-(used in USA and other countries with limted character set)
+(used in USA and other countries with limited character set)
is maps 1:1 to a
.BR UTF-32 ", " UTF-16 " or " UTF-8
coded Unicode character.
@@ -1836,15 +1836,15 @@
.IP \-output\-charset
Defines the character set that will be used with for the Rock Ridge names
on the CD. Defaults to the input character set. Only likely to be useful
-if used on a non-Unix platform. e.g. using
+if used on a non-UNIX platform. e.g. using
.B mkisofs
on a Microsoft Win32 machine to create Rock Ridge CDs. If you are using
.B mkisofs
-on a Unix machine, it is likely that the output character set
+on a UNIX machine, it is likely that the output character set
will be the same as the input character set.
.IP \-input\-hfs\-charset
Defines the HFS character set used for HFS file names decoded from
-any of the various Apple/Unix file formats. Only useful when used with
+any of the various Apple/UNIX file formats. Only useful when used with
.I \-mac\-name
option. See the
.B HFS MACINTOSH FILE NAMES
@@ -1914,7 +1914,7 @@
application etc. The CREATOR and TYPE of a particular file can be found by
using something like ResEdit (or similar) on a Macintosh.
.LP
-The CREATOR and TYPE information is stored in all the various Apple/Unix
+The CREATOR and TYPE information is stored in all the various Apple/UNIX
encoded files.
For other files it is possible to base the CREATOR and TYPE on the
filename's extension using a
@@ -1982,13 +1982,13 @@
.IP
The first column
.I EXTN
-defines the Unix filename extension to be
+defines the UNIX filename extension to be
mapped. The default mapping for any filename extension that doesn't
match is defined with the "*" character.
.IP
The
.I Xlate
-column defines the type of text translation between the Unix and
+column defines the type of text translation between the UNIX and
Macintosh file it is ignored by
.BR mkisofs ,
but is kept to be compatible with
@@ -2045,7 +2045,7 @@
0/string/GIF8/8BIM GIFf GIF image
0/beshort/0xffd8/8BIM JPEG image data
0/string/SIT!/SIT! SIT! StuffIt Archive
-0/string/\\037\\235/LZIV ZIVU standard unix compress
+0/string/\\037\\235/LZIV ZIVU standard UNIX compress
0/string/\\037\\213/GNUz ZIVU gzip compressed data
0/string/%!/ASPS TEXT Postscript
0/string/\\004%!/ASPS TEXT PC Postscript with a ^D to start
@@ -2079,9 +2079,9 @@
.B \-hfs\-type
options.
.PP
-If the a file is in one of the known Apple/Unix formats (and the format
+If the a file is in one of the known Apple/UNIX formats (and the format
has been selected), then the CREATOR and TYPE are taken from the values
-stored in the Apple/Unix file.
+stored in the Apple/UNIX file.
.PP
Other files can have their CREATOR and TYPE set from their file name
extension (the
@@ -2100,25 +2100,25 @@
.I Data
and
.I Resource
-fork. Either may be empty. Unix (and many other OSs) can only
+fork. Either may be empty. UNIX (and many other OSs) can only
cope with files having one part (or fork). To add to this, Macintosh files
have a number of attributes associated with them - probably the most
-important are the TYPE and CREATOR. Again Unix has no concept of these
+important are the TYPE and CREATOR. Again UNIX has no concept of these
types of attributes.
.PP
e.g. a Macintosh file may be a JPEG image where the image is stored in the
Data fork and a desktop thumbnail stored in the Resource fork. It is usually
the information in the data fork that is useful across platforms.
.PP
-Therefore to store a Macintosh file on a Unix filesystem, a way has to be
+Therefore to store a Macintosh file on a UNIX filesystem, a way has to be
found to cope with the two forks and the extra attributes (which are
referred to as the
.I finder
.IR info ).
Unfortunately, it seems that every software package that stores Macintosh
-files on Unix has chosen a completely different storage method.
+files on UNIX has chosen a completely different storage method.
.PP
-The Apple/Unix formats that
+The Apple/UNIX formats that
.I mkisofs
(partially) supports are:
.IP "CAP AUFS format"
@@ -2201,7 +2201,7 @@
Data fork stored in a file. Resource fork stored in a file with
same name prefixed with "._". Finder info also stored in same "._" file.
.IP "MacOS X HFS (Alpha)"
-Not really an Apple/Unix encoding, but actual HFS/HFS+ files on a MacOS X
+Not really an Apple/UNIX encoding, but actual HFS/HFS+ files on a MacOS X
system. Data fork stored in a file. Resource fork stored in a pseudo file
with the same name with the suffix '/rsrc'. The finderinfo is only
available via a MacOS X library call.
@@ -2212,13 +2212,13 @@
.IP
If a file is found with a zero
length resource fork and empty finderinfo, it is assumed not to have
-any Apple/Unix encoding - therefore a TYPE and CREATOR can be set using
+any Apple/UNIX encoding - therefore a TYPE and CREATOR can be set using
other methods.
.LP
.I mkisofs
will attempt to set the CREATOR, TYPE, date and possibly other flags from
the finder info. Additionally, if it exists, the Macintosh filename is set
-from the finder info, otherwise the Macintosh name is based on the Unix
+from the finder info, otherwise the Macintosh name is based on the UNIX
filename - see the
.B "HFS MACINTOSH FILE NAMES
section below.
@@ -2255,21 +2255,21 @@
approaching 650MB.
.SH "HFS MACINTOSH FILE NAMES
-Where possible, the HFS filename that is stored with an Apple/Unix file
-is used for the HFS part of the CD. However, not all the Apple/Unix
+Where possible, the HFS filename that is stored with an Apple/UNIX file
+is used for the HFS part of the CD. However, not all the Apple/UNIX
encodings store the HFS filename with the finderinfo. In these cases,
-the Unix filename is used - with escaped special characters. Special
+the UNIX filename is used - with escaped special characters. Special
characters include '/' and characters with codes over 127.
.PP
-Aufs escapes these characters by using ":" followed by the character code
+AUFS escapes these characters by using ":" followed by the character code
as two hex digits. Netatalk and EtherShare have a similar scheme, but uses
"%" instead of a ":".
.PP
-If mkisofs can't find an HFS filename, then it uses the Unix name, with
+If mkisofs can not find an HFS filename, it uses the UNIX name, with
any %xx or :xx characters (xx == two hex digits) converted to a single
character code. If "xx" are not hex digits ([0-9a-fA-F]), then they are
left alone - although any remaining ":" is converted to "%" as colon
-is the HFS directory separator. Care must be taken, as an ordinary Unix
+is the HFS directory separator. Care must be taken, as an ordinary UNIX
file with %xx or :xx will also be converted. e.g.
.PP
.TS
@@ -2297,7 +2297,7 @@
the starting point for the ISO9660, Joliet and Rock Ridge filenames using
the
.B \-mac\-name
-option. Normal Unix files without an HFS name will still use their Unix name.
+option. Normal UNIX files without an HFS name will still use their UNIX name.
e.g.
.PP
If a
@@ -2307,10 +2307,10 @@
.IR Exchange )
file is stored as
.I someimage.gif.bin
-on the Unix filesystem, but contains a HFS file called
+on the UNIX filesystem, but contains a HFS file called
.IR someimage.gif ,
then this is the name that would appear on the HFS part of the CD. However, as
-mkisofs uses the Unix name as the starting point for the other names, then
+mkisofs uses the UNIX name as the starting point for the other names, then
the ISO9660 name generated will probably be
.I SOMEIMAG.BIN
and the Joliet/Rock Ridge would be
@@ -2325,7 +2325,7 @@
.B \-mac\-name
option will not currently work with the
.B \-T
-option - the Unix
+option - the UNIX
name will be used in the TRANS.TBL file, not the Macintosh name.
.PP
The character set used to convert any HFS file name to a Joliet/Rock Ridge
@@ -2339,13 +2339,13 @@
cp10081 (MacTurkish).
.PP
Note: the character codes used by HFS file names taken from the various
-Apple/Unix formats will not be converted as they are assumed to be in the
+Apple/UNIX formats will not be converted as they are assumed to be in the
correct Apple character set. Only the Joliet/Rock Ridge names derived from
the HFS file names will be converted.
.PP
The existing mkisofs code will filter out any illegal characters for the
ISO9660 and Joliet filenames, but as mkisofs expects to be dealing
-directly with Unix names, it leaves the Rock Ridge names as is.
+directly with UNIX names, it leaves the Rock Ridge names as is.
But as '/' is a legal HFS filename character, the
.B \-mac\-name
option converts '/' to a '_' in Rock Ridge filenames.
@@ -2590,7 +2590,7 @@
command line option.
.TP
.B PREP
-This should describe the preparer of the CDROM,
+This should describe the preparer of the CD-ROM,
usually with a mailing address and phone number.
There is space on the disc for 128 characters of information.
May be overridden using the
@@ -2598,7 +2598,7 @@
command line option.
.TP
.B PUBL
-This should describe the publisher of the CDROM,
+This should describe the publisher of the CD-ROM,
usually with a mailing address and phone number.
There is space on the disc for 128 characters of information.
May be overridden using the
@@ -2644,7 +2644,7 @@
.SH EXAMPLES
.PP
-To create a vanilla ISO-9660 filesystem image in the file
+To create a vanilla ISO9660 filesystem image in the file
.IR cd.iso ,
where the directory
.I cd_dir
@@ -2669,7 +2669,7 @@
% mkisofs \-o cd.iso \-r cd_dir
.PP
To write a tar archive directly to a CD that will later contain a simple
-iso9660 filesystem with the tar archive call:
+ISO9660 filesystem with the tar archive call:
.PP
% star \-c . | mkisofs \-stream\-media\-size 333000 | \\
.br
@@ -2684,7 +2684,7 @@
To create a HFS hybrid CD from the source directory
.I cd_dir
that contains
-Netatalk Apple/Unix files:
+Netatalk Apple/UNIX files:
.PP
% mkisofs \-o cd.iso \-\-netatalk cd_dir
.PP
@@ -2701,7 +2701,7 @@
.I cd_dir
and
.IR another_dir.
-Files in all the known Apple/Unix format
+Files in all the known Apple/UNIX format
are decoded and any other files are given CREATOR and TYPE based on their
magic number given in the file "magic":
.PP
@@ -2711,7 +2711,7 @@
.PP
The following example puts different files on the CD that all have
the name README, but have different contents when seen as a
-ISO9660/RockRidge, Joliet or HFS CD.
+ISO9660/Rock Ridge, Joliet or HFS CD.
.PP
Current directory contains:
.PP
@@ -2739,7 +2739,7 @@
.PP
i.e. the file README.hfs will be seen as README on the HFS CD and the
other two README files will be hidden. Similarly for the Joliet and
-ISO9660/RockRidge CD.
+ISO9660/Rock Ridge CD.
.PP
There are probably all sorts of strange results possible with
combinations of the hide options ...
@@ -2775,14 +2775,14 @@
.SH NOTES
.PP
.B mkisofs
-is not based on the standard mk*fs tools for unix, because we must generate
-a complete copy of an existing filesystem on a disk in the iso9660
+is not based on the standard mk*fs tools for UNIX, because we must generate
+a complete copy of an existing filesystem on a disk in the ISO9660
filesystem. The name mkisofs is probably a bit of a misnomer, since it
not only creates the filesystem, but it also populates it.
However, the appropriate tool name for a UNIX tool that creates populated
filesystems - mkproto - is not well known.
.PP
-.B Mkisofs
+.B mkisofs
may safely be installed suid root. This may be needed to allow
.B mkisofs
to read the previous session when creating a multi session image.
@@ -2791,7 +2791,7 @@
.B mkisofs
is creating a filesystem image with Rock Ridge attributes and the
directory nesting level of the source directory tree is too much
-for ISO-9660,
+for ISO9660,
.B mkisofs
will do deep directory relocation.
This results in a directory called
@@ -2812,7 +2812,7 @@
.TP
\(bu
Any files that have hard links to files not in the tree being copied to the
-iso9660 filesystem will have an incorrect file reference count.
+ISO9660 filesystem will have an incorrect file reference count.
.TP
\(bu
Does not check for SUSP record(s) in "." entry of the
@@ -2863,16 +2863,16 @@
_N' (N == decimal number) substituted for the last few characters
to generate unique names.
.PP
-Care must be taken when "grafting" Apple/Unix files or directories (see
+Care must be taken when "grafting" Apple/UNIX files or directories (see
above for the method and syntax involved). It is not possible to use a
-new name for an Apple/Unix encoded file/directory. e.g. If a Apple/Unix
+new name for an Apple/UNIX encoded file/directory. e.g. If a Apple/UNIX
encoded file called "oldname" is to added to the CD, then you can not use
the command line:
.IP
mkisofs \-o output.raw \-hfs \-graft\-points newname=oldname cd_dir
.LP
mkisofs will be unable to decode "oldname". However, you can graft
-Apple/Unix encoded files or directories as long as you do not attempt to
+Apple/UNIX encoded files or directories as long as you do not attempt to
give them new names as above.
.PP
When creating an HFS volume with the multisession options,
@@ -2907,7 +2907,7 @@
The maximum number of files in an HFS volume is about 65500 - although
the real limit will be somewhat less than this.
.PP
-The resulting hybrid volume can be accessed on a Unix machine by using
+The resulting hybrid volume can be accessed on a UNIX machine by using
the hfsutils routines. However, no changes can be made to the volume as it
is set as
.B locked.
@@ -2921,7 +2921,7 @@
.B \-mac\-name
option will not currently work with the
.B \-T
-option - the Unix
+option - the UNIX
name will be used in the TRANS.TBL file, not the Macintosh name.
.PP
Although
More information about the Debburn-changes
mailing list