Date: Tue, 24 Oct 2006 13:37:00 -0700 From: "Matthew Jacob" <lydianconcepts@gmail.com> To: "Michiel Boland" <michiel@boland.org> Cc: freebsd-current@freebsd.org Subject: Re: 'ro' option in fstab not recognized? Message-ID: <7579f7fb0610241337u10eceb27pba6adf65ebf19dab@mail.gmail.com> In-Reply-To: <Pine.GSO.4.64.0610242052300.17749@brakkenstein.nijmegen.internl.net> References: <Pine.GSO.4.64.0610242052300.17749@brakkenstein.nijmegen.internl.net>
next in thread | previous in thread | raw e-mail | index | archive | help
No, you're not stupid. This has been happening in 6 and -current for months now. I just haven't had time to figure out what got broken. You can fix it after mount by doing mount -u -o ro /usr/j/usr/local On 10/24/06, Michiel Boland <michiel@boland.org> 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? :) > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7579f7fb0610241337u10eceb27pba6adf65ebf19dab>