> > What sort of fallback behaviour would you want in case of error here?
> Just let chroot() either succeed or fail. It's own "fallback behavior"
> in such a case should prove adequate. :)
Hmm. Failure to chroot == failure to start init?
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message