| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
This unbreaks "/rescue/mount -t foo" -- previously it was necessary to
explicitly call "/rescue/mount_foo".
Hints from: gordon
X-MFC after: 3 days (if approved by re@)
|
|
|
|
|
|
|
| |
that it really wasn't intended as a security feature.
Wording mostly by: simon
Discussed with: secteam
|
| |
|
| |
|
|
|
|
| |
Noticed by: clement
|
|
|
|
| |
but allows a "nodev" in /etc/fstab, etc.
|
|
|
|
| |
Asked to commit by: phk
|
|
|
|
|
|
| |
front of it.
Reviewed by: phk
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
libufs, which only works for Charlie root.
This change reverts the introduction of libufs and moves the
check into the kernel. Since the f_fstypename is the same
for both ufs and ufs2, we check fs_magic for presence of
ufs2 and copy "ufs2" explicitly instead.
Submitted by: Christian S.J. Peron <maneo@bsdpro.com>
|
|
|
|
|
|
| |
per letter dated July 22, 1999.
Approved by: core, imp
|
|
|
|
|
|
|
| |
MAC support on the file system, if supported, which causes MAC to treat
each object as having its own label, rather than using a single label
for all objects on the file system. This doesn't have to be used in
combination with the tunefs/newfs flags -- it's an alternative.
|
| |
|
|
|
|
| |
Submitted by: "Christian S.J. Peron" <maneo@bsdpro.com>
|
| |
|
|
|
|
|
|
|
| |
more relevant manual pages.
PR: 62394
Submitted by: Marc Silver <marcs@draenor.org>
|
|
|
|
| |
Pointy hat to: pjd
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in those cases:
1. File system was mounted by an unprivileged user.
2. File system was mounted by an unprivileged root user.
3. File system was mounted by a privileged non-root user.
Point 1 is when file system was mounted by unprivileged user
(sysctl vfs.usermount was equal to 1 then).
Point 2 is when file system was mounted by root, while sysctl
security.bsd.suser_enabled is set to 0 and sysctl vfs.usermount
is set to 1.
Point 3 is because we want to be ready for capabilities.
Reviewed by: rwatson
Approved by: scottl (mentor)
|
|
|
|
| |
Submitted by: Ruslan Ermilov <ru@FreeBSD.org>
|
|
|
|
|
|
|
| |
with -o
Submitted by: Ruslan Ermilov <ru@FreeBSD.org>
Pointed out by: Ceri Davies <ceri@submonkey.net
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
| |
PR: bin/59144
Submitted by: Stefan Farfeleder <stefan@fafoe.narf.at>
|
| |
|
|
|
|
|
|
| |
instead of casting the unsigned 64-bit values to longs.
Suggested by: bde
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 <cejkar@fit.vutbr.cz> (FSID part)
Approved by: re (scottl)
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
This simplifies the code path and makes the default path easy to override
in the /rescue case.
Submitted by: Tim Kientzle <kientzle@acm.org>
|
| |
|
| |
|
| |
|
|
|
|
| |
Requested by: ru
|
|
|
|
| |
specify an alternate fstab file.
|
| |
|
|
|
|
|
|
|
|
| |
non-root users.
PR: docs/42651
Submitted by: Thomas Seck <tmseck@netcologne.de>
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
dump(8) issues are assumed to be fixed.
PR: 46224
Submitted By: Chris Knight <chris@aims.com.au>
Approved By: re (murray)
|
|
|
|
|
|
|
| |
mount option printing.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
| |
|
| |
|
|
|
|
|
| |
now don't try to load the filesystem module, the kernel takes
care of this.
|
|
|
|
|
|
|
|
|
|
| |
remove all the code which was trying to do so.
This code was nasty in several ways, it was hiding
the kernel bug where the kernel was unable to properly
load a module, and it was quitting if it wasn't able
to load the module. The consequence is that an ABI
breakage of the vfsconf API would have broken *every*
mount utility.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
kernel access control.
Teach mount(8) to understand the MNT_MULTILABEL flag, which is used
to determine whether a file system operates with individual per-vnode
labels, or treats the entire file system as a single object with a
single (mount) label. The behavior here will probably evolve some
now that nmount(2) is available and can more flexibly support mount
options.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
|
|
|
|
|
|
| |
PR: 30139
Submitted by: Chris Knight <chris@aims.com.au?
MFC after: 3 days
|
| |
|
| |
|
| |
|