2006-12-07 00:25:44 +01:00
|
|
|
.TH ISOSIZE "8" "December 2000" "sg3_utils-0.91" SG_UTILS
|
|
|
|
|
.SH NAME
|
2009-07-22 11:29:04 +02:00
|
|
|
isosize \- outputs the length of an iso9660 file system
|
2006-12-07 00:25:44 +01:00
|
|
|
.SH SYNOPSIS
|
|
|
|
|
.B isosize
|
2009-07-22 11:29:04 +02:00
|
|
|
.RB [ \-x ]
|
|
|
|
|
.RB [ \-d
|
|
|
|
|
.IR <num> ]
|
|
|
|
|
.IR <iso9660_image_file> ...
|
2006-12-07 00:25:44 +01:00
|
|
|
.SH DESCRIPTION
|
|
|
|
|
.\" Add any additional description here
|
|
|
|
|
.PP
|
|
|
|
|
This command outputs the length of an iso9660 file system that
|
|
|
|
|
is contained in given file. That file may be a normal file or
|
|
|
|
|
a block device (e.g. /dev/hdd or /dev/sr0). In the absence of
|
|
|
|
|
any switches (or errors) it will output the size of the iso9660
|
2009-07-22 11:29:04 +02:00
|
|
|
file system in bytes. This can now be a large number (>> 4 GB).
|
2006-12-07 00:25:44 +01:00
|
|
|
.TP
|
2009-07-22 11:29:04 +02:00
|
|
|
.B \-x
|
2006-12-07 00:25:44 +01:00
|
|
|
output in humanly readable form the block count and the block
|
|
|
|
|
size. Output uses the term "sectors" for "blocks".
|
|
|
|
|
.TP
|
2009-07-22 11:29:04 +02:00
|
|
|
.BI \-d\ <num>
|
|
|
|
|
only has affect when
|
|
|
|
|
.B \-x
|
|
|
|
|
is not given. The number output (if no errors)
|
|
|
|
|
is the iso9660 file size in bytes divided by
|
|
|
|
|
.IR <num> .
|
|
|
|
|
So if
|
|
|
|
|
.I <num>
|
|
|
|
|
is the block size then the output number will be the block count.
|
2006-12-07 00:25:44 +01:00
|
|
|
.PP
|
|
|
|
|
The size of the file (or block device) holding a iso9660 file
|
|
|
|
|
system can be marginally larger than the actual size of the
|
|
|
|
|
iso9660 file system. One reason for this is that cd writers
|
|
|
|
|
are allowed to add "run out" sectors at the end of a iso9660
|
|
|
|
|
image.
|
