What does the following mean?
nwa is 262298 but invis track starts blk 0
cdfs: nwa from drive 0 != computed nwa 262,146
be careful! assuming computed nwa
Previously using a disk that came up with this error led to what
looked like corrupted data (I was able to ign
On 1 December 2015 at 03:24, arisawa wrote:
> current kernel allows unmount even if after rfork m.
> this feature makes sandboxing difficult.
> can anyone explain this feature is necessary?
>
For some applications, similar to ftp or http, I've built a name space
somewhere and then bound that to
I said:
> 2015/12/01 12:24、arisawa のメール：
>
> Hello 9fans,
>
> current kernel allows unmount even if after rfork m.
> this feature makes sandboxing difficult.
> can anyone explain this feature is necessary?
>
> Kenji Arisawa
I make a protection for unmounting after rfork -m and now testing.
my
