> So a filesystem might:

> 1.  Have a known filesystem encoding by virtue of being one of the fs types
>     that specify an encoding
> 2.  Have a known filesystem encoding, even though it is one of the agnostic
>     fs types, because that information has been given to mount
> 3.  Have no known filesystem encoding because it's agnostic and nothing was
>     specified to mount.

I like this.  (Well, I don't like it as much as I like a totally
encoding-agnostic interface like the traditional one, but it looks as
though NetBSD has decided it wants to change the filesystem interface
from octet sequences to character sequences, and this way at least I
can get it to operate with octet sequences if I want.)

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