From: Sami Kerola <kerolasa@iki.fi>
To: util-linux@vger.kernel.org
Cc: kerolasa@iki.fi
Subject: [PATCH 14/14] docs: fsck(8), mkfs(8): update manual references
Date: Sun, 16 Dec 2012 10:44:02 +0000 [thread overview]
Message-ID: <1355654642-22106-15-git-send-email-kerolasa@iki.fi> (raw)
In-Reply-To: <1355654642-22106-1-git-send-email-kerolasa@iki.fi>
Signed-off-by: Sami Kerola <kerolasa@iki.fi>
---
disk-utils/fsck.8 | 16 +++++-----------
disk-utils/mkfs.8 | 10 ++++------
2 files changed, 9 insertions(+), 17 deletions(-)
diff --git a/disk-utils/fsck.8 b/disk-utils/fsck.8
index 344a06f..21e79da 100644
--- a/disk-utils/fsck.8
+++ b/disk-utils/fsck.8
@@ -451,17 +451,11 @@ enables debug output.
.SH SEE ALSO
.BR fstab (5),
.BR mkfs (8),
-.BR fsck.ext2 (8)
-or
-.BR fsck.ext3 (8)
-or
.BR e2fsck (8),
-.BR cramfsck (8),
-.BR fsck.minix (8),
-.BR fsck.msdos (8),
+.BR e2fsck.conf (5),
+.BR jfs_fsck (8),
+.BR jfs_fscklog (8),
.BR fsck.jfs (8),
-.BR fsck.nfs (8),
-.BR fsck.vfat (8),
+.BR fsck.minix (8),
.BR fsck.xfs (8),
-.BR fsck.xiafs (8),
-.BR reiserfsck (8).
+.BR reiserfsck (8)
diff --git a/disk-utils/mkfs.8 b/disk-utils/mkfs.8
index af9304b..c8e3d22 100644
--- a/disk-utils/mkfs.8
+++ b/disk-utils/mkfs.8
@@ -94,17 +94,15 @@ for the ext2 filesystem.
.BR fs (5),
.BR badblocks (8),
.BR fsck (8),
-.BR mkdosfs (8),
-.BR mke2fs (8),
.BR mkfs.bfs (8),
.BR mkfs.ext2 (8),
.BR mkfs.ext3 (8),
.BR mkfs.ext4 (8),
+.BR mkfs.ext4dev (8),
+.BR mkfs.jfs (8),
+.BR jfs_mkfs (8),
.BR mkfs.minix (8),
-.BR mkfs.msdos (8),
-.BR mkfs.vfat (8),
-.BR mkfs.xfs (8),
-.BR mkfs.xiafs (8)
+.BR mkfs.xfs (8)
.SH AVAILABILITY
The mkfs command is part of the util-linux package and is available from
ftp://ftp.kernel.org/pub/linux/utils/util-linux/.
--
1.8.0.2
next prev parent reply other threads:[~2012-12-16 10:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 10:43 [00/14]: pull: ipcs resubmission, bug fixes, minix todo, etc Sami Kerola
2012-12-16 10:43 ` [PATCH 01/14] docs: swapon.8 option name fix Sami Kerola
2012-12-16 10:43 ` [PATCH 02/14] ipcs: assist debugging Sami Kerola
2012-12-16 10:43 ` [PATCH 03/14] ipcs: add --human readable size conversion option Sami Kerola
2012-12-16 10:43 ` [PATCH 04/14] ipcs: add --bytes size output option Sami Kerola
2012-12-16 10:43 ` [PATCH 05/14] isosize: fix usage() -h option print out Sami Kerola
2012-12-16 10:43 ` [PATCH 06/14] isosize: inform if file does not look like iso file system Sami Kerola
2012-12-16 10:43 ` [PATCH 07/14] more: remove unnecessary variable Sami Kerola
2012-12-16 10:43 ` [PATCH 08/14] tunelp: deprecation: remove command from default build Sami Kerola
2012-12-16 10:43 ` [PATCH 09/14] minix: change types in header file Sami Kerola
2012-12-16 10:43 ` [PATCH 10/14] minix: use off_t, size_t, etc appropriate types Sami Kerola
2012-12-16 10:43 ` [PATCH 11/14] minix: replace magic constants with macro names Sami Kerola
2012-12-16 10:44 ` [PATCH 12/14] docs: add missing exit value to fsck.minix(8) Sami Kerola
2012-12-16 10:44 ` [PATCH 13/14] lib/ismounted: detect loopback mounts Sami Kerola
2012-12-19 13:38 ` Karel Zak
2012-12-16 10:44 ` Sami Kerola [this message]
2012-12-19 13:54 ` [PATCH 14/14] docs: fsck(8), mkfs(8): update manual references Karel Zak
2012-12-19 14:29 ` [00/14]: pull: ipcs resubmission, bug fixes, minix todo, etc Karel Zak
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=1355654642-22106-15-git-send-email-kerolasa@iki.fi \
--to=kerolasa@iki.fi \
--cc=util-linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox