src-test/usr.bin/lsvfs, branch stable/7FreeBSD source treehttps://cgit-dev.freebsd.org/src-test/atom?h=stable%2F72007-11-15T15:18:44ZMFC: Increase string buffer to account for addition of "jail" to flags.2007-11-15T15:18:44ZStefan Eßerse@FreeBSD.org2007-11-15T15:18:44Zurn:sha1:55930f85a7fb5384291648c14ce06c4b48d54ce7
Approved by: re (ken)
Add security.jail.mount_allowed sysctl, which allows to mount and2007-04-05T21:03:05ZPawel Jakub Dawidekpjd@FreeBSD.org2007-04-05T21:03:05Zurn:sha1:f3a8d2f93ce69707ed05a48e89d884046f2d8a6a
unmount jail-friendly file systems from within a jail.
Precisely it grants PRIV_VFS_MOUNT, PRIV_VFS_UNMOUNT and
PRIV_VFS_MOUNT_NONUSER privileges for a jailed super-user.
It is turned off by default.
A jail-friendly file system is a file system which driver registers
itself with VFCF_JAIL flag via VFS_SET(9) API.
The lsvfs(1) command can be used to see which file systems are
jail-friendly ones.
There currently no jail-friendly file systems, ZFS will be the first one.
In the future we may consider marking file systems like nullfs as
jail-friendly.
Reviewed by: rwatson
spell "file system" correctly2005-01-24T20:06:16ZPhilippe Charniercharnier@FreeBSD.org2005-01-24T20:06:16Zurn:sha1:8a579692b2ca58249ada2d1429b45f83744c0219
Approved by: ru
Mechanically kill hard sentence breaks.2004-07-02T22:22:35ZRuslan Ermilovru@FreeBSD.org2004-07-02T22:22:35Zurn:sha1:6a3e8b0adc8c622ae61275a94d5d869980a68069Uniformly refer to a file system as "file system".2002-12-12T17:26:04ZRuslan Ermilovru@FreeBSD.org2002-12-12T17:26:04Zurn:sha1:8d5d039f80a8d31947f4e84af20e8a56d0009c32
Approved by: re
Add #include <sys/sysctl.h>. In my tree, mount.h includes2002-08-11T02:07:43ZMaxime Henrionmux@FreeBSD.org2002-08-11T02:07:43Zurn:sha1:24befda40b40b9a9c5a0e5b69203f909ab65300c
sysctl.h and I was depending on this namespace pollution.
Submitted by: jake
- Introduce a new struct xvfsconf, the userland version of struct vfsconf.2002-08-10T20:19:04ZMaxime Henrionmux@FreeBSD.org2002-08-10T20:19:04Zurn:sha1:5965373e69ca208cedd8ede9716ef0d58e6c3434
- Make getvfsbyname() take a struct xvfsconf *.
- Convert several consumers of getvfsbyname() to use struct xvfsconf.
- Correct the getvfsbyname.3 manpage.
- Create a new vfs.conflist sysctl to dump all the struct xvfsconf in the
kernel, and rewrite getvfsbyname() to use this instead of the weird
existing API.
- Convert some {set,get,end}vfsent() consumers to use the new vfs.conflist
sysctl.
- Convert a vfsload() call in nfsiod.c to kldload() and remove the useless
vfsisloadable() and endvfsent() calls.
- Add a warning printf() in vfs_sysctl() to tell people they are using
an old userland.
After these changes, it's possible to modify struct vfsconf without
breaking the binary compatibility. Please note that these changes don't
break this compatibility either.
When bp will have updated mount_smbfs(8) with the patch I sent him, there
will be no more consumers of the {set,get,end}vfsent(), vfsisloadable()
and vfsload() API, and I will promptly delete it.
Consistently use FBSDID2002-06-30T05:25:07ZDavid E. O'Brienobrien@FreeBSD.org2002-06-30T05:25:07Zurn:sha1:e026a48c34d396fe7d0e382673a69bc047c0bfcaMore consistancy. file system > filesystem2002-05-16T02:19:14ZTom Rhodestrhodes@FreeBSD.org2002-05-16T02:19:14Zurn:sha1:46c2a2cfa4db0a7969436da3293dedaadf750470Very minor whitespace nit.2002-04-28T12:36:56ZMark Murraymarkm@FreeBSD.org2002-04-28T12:36:56Zurn:sha1:900d70a0c0fb2ad8808649c13cd1286cfe15bc06