src/lib/libc/sys/mount.2, branch release/5.4.0

MFC 1.43 and 1.44:

2005-02-26T04:44:54Z

Do not mislead users into checking for a mount_ufs or mount_ufs2 manual page. They do not exist. PR: 53303 Submitted by: Marc Silver (original version)

Document the MNT_SNAPSHOT mount flag with a cross-reference

2004-08-13T14:33:03Z

to mksnap_ffs(8). PR: 70402 Submitted by: James Raftery

Markup, grammar, and spelling fixes.

2004-06-30T20:09:10Z

Add fairly minimal documentation for the nmount() syscall.

2004-03-16T09:45:38Z

In the !MNT_BYFSID case, return EINVAL from unmount(2) when the

2003-09-08T16:23:21Z

specified directory is not found in the mount list. Before the MNT_BYFSID changes, unmount(2) used to return ENOENT for a nonexistent path and EINVAL for a non-mountpoint, but we can no longer distinguish between these cases. Of the two error codes, EINVAL was more likely to occur in practice, and it was the only one of the two that was documented. Update the manual page to match the current behaviour. Suggested by: tjr Reviewed by: tjr

Add a new mount flag MNT_BYFSID that can be used to unmount a file

2003-07-01T17:40:23Z

system by specifying the file system ID instead of a path. Use this by default in umount(8). This avoids the need to perform any vnode operations to look up the mount point, so it makes it possible to unmount a file system whose root vnode cannot be looked up (e.g. due to a dead NFS server, or a file system that has become detached from the hierarchy because an underlying file system was unmounted). It also provides an unambiguous way to specify which file system is to be unmunted. Since the ability to unmount using a path name is retained only for compatibility, that case now just uses a simple string comparison of the supplied path against f_mntonname of each mounted file system. Discussed on: freebsd-arch mdoc help from: ru

Separate the description of the flags for mount(2) and unmount(2)

2003-06-30T22:22:12Z

to clarify which system call accepts which arguments. Previously the manual page gave the impression that calling unmount() with flags of (MNT_FORCE | MNT_UPDATE | MNT_RDONLY) would downgrade a read-write mount to read-only, which is clearly untrue; to do that, these flags should be passed to mount() instead.

mdoc(7) police: markup laundry.

2003-02-23T01:47:49Z

Mention the oddities and requirements for mount operations executed by

2003-01-13T19:42:21Z

non-root users. PR: docs/42651 Submitted by: Thomas Seck MFC after: 3 days

mdoc(7) police: "The .Fa argument.".

2002-12-19T09:40:28Z