Date: Mon, 18 Feb 2008 13:50:34 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Yar Tikhiy <yar@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern vfs_mount.c Message-ID: <86y79i5syt.fsf@ds4.des.no> In-Reply-To: <200802141704.m1EH4VL4099009@repoman.freebsd.org> (Yar Tikhiy's message of "Thu\, 14 Feb 2008 17\:04\:31 %2B0000 \(UTC\)") References: <200802141704.m1EH4VL4099009@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Yar Tikhiy <yar@FreeBSD.org> writes: > Log: > 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.) >=20=20=20 > 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.) Can you guarantee that this will not f*** up the bootp / dhcp + nfsroot case? There are dragons in that code which were decidedly not funny to track down and fix. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86y79i5syt.fsf>