[OpenAFS-devel] Re: on sockets and devices in AFS

[Derrick Brashear]

The point of not writing back is that it can be done today without protocol c=
hange. No issue of what unsuspecting clients see, because what they see is .=
.. nothing.

On Sep 16, 2010, at 3:53 PM, Andrew Deason <adeason@sinenomine.net> wrote:

> On Thu, 16 Sep 2010 07:53:59 -0400
> chas williams - CONTRACTOR <chas@cmf.nrl.navy.mil> wrote:
>=20
>> On Thu, 16 Sep 2010 09:58:22 +0200
>> Derrick Brashear <shadow@dementia.org> wrote:
>>=20
>>=20
>>> 2) if created locally they would cover a later file of the same name
>>> if one is created
>>=20
>> how about a new 'file type' that is 'special' just like mounts.
>> however, they would only have a local (to the client host)
>> meaning.  old clients would see 'files' (with a strange prefix i
>> guess) and new clients would be able to handle these things as special
>> devices (named pipes and the like).
>=20
> Old clients could write stuff to that file, though, which is also thus
> hidden from new clients. Unless you add knowledge about the special
> prefix or whatever to the fileserver, prohibiting such.
>=20
> We can't create an actual new file type? (as in, an
> AFSFetchStatus.FileType type)
>=20
> --=20
> Andrew Deason
> adeason@sinenomine.net
>=20
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel