From 66ee8158b69525e12060ef558cb5d77feadab1dc Mon Sep 17 00:00:00 2001 From: Karel Zak Date: Thu, 7 Dec 2006 00:25:44 +0100 Subject: Imported from util-linux-2.10s tarball. --- disk-utils/isosize.8 | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 disk-utils/isosize.8 (limited to 'disk-utils/isosize.8') diff --git a/disk-utils/isosize.8 b/disk-utils/isosize.8 new file mode 100644 index 00000000..47ab71fc --- /dev/null +++ b/disk-utils/isosize.8 @@ -0,0 +1,29 @@ +.TH ISOSIZE "8" "December 2000" "sg3_utils-0.91" SG_UTILS +.SH NAME +isosize \- outputs the length of a iso9660 file system +.SH SYNOPSIS +.B isosize +[\fI-x\fR] [\fI-d \fR] \fI\fR... +.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 +file system in bytes. This can now be a large number (> > 4 GB). +.TP +-x +output in humanly readable form the block count and the block +size. Output uses the term "sectors" for "blocks". +.TP +-d +only has affect when "-x" is not given. The number output (if no errors) +is the iso9660 file size in bytes divided by . So if is +the block size then the output number will be the block count. +.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. -- cgit v1.2.3