Date: Wed, 2 Apr 2014 20:38:23 -0700 (PDT) From: "Ronald F.Guilmette" <rfg@tristatelogic.com> To: FreeBSD-gnats-submit@freebsd.org Cc: rfg@tristatelogic.com Subject: docs/188214: Manpage for fsck(8) doesn't say what happens when no -t or -T Message-ID: <20140403033823.BDBAC3AE0E@segfault.tristatelogic.com> Resent-Message-ID: <201404030340.s333e0Ko009783@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 188214 >Category: docs >Synopsis: Manpage for fsck(8) doesn't say what happens when no -t or -T >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Thu Apr 03 03:40:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Ronald F. Guilmette >Release: FreeBSD 9.1-RELEASE amd64 >Organization: entr0py >Environment: 9.1-RELEASE amd64 >Description: It has been suggested to me that if and when fsck(8) is invoked _without_ any explicitly provided -t or -T options, fsck will, in such cases, attempt to intuit the type of the filesystem on its own, perhaps based upon information/clues gleened from the local /etc/fstab file and/or from some relevant BSD disk label. If true, then this behavior does not appear to be documented at all within the fsck(8) manpage. This is an important aspect of the behavior of fsck(8). If verified, then it should be documented in the manpage. >How-To-Repeat: man 8 fsck >Fix: Sorry, I do not have any suggested replacement text for the relevant manpage at this time. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140403033823.BDBAC3AE0E>