From a90ba4da61f444336378b0013025e5307d9368fc Mon Sep 17 00:00:00 2001
From: joerg <joerg@FreeBSD.org>
Date: Sun, 24 Aug 1997 17:51:12 +0000
Subject: Mention the various reasons for messages of the form:

	xxxxx filesystem is not available

Inspired by:  PR 3311, and a following discussion with Mikhail
---
 sbin/mount/mount.8 | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)

(limited to 'sbin/mount')

diff --git a/sbin/mount/mount.8 b/sbin/mount/mount.8
index c9ef374..ca26529 100644
--- a/sbin/mount/mount.8
+++ b/sbin/mount/mount.8
@@ -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
-- 
cgit v1.1