On 30/06/2004, at 4:40 PM, Chris Zumbrunn wrote:
On 30. Jun 2004, at 3:01, Alasdair Lumsden wrote:
While Mach is derived from 4.3BSD (circa 1986~1988), there's been
about
15 years worth of divergence since then. For example, FreeBSD is
monolithic while Mach is more micro-kernel based. Also the dri
On 01/07/2004, at 12:25 PM, Sam Lawrance wrote:
This is unexpected. You can successfully mount the snapshot
read/write and create and write to files in that snapshot. You can
also write to files that existed in the snapshot prior to mounting it
read/write.
Perhaps the writing is done from a point
> This is unexpected. You can successfully mount the snapshot
> read/write and create and write to files in that snapshot. You can
> also write to files that existed in the snapshot prior to mounting it
> read/write.
Perhaps the writing is done from a point where the schg flag is not
checked
> > Has anyone looked at this? Does anyone have any comments?
> >
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/50827
>
> I don't think you'll ever find anyone interested in file locking
> anymore. Since they're all advisory, anyway, you can just implement them
> at a higher level in your a
It was mentioned earlier this week that UFS2 snapshots could somehow be
mounted read/write and then written to. I noticed this a few weeks ago
but didn't think much of it.
I have reproduced this:
mksnap_ffs / /snap1
mkdir /snapmount
mdconfig -a -t vnode -f /snap1 -u 4
mount -r /dev/md4 /snapmou
5 matches
Mail list logo
