From: Davidlohr Bueso <dave@gnu.org>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux-ng <util-linux-ng@vger.kernel.org>
Subject: [PATCH 2/3] mkfs.minix: document mfs3 changes
Date: Thu, 31 Mar 2011 11:59:33 -0300 [thread overview]
Message-ID: <1301583573.2159.16.camel@offworld> (raw)
Update the mkfs.minix manpage for new options and amount of characters for a filename.
Signed-off-by: Davidlohr Bueso <dave@gnu.org>
---
disk-utils/mkfs.minix.8 | 17 +++++++++++++----
1 files changed, 13 insertions(+), 4 deletions(-)
diff --git a/disk-utils/mkfs.minix.8 b/disk-utils/mkfs.minix.8
index 9359106..da503e0 100644
--- a/disk-utils/mkfs.minix.8
+++ b/disk-utils/mkfs.minix.8
@@ -1,4 +1,4 @@
-.\" Copyright 1992, 1993, 1994 Rickard E. Faith (faith@cs.unc.edu)
+.\" Copyright 1992, 1993, 1994 Rickard E. Faith (faith@cs.unc.edu) - updated by Davidlohr Bueso <dave@gnu.og> 2011.
.\" May be freely distributed.
.TH MKFS.MINIX 8 "2 July 1996" "Util-linux 2.6" "Linux System Administrator's Manual"
.SH NAME
@@ -46,12 +46,12 @@ are found, the count is printed.
.TP
.BI \-n " namelength"
Specify the maximum length of filenames.
-Currently, the only allowable values are 14 and 30.
+Currently, the only allowable values are 14, 30 and 60 (v3 specific).
The default is 30. Note that kernels older than 0.99p7
only accept namelength 14.
.TP
.BI \-i " inodecount"
-Specify the number of inodes for the filesystem.
+ Specify the number of inodes for the filesystem.
.TP
.BI \-l " filename"
Read the bad blocks list from
@@ -59,8 +59,17 @@ Read the bad blocks list from
The file has one bad block number per line. The count of bad blocks read
is printed.
.TP
-.B \-v
+.B \-1
+Make a Minix version 1 filesystem.
+.TP
+.B \-2, \-v
Make a Minix version 2 filesystem.
+.TP
+.B \-3
+Make a Minix version 3 filesystem.
+.TP
+.BI \-B " blocksize"
+Specify the block size to use (only for v3)
.SH "EXIT CODES"
The exit code returned by
.B mkfs.minix
--
1.7.1
reply other threads:[~2011-03-31 15:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1301583573.2159.16.camel@offworld \
--to=dave@gnu.org \
--cc=kzak@redhat.com \
--cc=util-linux-ng@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.