src-test2/sbin/mount, branch release/5.2.0

Don't include the file system ID in the output of `mount -v' if it

2003-12-05T09:36:56Z

is all zeros. The kernel now consistently zeroes FSIDs for non-root users, so there's no point in printing these. Also fix a number of compiler warnings, including two real bugs: - a bracket placement bug caused `mount -t ufs localhost:/foo /mnt' to override the `-t ufs' specification and use mount_nfs. - an unitialised variable was used instead of _PATH_SYSPATH when warning that the mount_* program cound not be found. Submitted by: Rudolf Cejka (FSID part) Approved by: re (scottl)

style.Makefile: Add a '?' before '=' in WARNS.

2003-10-26T00:35:05Z

Reduce fstab(5)/mount(8) confusion by changing the man pages to say "ro"

2003-10-22T18:25:49Z

instead of "rdonly". "rdonly" works for mount(8) and mount_std(8) but not from /etc/fstab, whereas "ro" works for all mount_*(8) commands.

Prefer PATH_MAX to MAXPATHLEN. PATH_MAX has the trailing NUL.

2003-08-07T04:51:41Z

When mount(8) is invoked with the `-v' flag, display the filesystem

2003-07-18T17:43:13Z

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

Convert fsck and mount to using execvP to find fsck_foo and mount_foo.

2003-06-29T17:53:48Z

This simplifies the code path and makes the default path easy to override in the /rescue case. Submitted by: Tim Kientzle

Fixed the markup in the recently added ENVIRONMENT section.

2003-05-17T22:35:35Z

Use __FBSDID() to quiet GCC 3.3 warnings.

2003-05-03T18:41:59Z

Bump the date for recent commits.

2003-04-07T22:58:35Z

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

2003-04-07T14:21:14Z

Requested by: ru