From 63b4b642303226b9a1cb399b3024024782f2f7b3 Mon Sep 17 00:00:00 2001 From: Thomas Schmitt Date: Tue, 26 Aug 2008 21:04:24 +0000 Subject: [PATCH] Adjusted man page statements about file size limits --- xorriso/xorriso.1 | 32 +++++++++++++++++--------------- 1 file changed, 17 insertions(+), 15 deletions(-) diff --git a/xorriso/xorriso.1 b/xorriso/xorriso.1 index d03153a6..db461848 100644 --- a/xorriso/xorriso.1 +++ b/xorriso/xorriso.1 @@ -2,7 +2,7 @@ .\" First parameter, NAME, should be all caps .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection .\" other parameters are allowed: see man(7), man(1) -.TH XORRISO 1 "Aug 24, 2008" +.TH XORRISO 1 "Aug 26, 2008" .\" Please adjust this date whenever revising the manpage. .\" .\" Some roff macros, for reference: @@ -679,7 +679,8 @@ Map a byte interval of a regular disk file into a regular file in the ISO image. This may be necessary if the disk file is larger than a single media, or if it exceeds the traditional limit of 2 GiB - 1 for old operating systems, -or the limit of 4 GiB - 1 for newer ones. +or the limit of 4 GiB - 1 for newer ones. Only the newest Linux kernels +seem to read properly files >= 4 GiB - 1. .br A clumsy remedy for this limit is to backup file pieces and to concatenate them at restore time. A well tested chopping size is 2047m. @@ -1228,12 +1229,13 @@ target file objects on disk as well, but "on" is downgraded to "nondir". \fB\-split_size\fR number["k"|"m"] Set the threshold for automatic splitting of regular files. Such splitting maps a large disk file onto a ISO directory with several part files in it. -This is necessary if the size of the disk file exceeds 4 GiB - 1. -Older operating systems can handle files only if they are smaller than 2 GiB. +This is necessary if the size of the disk file exceeds MAX = 400 GiB - 800 KiB. +Older operating systems can handle files only if they are smaller than 2 GiB +or 4 GiB. But osirrox is not affected by eventual operating system size limits. See also option -cut_out for more information about file parts. .br -Default is 0 which will exclude files >= 4 GiB by a FAILURE event. -A well tested -split_size is 2047m. Sizes of 4 GiB or more are not permissible. +Default is 0 which will exclude files >= MAX by a FAILURE event. +A well tested -split_size is 2047m. Sizes of MAX or more are not permissible. .TP .B Settings for result writing: .TP @@ -1724,6 +1726,15 @@ data_to='' sector_map='' map_with_volid=off patch_lba0=off report=blocks .br Non-default settings: .br +The result list tells intervals of 2 KiB blocks with start address, number +of blocks and quality. Qualities which begin with "+" are +supposed to be valid readable data. Qualities with "-" are no valid data. +.br +"report=files" lists the files which use damaged blocks (not with use=outdev). +The format is like with find -exec report_damage. +.br +"report=blocks_files" first lists damaged blocks and then affected files. +.br "use=outdev" reads from the output drive instead of the input drive. This avoids loading the ISO image tree from media. .br @@ -1781,15 +1792,6 @@ have an -indev and a loaded image. ":force" may be appended after the number. .br "use=sector_map" does not read any media but loads the file given by option sector_map= and processes this virtual outcome. -.br -The result list tells intervals of 2 KiB blocks with start address, number -of blocks and quality. Qualities which begin with "+" are -supposed to be valid readable data. Qualities with "-" are no valid data. -.br -"report=files" lists the files which use damaged blocks (not with use=outdev). -The format is like with find -exec report_damage. -.br -"report=blocks_files" first lists damaged blocks and then affected files. .TP .B osirrox restore options: .PP