'ro' option in fstab not recognized?

[Ruslan Ermilov]

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.
> 
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.
> 
> You can fix it after mount by doing
> 
>  mount -u -o ro /usr/j/usr/local
> 
> 
> On 10/24/06, Michiel Boland <michiel at 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? :)


Cheers,
-- 
Ruslan Ermilov
ru at FreeBSD.org
FreeBSD committer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20061024/16ccb65e/attachment.pgp