| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
EINTEGRITY was previously documented as a UFS-specific error for
mount(2). This documents EINTEGRITY as a filesystem-independent error
that may be reported by the backing store of a filesystem.
While here, document EIO as a filesystem-independent error for both
mount(2) and posix_fadvise(2). EIO was previously only documented for
UFS for mount(2).
Reviewed by: mckusick
Suggested by: mckusick
MFC after: 2 weeks
Sponsored by: Chelsio Communications
Differential Revision: https://reviews.freebsd.org/D24168
Notes:
svn path=/head/; revision=359465
|
| |
|
|
|
|
|
|
|
|
|
|
| |
when a superblock check-hash error is detected. This change clarifies
a mount that failed due to media hardware failures (EIO) from a mount
that failed due to media errors (EINTEGRITY) that can be corrected by
running fsck(8).
Sponsored by: Netflix
Notes:
svn path=/head/; revision=358899
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The two options are
* nocover/cover: Prevent/allow mounting over an existing root mountpoint.
E.g., "mount -t ufs -o nocover /dev/sd1a /usr/local" will fail if /usr/local
is already a mountpoint.
* emptydir/noemptydir: Prevent/allow mounting on a non-empty directory.
E.g., "mount -t ufs -o emptydir /dev/sd1a /usr" will fail.
Neither of these options is intended to be a default, for historical and
compatibility reasons.
Reviewed by: allanjude, kib
Differential Revision: https://reviews.freebsd.org/D21458
Notes:
svn path=/head/; revision=352614
|
| |
|
|
|
|
|
|
|
|
| |
HISTORY section. Note: Any system calls that were added prior to v7,
but after v1 weren't changed.
Obtained from: http://www.tuhs.org/cgi-bin/utree.pl?file=V1/man/man2
Notes:
svn path=/head/; revision=326435
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Renumber cluase 4 to 3, per what everybody else did when BSD granted
them permission to remove clause 3. My insistance on keeping the same
numbering for legal reasons is too pedantic, so give up on that point.
Submitted by: Jan Schaumann <jschauma@stevens.edu>
Pull Request: https://github.com/freebsd/freebsd/pull/96
Notes:
svn path=/head/; revision=314436
|
| |
|
|
|
|
|
|
|
| |
NMOUNT has gone together with static mount table in 4.3BSD-Reno.
MFC after: 1 week
Notes:
svn path=/head/; revision=281470
|
| |
|
|
| |
Notes:
svn path=/head/; revision=274933
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=208586
|
| |
|
|
| |
Notes:
svn path=/head/; revision=203036
|
| |
|
|
|
|
|
|
|
| |
clause.
# If I've done so improperly on a file, please let me know.
Notes:
svn path=/head/; revision=165903
|
| |
|
|
|
|
|
| |
Noticed by: ru, who else? :)
Notes:
svn path=/head/; revision=142412
|
| |
|
|
|
|
|
|
|
|
| |
page. They do not exist.
PR: 53303
Submitted by: Marc Silver <marcs@draenor.org> (original version)
Notes:
svn path=/head/; revision=142349
|
| |
|
|
| |
Notes:
svn path=/head/; revision=140505
|
| |
|
|
| |
Notes:
svn path=/head/; revision=138188
|
| |
|
|
|
|
|
|
|
|
| |
to mksnap_ffs(8).
PR: 70402
Submitted by: James Raftery <james@now.ie>
Notes:
svn path=/head/; revision=133654
|
| |
|
|
| |
Notes:
svn path=/head/; revision=131365
|
| |
|
|
| |
Notes:
svn path=/head/; revision=127060
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=119885
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=117132
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
Notes:
svn path=/head/; revision=117089
|
| |
|
|
| |
Notes:
svn path=/head/; revision=111285
|
| |
|
|
|
|
|
|
|
|
|
| |
non-root users.
PR: docs/42651
Submitted by: Thomas Seck <tmseck@netcologne.de>
MFC after: 3 days
Notes:
svn path=/head/; revision=109186
|
| |
|
|
| |
Notes:
svn path=/head/; revision=108087
|
| |
|
|
| |
Notes:
svn path=/head/; revision=108040
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
Notes:
svn path=/head/; revision=108028
|
| |
|
|
|
|
|
| |
Approved by: re
Notes:
svn path=/head/; revision=107788
|
| |
|
|
| |
Notes:
svn path=/head/; revision=84306
|
| |
|
|
|
|
|
| |
Submitted by: yar
Notes:
svn path=/head/; revision=82642
|
| |
|
|
| |
Notes:
svn path=/head/; revision=79754
|
| |
|
|
| |
Notes:
svn path=/head/; revision=79531
|
| |
|
|
| |
Notes:
svn path=/head/; revision=77575
|
| |
|
|
| |
Notes:
svn path=/head/; revision=69051
|
| |
|
|
|
|
|
| |
initially suggested by mdoc(7) style, but was broken over the years
Notes:
svn path=/head/; revision=59954
|
| |
|
|
|
|
|
| |
More libraries manpages updates following.
Notes:
svn path=/head/; revision=59460
|
| |
|
|
| |
Notes:
svn path=/head/; revision=50476
|
| |
|
|
|
|
|
|
|
|
| |
error for a pathname to contain a character with the high-order
bit set.
Inspired by: joerg's previous commit
Notes:
svn path=/head/; revision=50466
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=48794
|
| |
|
|
|
|
|
|
| |
Submitted by: Markus Friedl <markus.friedl@informatik.uni-erlangen.de>
via OpenBSD
Notes:
svn path=/head/; revision=44484
|
| |
|
|
| |
Notes:
svn path=/head/; revision=38596
|
| |
|
|
| |
Notes:
svn path=/head/; revision=33515
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
Notes:
svn path=/head/; revision=31144
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
Notes:
svn path=/head/; revision=31132
|
| |
|
|
|
|
|
| |
Pointed out by: bde
Notes:
svn path=/head/; revision=31050
|
| |
|
|
|
|
|
|
| |
changed sysctl to lsvfs as "sysctl vfs" doesn't return a listing of
possible filesystem names
Notes:
svn path=/head/; revision=30963
|
| |
|
|
|
|
|
| |
and Lite1 or earlier reality for the 4th arg.
Notes:
svn path=/head/; revision=23862
|
| |
|
|
|
|
|
|
| |
- add undelete() and undelete.2 (requires libc minor bump some time)
- man page updates
Notes:
svn path=/head/; revision=23660
|
| |
|
|
| |
Notes:
svn path=/head/; revision=22527
|
| |
|
|
| |
Notes:
svn path=/head/; revision=22134
|
| |
|
|
| |
Notes:
svn path=/head/; revision=21907
|
| |
|
|
|
|
|
|
| |
say is means that a pathname had the high-order bit
set, since this is no longer an error.
Notes:
svn path=/head/; revision=21570
|