> On Sun, Jul 25, 2010 at 09:48:23PM -0400, Kenneth R Westerback wrote:
> > If you wanted to mount according to the partition type number, DON'T
> > USE '-t <blah>'. We give you the option to OVERRIDE the partition
> > type number and you made use of that override. You have taken command
> 
> I believe that this thread is the result of documentation error on the
> mount(8) man page.  A patch for the man page is at the end of this
> message.
> 
> The problem is that the man page says:
> 
>  The argument following the -t is used to indicate the file system type.
>  The type ffs is the default.
> 
> This is incorrect.  According to lines 248 through 251 of the source
> file at
> 
>  http://www.openbsd.org/cgi-bin/cvsweb/src/sbin/mount/mount.c?annotate=1.50
> 
> the actual default behavior is to check the disklabel's filesystem type:
> 
>  If -t flag has not been specified, and spec contains either
>  a ':' or a '@' then assume that an NFS filesystem is being
>  specified ala Sun.  If not, check the disklabel for a
>  known filesystem type.
> 
> The original poster in this thread is wondering why mount(8) did not
> check the disklabel's filesystem type when he specified the -t option.
> The answer is that mount(8) checks the disklabel's filesystem type by
> default, but that -t overrides that default behavior.
> 
> 
> --- sbin/mount/mount.8.orig     Mon Jul 26 11:59:30 2010
> +++ sbin/mount/mount.8  Mon Jul 26 12:48:45 2010
> @@ -269,12 +269,15 @@
>  The argument following the
>  .Fl t
>  is used to indicate the file system type.
> -The type
> -.Ar ffs
> -is the default.
> +If this option is omitted, then
> +.Nm
> +attempts to guess a file system type using the 
> +.Xr disklabel 5
> +and other information.
>  The
>  .Fl t
>  option can be used
> +to override this behavior and
>  to indicate that the actions should only be taken on
>  file systems of the specified type.
>  More than one type may be specified in a comma separated list.

This diff isn't quite right.  There are no disklabels on NFS
partitions; heck, there's no true disklabel on a MSDOS-only memory
stick.  The language you've written is too specific.

Reply via email to