From owner-freebsd-current@FreeBSD.ORG Tue Oct 24 22:06:13 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8580916A403 for ; Tue, 24 Oct 2006 22:06:13 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0986F43D5A for ; Tue, 24 Oct 2006 22:06:11 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 198E25E18; Wed, 25 Oct 2006 02:06:10 +0400 (MSD) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id 0FACA5DD4; Wed, 25 Oct 2006 02:06:10 +0400 (MSD) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id k9OM6AU7001328; Wed, 25 Oct 2006 02:06:10 +0400 (MSD) (envelope-from ru) Date: Wed, 25 Oct 2006 02:06:10 +0400 From: Ruslan Ermilov To: Matthew Jacob Message-ID: <20061024220610.GB929@rambler-co.ru> References: <7579f7fb0610241337u10eceb27pba6adf65ebf19dab@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="K8nIJk4ghYZn606h" Content-Disposition: inline In-Reply-To: <7579f7fb0610241337u10eceb27pba6adf65ebf19dab@mail.gmail.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: Michiel Boland , freebsd-current@freebsd.org Subject: Re: 'ro' option in fstab not recognized? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Oct 2006 22:06:13 -0000 --K8nIJk4ghYZn606h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 24, 2006 at 01:37:00PM -0700, Matthew Jacob wrote: > No, you're not stupid. This has been happening in 6 and -current for > months now. >=20 I cannot reproduce it on RELENG_6. On -CURRENT indeed there was a problem; I've just fixed it backing out rev. 1.86 to mount.c, see the commit log for details. > I just haven't had time to figure out what got broken. >=20 > You can fix it after mount by doing >=20 > mount -u -o ro /usr/j/usr/local >=20 >=20 > On 10/24/06, Michiel Boland wrote: > >Hi. I must be extremely stupid. I have this in my fstab > > > >/usr/local /usr/j/usr/local nullfs ro 0 0 > > > >but /usr/j/usr/local still appears to be mounted read-write. > > > >Oh wait, I guess this is also already covered by PR 100164. > > > >Line 197 of sys/mount/mount.c explicitly adds an option "noro". > >Looks to me like this makes it impossible to mount *any* file system > >read-only, except by explicitly passing flags to mount. > >Surely this is not what fstab was designed for? :) Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --K8nIJk4ghYZn606h Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFPo5SqRfpzJluFF4RAvDUAJwO6rP05pcFBA877eihNcEgdLqe+gCffwB7 3gizIEAc5rIqyC5Frfu7U6U= =6Pt7 -----END PGP SIGNATURE----- --K8nIJk4ghYZn606h--