Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for manpage 'mount(8)'

This is an experimental report containing PRs for manpage 'mount(8)' as of Sun Apr 20 07:38:03 2014 UTC. See notes.


PRs for manpage 'mount(8)':
SSubmittedTrackerResp.Description
o2013/04/01arm/177538armtunefs(8) and mount(8) can not access a newfs(8)'d filesystem (clang, EABI).
o2010/05/13bin/146543[patch] mount(8): securelevel does not affect mount (duplicate of kern/22142)
p2009/10/15bin/139651fs[nfs] mount(8): read-only remount of NFS volume does not work
o2008/11/24kern/129152fs[panic] non-userfriendly panic when trying to mount(8) non-existing or wrong rootdev
o2008/09/01kern/127029fs[panic] mount(8): trying to mount a write protected zip disk panics the machine (unless the -r flag is used)
o2007/08/09bin/115361fs[zfs] mount(8) gets into a state where it won't set/unset ZFS properties (atime, exec, setuid)
o2007/06/18bin/113838fs[patch] [request] mount(8): add support for relative pathnames
o2007/04/21bin/111978[patch] [request] make syspath list for mount(8) configurable at runtime
o2005/07/29bin/84298[patch] allow mount(8) to recognize relative pathnames as mountpoints
o2005/06/08bin/82037mount(8)/unmount(8)/fsck(8) mount point specification inconsistency.
o2003/10/24bin/58483[patch] mount(8): allow type special or node relative names
s2002/09/29bin/43497mount(8): mount -t nfs -> crunchgen incompatible
o2002/08/10bin/41526mount(8) symlinked mount points get mounted more than once w/ mount -a
o2001/10/29bin/31588change request to allow mount(8) to set the MNT_IGNORE flag
o2000/07/04bin/19683mount(8) displays incorrect mount point on failed mount
o1999/09/21bin/13882mount(8) mount -p is missing the quota options
16 problems total.


Notes

GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.

Please give feedback on this report to linimon@FreeBSD.org. Thanks.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.