summaryrefslogtreecommitdiffstats
path: root/lib/libc/stdlib/labs.c
diff options
context:
space:
mode:
authoryar <yar@FreeBSD.org>2008-02-14 17:04:31 +0000
committeryar <yar@FreeBSD.org>2008-02-14 17:04:31 +0000
commit9713f1f445b6ba1d2c2b46e10a1c5b61b5633763 (patch)
tree8e0a9bfa2af120bb39925453ef3dfe0268093ee8 /lib/libc/stdlib/labs.c
parent0e60a1b33c0d7b886460cc863fd7d1eddffef40f (diff)
downloadFreeBSD-src-9713f1f445b6ba1d2c2b46e10a1c5b61b5633763.zip
FreeBSD-src-9713f1f445b6ba1d2c2b46e10a1c5b61b5633763.tar.gz
In the new order of things dictated by nmount(2), a read-only mount
is to be requested via a "ro" option. At the same time, MNT_RDONLY is gradually becoming an indicator of the current state of the FS instead of a command flag. Today passing MNT_RDONLY alone to the kernel's mount machinery will lead to various glitches. (See the PRs for examples.) Therefore mount the root FS with a "ro" option instead of the MNT_RDONLY flag. (Note that MNT_RDONLY still is added to the mount flags internally, by vfs_donmount(), if "ro" was specified.) To be able to pass "ro" cleanly to kernel_vmount(), teach the latter function to accept options with NULL values. Also correct the comment explaining how mount_arg() handles length of -1. PR: bin/106636 kern/120319 Submitted by: Jaakko Heinonen <see PR kern/120319 for email> (originally)
Diffstat (limited to 'lib/libc/stdlib/labs.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud