changelog for cleaned up clean target

[debian/cpmtools] / fsck.cpm.1.in

diff --git a/fsck.cpm.1.in b/fsck.cpm.1.in
index e6fa5a7356c114a9008b93a6fcc0e4a8b77c904e..84a3c80388133942a8e0d5bce102553d3f4ec339 100644 (file)
--- a/fsck.cpm.1.in
+++ b/fsck.cpm.1.in
@@ -8,6 +8,7 @@ fsck.cpm \- check a CP/M file system
 .RB [ \-f
 .IR format ]
 .RB [ \-n ]
 .RB [ \-f
 .IR format ]
 .RB [ \-n ]

+.RB [ \-u ]

 .I image
 .ad b
 .\"}}}
 .I image
 .ad b
 .\"}}}


@@ -25,8 +26,13 @@ invalid time stamp mode).  The second pass checks extent connectivity
 .SH OPTIONS .\"{{{
 .IP "\fB\-f\fP \fIformat\fP"
 Use the given CP/M disk \fIformat\fP instead of the default format.
 .SH OPTIONS .\"{{{
 .IP "\fB\-f\fP \fIformat\fP"
 Use the given CP/M disk \fIformat\fP instead of the default format.

+.IP "\fB\-T\fP \fIlibdsk-type\fP"
+libdsk driver type, e.g. \fBtele\fP for Teledisk images or \fBraw\fP for raw images 
+(requires building cpmtools with support for libdsk).

 .IP "\fB\-n\fP"
 Open the file system read-only and do not repair any errors.
 .IP "\fB\-n\fP"
 Open the file system read-only and do not repair any errors.

+.IP "\fB\-u\fP"
+Show all CP/M file names in upper case.

 .\"}}}
 .SH "RETURN VALUE" .\"{{{
 Upon successful completion, exit code 0 is returned.
 .\"}}}
 .SH "RETURN VALUE" .\"{{{
 Upon successful completion, exit code 0 is returned.


@@ -37,12 +43,14 @@ Any errors are indicated by exit code 1.
 .SH FILES .\"{{{
 @DATADIR@/diskdefs     CP/M disk format definitions
 .\"}}}
 .SH FILES .\"{{{
 @DATADIR@/diskdefs     CP/M disk format definitions
 .\"}}}

+.SH ENVIRONMENT \"{{{
+CPMTOOLSFMT     Default format
+.\"}}}

 .SH DIAGNOSTICS .\"{{{
 .SH DIAGNOSTICS .\"{{{

-.IP "\fIimage\fP: \fIused\fP/\fItotal\fP files (\fIn\fP.\fIn\fP% 
-non-contiguous), \fIused\fP/\fItotal\fP blocks"
+.IP "\fIimage\fP: \fIused\fP/\fItotal\fP files (\fIn\fP.\fIn\fP% non-contiguos), \fIused\fP/\fItotal\fP blocks"

 No inconsistencies could be found.  The number of used files actually
 is the number of used extents.  Since a file may use more than
 No inconsistencies could be found.  The number of used files actually
 is the number of used extents.  Since a file may use more than

-one extent, this may be greater than the actual number of files, but a
+one extent, this may be greather than the actual number of files, but a

 correct measure would not reflect how many files could still be created
 at most.  A file is considered fragmented, if sequential data blocks
 pointed to by the same extent do not have sequential block numbers.
 correct measure would not reflect how many files could still be created
 at most.  A file is considered fragmented, if sequential data blocks
 pointed to by the same extent do not have sequential block numbers.


@@ -50,8 +58,8 @@ The number of used blocks includes the blocks used for system tracks
 and the directory.
 .\"}}}
 .SH AUTHORS .\"{{{
 and the directory.
 .\"}}}
 .SH AUTHORS .\"{{{

-This program is copyright 1997\(en2007 Michael Haardt
-<michael@moria.de>.  The Windows port is copyright 2000, 2001 John Elliott
+This program is copyright 1997\(en2021 Michael Haardt
+<michael@moria.de>.  The Windows port is copyright 2000, 2001, 2011 John Elliott

 <jce@seasip.demon.co.uk>.
 .PP
 This program is free software; you can redistribute it and/or modify
 <jce@seasip.demon.co.uk>.
 .PP
 This program is free software; you can redistribute it and/or modify