Re: Respawn crashed PUFFS filesystems?

[Mouse <mouse%Rodents-Montreal.ORG@localhost>]

>> Is there any way it could be set as an option at mount time?
> The problem is that mount(8) passes the options verbatim to
> /sbin/mount_xxx, which is supposed to start the xxx filesystem.  The
> filesystem will parse the options on its own before passing
> appropriate flags to mount(2). We have no way to make sure a third
> party software will not choke on an unexpected option, and no way to
> make it pass the option to mount(2).

As for "choke on an unexpected option", well, third-party software can
choke for any reason or none.  But I don't see any reason we can't
document this as one of the likely options and let anyone who doesn't
handle it, or doesn't pass it back at mount(2) time, deal with user
censure for not supporting a useful and easy-to-support facility.

Alternatively....

This could be useful in other contexts, from post-unmount cleanup in
general to auto-remount of non-puffs filesystems.  Perhaps it's
appropriate to add vfsctl(2), with an option which can set a "run this
on unmount" command?  Or maybe a "wait for unmount" operation?

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
 X  Against HTML                mouse%rodents-montreal.org@localhost
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B