Christian S.J. Peron wrote: >>Hi everybody, >>due to limited connectivity in August, I've been able to >>update my -CURRENT box only yesterday since the first days of August >>(iirc). >> >>I noticed that mdconfig -a -t vnode -f ${myfile} isn't working anymore >>when ${myfile} is on a read-only filesystem: >> >>sberta:/usr/local/freesbie-clone/uzip# mdconfig -a -t vnode -f usr.uzip >>md0 >>sberta:/usr/local/freesbie-clone/uzip# mdconfig -d -u 0 >>sberta:/usr/local/freesbie-clone/uzip# mount -fru /usr >>sberta:/usr/local/freesbie-clone/uzip# mdconfig -a -t vnode -f usr.uzip >>mdconfig: ioctl(/dev/mdctl): Read-only file system >> >>This makes impossible to use compressed filesystems on devices like >>cdrom or read-only diskless environment. Any idea? I'm using: >> >>FreeBSD sberta.saturnero.sat 7.0-CURRENT FreeBSD 7.0-CURRENT #2: Sat Aug 27 18:1 >>5:39 CEST 2005 satu at sberta.saturnero.sat:/usr/obj/usr/src/sys/SBERTA i386 >>sberta:/usr/local/freesbie-clone/uzip# >> >>Bye and thanks in advance, >>Dario >> > > > Come to think about it, -o readonly isnt going to help. the bottom line is, > if the backing store is readonly, it should never be possible to write to it. -o readonly seems to help: # mdconfig -a -t vnode -f usr.uzip mdconfig: ioctl(/dev/mdctl): Read-only file system # mdconfig -a -t vnode -o readonly -f usr.uzip md0 Anyway, imho, the readonly option should be automatically set if the backing store is readonly. Otherwise, this behaviour should be well documented in mdconfig(8) and/or md(4). Bye and thanks, Dario -- Dario Freni (saturnero_at_freesbie.org) FreeSBIE developer (http://www.freesbie.org) GPG Public key at http://www.saturnero.net/saturnero.asc
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:42 UTC