ChangeLog, fsck.8.in:

fsck.8.in: Add explicit language to describe how options get passed to
  	filesystem-specific checkers.
This commit is contained in:
Theodore Ts'o 2001-05-05 06:45:05 +00:00
parent cd130a0887
commit 609c9d0f49
2 changed files with 27 additions and 4 deletions

View File

@ -1,5 +1,8 @@
2001-05-05 Theodore Tso <tytso@valinux.com>
* fsck.8.in: Add explicit language to describe how options get
passed to filesystem-specific checkers.
* badblocks.8.in: Fixed man page to describe the first optional
parameter to badblocks as last_block, instead of
num_blocks. (Debian bug #87216)

View File

@ -183,12 +183,32 @@ Produce verbose output, including all file system-specific commands
that are executed.
.TP
.B fsck-options
Any options which are not understood by
.BR fsck ,
or which follow the
Options which which are not understood by
.B fsck
are passed to the filesystem-specific checker. These arguments
.B must
not take arguments, as there is no
way for
.B fsck
to be able to properly guess which arguments take options and which
don't.
.IP
Options and arguments which follow the
.B \-\-
option are treated as file system-specific options to be passed to the
are treated as file system-specific options to be passed to the
file system-specific checker.
.IP
Please note that fsck is not
designed to pass arbitrarily complicated options to filesystem-specific
checkers. If you're doing something complicated, please just
execute the filesystem-specific checker directly. If you pass
.B fsck
some horribly complicated option and arguments, and it doesn't do
what you expect,
.B don't bother reporting it as a bug.
You're almost certainly doing something that you shouldn't be doing
with
.BR fsck.
.PP
Currently, standardized file system-specific options are somewhat in
flux. Although not guaranteed, the following options are supported