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_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? :) > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" >Received on Tue Oct 24 2006 - 18:37:07 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:01 UTC