>> Solving this is not trivial, I don't think changing the panic() to
>> return(appropriate_error_code) is the rigth thing to do, in some
>> case you want to panic if a filesystem gets corrupted.
> [...consider / or /usr...]
I think an error return is preferable to a panic, during the mount
operation. During normal operation, it seems to me that the right
thing is to panic if the mount was done by root and to do the
forcible-unmount thing if non-root. (This arguably should be a mount
option which is forced on for non-root mounts, so that root mounts can
get the force-unmount semantics if desired.)
der Mouse
mo...@rodents.montreal.qc.ca
7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
