--f0KYrhQ4vYSV2aJu
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jul 19, 2001 at 10:44:03AM +0200, Matthias Scheler wrote:
> On Thu, Jul 19, 2001 at 10:40:53AM +0200, Ignatios Souvatzis wrote:
> > There are other file systems with potential problems, if I recall right=
...
> > e.g., the DOS\0 and DOS\1 variants of adosfs, which always have some=20
> > metadata in their datablocks,
>=20
> It's DOS\0, DOS\2 and DOS\4 which have metadata in the data blocks.
>=20
> > ... so for this case, data copying always happens. (Chuck?)
>=20
> Does mmap() do that transperantly?

I don't remember ... that's why I wronte ``(Chuck?)'' above ('twas his code
that fixed DOS\0, only my alpha-testing). I might be able to just try one of
the next evenings. (Did I mention that I hate moving?)

> > Maybe we need to disable mmap()ing for such filesystems inside the kern=
el,
> > and make cp do the right thing if mmap fails? Is this possible?
>=20
> Sounds reasonable for "cp". But what about other applications?

Well, mmap() can always fail due to resource shortage, right? So an
application has to deal with it or fail in this case...

Regards,
	-is

--f0KYrhQ4vYSV2aJu
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iQEVAgUBO1afyTCn4om+4LhpAQFsQAf/YTVluzC15YZTnKIgDjEnVKo1o2S2xTq1
B+/1BTqGCD78C3Kh6owLa7zG6FrAksmKTGw9myaa3cJa4Exz+mejroM9IIqjfNHx
fsi586Bx65VbcsVamUryPakXiW/DMJG+xS7dPqWEiZ4myNxRWWmnTOccBjUD7BC4
Baq12wcxa7p8ltCJvFsPeni85o7AWwR46uCJIauJe6a0b7dojiGl9lLD05jYM/As
3atSc6nTN4IHExnYe08Okajpb57uxYKtYg9PKQAf+hDuer1SWhehFqcqj57GKe2L
qZQaeCcp0JVaZT+/r1po0SoPuJzhpGlCyFVUR/7n82pbBC6UGl/+CA==
=Mbxl
-----END PGP SIGNATURE-----

--f0KYrhQ4vYSV2aJu--