--HlL+5n6rz5pIUxbD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Mar 30, 2002 at 04:24:43PM +0100, Reinoud Zandijk wrote:
>=20
> What about a filesystem specific callback function for name comparison? =
=20
> then the filesystems who would want such a comparisation done in one way =
or
> another can do it their way... another option would offcource be to speci=
fy
> a standard comparisation method in the filingsystems structure given to t=
he
> kernel.... then `most common' ones can be shared.

Now you have the problem reversed, I think.

We want a case-independent view of a case-obeying filesystem, so that we can
(on the server) treat a Unix filesystem like, say, a MS-DOS machine wants to
see it, is this right?

Filesystems that define a charset and case-mapping procedure (like the
different Adosfs flavours, and msdosfs) are already doing so.

Now - what seems to be the right thing to me - certainly the right
intermediate solution until a "right" method of associating a character=20
encoding with a file name space has been defined - is to write a small
intermediate layer to do the mapping you want. Then mount it on top of
your Unixoid file system.

The backside would be that the result would not be case preserving, but
I suspect we can live with that. Actually, I suspect it is even possible
to write it case preserving with not much more effort.

Adosfs and friends are fine right now - they work how they are specified in=
=20
their original OS's and create the same bits. Best leave it alone, unless y=
ou
have a very good reason.

Regards,
	-is

--HlL+5n6rz5pIUxbD
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: 2.6.i

iQEVAgUBPKq+RzCn4om+4LhpAQEevQf/cwb1gnHGtLZkVYDBOvWd2tC2OmIBQvo/
M3yUUPHHyGE3pzUt43rAKELM+0KS2Utu3OfGVxhs9W7fKZSm44ZtnM5Jop6WXLwz
CoZD1/9v6fmTTzjKnv1JuUFTHREKe6HItietG1DeUmQAvtIyUqMJWZy7bAHtaxpC
FkIWDL4twZ0VOJg/IKyB+3C1mEj0H4eicXP0fvGpcUGTTWGA94LsshfRDDeSaEp2
vS1PsKLTLFD6BmSZfsjhRE3RPyG7N1I/1Ylp75H4iMXhH+wT0pX9I3lHpTd2TS4v
xx8Lx4qYAQEm2uxyqGPs1uQNd+8B6+COyf+gxwnRMIBVXoFqTGLDew==
=CLNb
-----END PGP SIGNATURE-----

--HlL+5n6rz5pIUxbD--