- Copy stable/10 (r259064) to releng/10.0 as part of the
10.0-RELEASE cycle.
- Update __FreeBSD_version [1]
- Set branch name to -RC1

[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so
start releng/10.0 at '100' so the branch is started with
a value ending in zero.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Add a sentence to the umount.8 man page to clarify the behaviour
for forced dismount when used on an NFS mount point. Requested by
Jeremy Chadwick.
This is a content change.

MFC after: 2 weeks

It's possible to unmount multiple items at once, make it clear.

Be more precise how to get fsids - 'mount -v' doesn't show fsids unless is run
by root.

Approved by: re (kib)

Remove advertising clause from University of California Regent's license,
per letter dated July 22, 1999.

Approved by: core, imp

s/considred/considered/

When mount(8) is invoked with the `-v' flag, display the filesystem
ID for each file system in addition to the normal information.

In umount(8), accept filesystem IDs as well as the usual device and
path names. This makes it possible to unambiguously specify which
file system is to be unmounted even when two or more file systems
share the same device and mountpoint names (e.g. NFS mounts from
the same export into different chroots).

Suggested by: Dan Nelson <dnelson@allantgroup.com>

mdoc(7) fixes: Fix the markup in the recently added ENVIRONMENT section.

Bump the date for recent commits.

Clarify the behavior of PATH_FSTAB with regard to 'tainted' execution.

Requested by: ru

Implement the '-F' option for mount & umount which allows the user to
specify an alternate fstab file.

s/filesystem/file system/g as discussed on -developers

The .Nm utility.

mdoc(7) police: removed HISTORY info from the .Os call.

Remove vestiges of MFS.

mdoc(7) police: use the new features of the Nm macro.

Clarify "mount -a -t" example - it only unmounts stuff in /etc/fstab.
Fix a typo.

PR: 19438
Submitted by: Eoin Lawless <eoin@maths.tcd.ie>
Reviewed by: sheldon

quoting << Martin_Blapp

- Completly changed the internals of umount(8). We do three
checks now to see if 'argv' is in the mounttable. It they
all fail, we return to main and print a warning.

- fixed the umount mount-order. The checks are rather complex
to do this. Cause umount(8) should also be able to unmount
several devices at once ('umount -a', 'umount -A',
'umount /mnt /mnt2'), the mount-order get's important.
I added checks to mark and unmark already unmounted devices.

- Various fixes with nfs-unmounts (no rpc-calls were done,
or they were done although there was an existing mount).
Since we allow overlay-mounts, we should also handle them
properly.

- Translate the deprecated nfs-syntax with '@' to ':' like
mount_nfs does. The ':' syntax has now precedence, but '@'
still works.

- 'umount -v' is now fixed for all cases and doesn't print
garbage like two times the mountpoint etc.

- removed non documented and useless umount '-F'.

- hanged nfsmounts can now unmounted 'without' any problems.
I've removed stat() and realpath() checks on the mountpoint.
Instead we just do a realpath() on the basedir of the
mountpath and add the dirname again.
Implemented this as an idea from phk. But there are still
vfs-restrictions if the nfs_mount is busy. If there are
unwritten metadata on a hanged nfs-mount, and we modify
nfs_vfsops.c to not return EBUSY, we get a deadlock :(
The problem has now moved from userland to kernel.

- removed the BUGS part from the umount(8) manpage.

- Converted it to ANSI C (more than 60% of the code have
changed).

Martin_Blapp

Fixed PR's
----------

o [1999/02/03] bin/9893 NFS umount of regular file impossible

s [1995/11/27] bin/841 stale nfs mounts cannot be umounted

o [1999/08/01] bin/12911 alfred NFS umounts are not properly done
if just the mountpoint gets umounted

Only partially solved:
----------------------

The problem is now in kernel:

o [1999/04/07] bin/11005 `umount -f' does not work if the
NFS-server is down.

PR: bin/9893 bin/841 bin/12911 bin/11005
Submitted by: Martin Blapp <mb@imp.ch>

$Id$ -> $FreeBSD$

Use errx() instead of err() for malloc failures. -Wall. Do not dot
terminate errx() string. Remove unused #includes. Use .Tn for NFS.

Fix a typo and while here cleanup the use of the .Nm macro.

PR: docs/4339
Submitted by: Matthew Hunt <mph@pobox.com>

Merge from Lite2.
- use new getvfsbyname() interface.
- new -A option, like -a except only mounted file systems are unmounted.

All non-cosmetic FreeBSD changes in umount.c, except ignoring of
realpath() failures, went away because they are done better in Lite2.
realpath() failures must be ignored so that non-pathnames like
"<above>:/foo" and "host:/bar" get as far as mount(2).

Reviewed by: dfr

From njw@cs.city.ac.uk (Nick Williams):

/sbin/umount does not return the correct exit status due to incorrect
logic in its internals.

Further, because of the nature of the code, you *cannot* use it to
umount a directory from a union mountpoint. Well, you can sometimes,
it depends on if the directory is at the top of the union stack or not :)

Submitted by: njw@cs.city.ac.uk (Nick Williams)

This commit was generated by cvs2svn to compensate for changes in r1558,
which included commits to RCS files with non-trunk default branches.

BSD 4.4 Lite sbin Sources

Note: XNSrouted and routed NOT imported here, they shall be imported with
usr.sbin.