Mention the various reasons for messages of the form:

xxxxx filesystem is not available

Inspired by:  PR 3311, and a following discussion with Mikhail
This commit is contained in:
Joerg Wunsch 1997-08-24 17:51:12 +00:00
parent e49f6a7c8d
commit 6caa839def
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=28658
2 changed files with 34 additions and 2 deletions

View File

@ -30,7 +30,7 @@
.\" SUCH DAMAGE.
.\"
.\" @(#)mount.8 8.8 (Berkeley) 6/16/94
.\" $Id: mount.8,v 1.15 1997/03/11 12:27:58 peter Exp $
.\" $Id: mount.8,v 1.16 1997/08/24 02:27:08 steve Exp $
.\"
.Dd June 16, 1994
.Dt MOUNT 8
@ -282,6 +282,22 @@ The file system object is to be read and write.
The options specific to NFS filesystems are described in the
.Xr mount_nfs 8
manual page.
.Sh DIAGNOSTICS
Various, most of them are self-explanatory.
.Pp
.Dl XXXXX filesystem is not available
.Pp
The kernel doesn't support the respective filesystem type. Note that
support for a particular filesystem might be provided either on a static
(kernel compile-time), or dynamic basis (loaded as a kernel module by
.Xr modload 8 ).
Normally,
.Nm
or its subprocesses attempt to dynamically load a filesystem module if
it hasn't been configured statically, using
.Xr vfsload 3 .
In this case, the above error message can also mean that you didn't
have permission to load the module.
.Sh FILES
.Bl -tag -width /etc/fstab -compact
.It Pa /etc/fstab

View File

@ -30,7 +30,7 @@
.\" SUCH DAMAGE.
.\"
.\" @(#)mount.8 8.8 (Berkeley) 6/16/94
.\" $Id: mount.8,v 1.15 1997/03/11 12:27:58 peter Exp $
.\" $Id: mount.8,v 1.16 1997/08/24 02:27:08 steve Exp $
.\"
.Dd June 16, 1994
.Dt MOUNT 8
@ -282,6 +282,22 @@ The file system object is to be read and write.
The options specific to NFS filesystems are described in the
.Xr mount_nfs 8
manual page.
.Sh DIAGNOSTICS
Various, most of them are self-explanatory.
.Pp
.Dl XXXXX filesystem is not available
.Pp
The kernel doesn't support the respective filesystem type. Note that
support for a particular filesystem might be provided either on a static
(kernel compile-time), or dynamic basis (loaded as a kernel module by
.Xr modload 8 ).
Normally,
.Nm
or its subprocesses attempt to dynamically load a filesystem module if
it hasn't been configured statically, using
.Xr vfsload 3 .
In this case, the above error message can also mean that you didn't
have permission to load the module.
.Sh FILES
.Bl -tag -width /etc/fstab -compact
.It Pa /etc/fstab