--Apple-Mail-3-425529632
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII; format=flowed


On Nov 20, 2004, at 1:30 PM, Chapman Flack wrote:

> When you claim a filesystem encoding for an agnostic filesystem, what 
> you're
> really doing is making an assertion.  Mounting an existing filesystem 
> and
> saying it's UTF8 doesn't make it so, just establishes that new names 
> will be
> encoded that way and existing names will be treated as encoded that 
> way unless
> invalid sequences are encountered, which would mean the assertion was 
> wrong.

Honestly, I think we need to reserve a chunk of space in the FFS 
superblock to specify the encoding that the file system is using.

         -- Jason R. Thorpe <thorpej@shagadelic.org>


--Apple-Mail-3-425529632
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQFBog1hOpVKkaBm8XkRAt/9AJ9VOed9feCD4vwPZpAk8olFYItb3gCgnL5e
QtbligH/NVqKL0KkJjsq9Gw=
=6i/Q
-----END PGP SIGNATURE-----

--Apple-Mail-3-425529632--