| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
NMOUNT has gone together with static mount table in 4.3BSD-Reno.
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the jail(8) command. [10:04]
Fix a one-NUL-byte buffer overflow in libopie. [10:05]
Correctly sanity-check a buffer length in nfs mount. [10:06]
Approved by: so (cperciva)
Approved by: re (kensmith)
Security: FreeBSD-SA-10:04.jail
Security: FreeBSD-SA-10:05.opie
Security: FreeBSD-SA-10:06.nfsclient
|
| |
|
|
|
|
|
|
| |
clause.
# If I've done so improperly on a file, please let me know.
|
|
|
|
| |
Noticed by: ru, who else? :)
|
|
|
|
|
|
|
| |
page. They do not exist.
PR: 53303
Submitted by: Marc Silver <marcs@draenor.org> (original version)
|
| |
|
| |
|
|
|
|
|
|
|
| |
to mksnap_ffs(8).
PR: 70402
Submitted by: James Raftery <james@now.ie>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
non-root users.
PR: docs/42651
Submitted by: Thomas Seck <tmseck@netcologne.de>
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Stop calling system calls "function calls".
Use "The .Fn system call" a-la "The .Nm utility".
When referring to a non-BSD implementation in
the HISTORY section, call syscall a function,
to be safe.
|
|
|
|
| |
Approved by: re
|
| |
|
|
|
|
| |
Submitted by: yar
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
initially suggested by mdoc(7) style, but was broken over the years
|
|
|
|
| |
More libraries manpages updates following.
|
| |
|
|
|
|
|
|
|
| |
error for a pathname to contain a character with the high-order
bit set.
Inspired by: joerg's previous commit
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
track.
The $Id$ line is normally at the bottom of the main comment block in the
man page, separated from the rest of the manpage by an empty comment,
like so;
.\" $Id$
.\"
If the immediately preceding comment is a @(#) format ID marker than the
the $Id$ will line up underneath it with no intervening blank lines.
Otherwise, an additional blank line is inserted.
Approved by: bde
|
|
|
|
|
| |
Submitted by: Markus Friedl <markus.friedl@informatik.uni-erlangen.de>
via OpenBSD
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Obtained from: Whistle Communications tree
Add an option to the way UFS works dependent on the SUID bit of directories
This changes makes things a whole lot simpler on systems running as
fileservers for PCs and MACS. to enable the new code you must
1/ enable option SUIDDIR on the kernel.
2/ mount the filesystem with option suiddir.
hopefully this makes it difficult enough for people to
do this accidentally.
see the new chmod(2) man page for detailed info.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ever since I first say the way the mount flags were used I've hated the
fact that modes, and events, internal and exported, and short-term
and long term flags are all thrown together. Finally it's annoyed me enough..
This patch to the entire FreeBSD tree adds a second mount flag word
to the mount struct. it is not exported to userspace. I have moved
some of the non exported flags over to this word. this means that we now
have 8 free bits in the mount flags. There are another two that might
well move over, but which I'm not sure about.
The only user visible change would have been in pstat -v, except
that davidg has disabled it anyhow.
I'd still like to move the state flags and the 'command' flags
apart from each other.. e.g. MNT_FORCE really doesn't have the
same semantics as MNT_RDONLY, but that's left for another day.
|
|
|
|
| |
Pointed out by: bde
|
|
|
|
|
| |
changed sysctl to lsvfs as "sysctl vfs" doesn't return a listing of
possible filesystem names
|
|
|
|
| |
and Lite1 or earlier reality for the 4th arg.
|
|
|
|
|
| |
- add undelete() and undelete.2 (requires libc minor bump some time)
- man page updates
|
| |
|
| |
|
| |
|
|
|
|
|
| |
say is means that a pathname had the high-order bit
set, since this is no longer an error.
|
| |
|
|
|
|
|
|
|
|
|
| |
dealing w/the fixit floppy.
Also added the MNT_RELOAD, MNT_WANTRDWR, MNT_ASYNC, MNT_NOATIME,
MOUNT_UNION flags. Someone might want to check my description of MNT_RELOAD.
2.2-R candidate. Not a 2.1.6-R candidate -- some current flags aren't in
2.1.5-R's version.
|
|
|
|
|
|
|
|
| |
in a bunch of man pages.
Use the correct .Bx (BSD UNIX) or .At (AT&T UNIX) macros
instead of explicitly specifying the version in the text
in a bunch of man pages.
|
|
|