Hans,
At 18:30 28/10/2000, Hans Reiser wrote:
>Anton Altaparmakov wrote:
> > You can't possibly have both using the same API since you would then get
> > name collision on filesystems where both named streams and EAs are
> > supported. (And I haven't even mentioned EAs and named streams attached to
> > actual _real_ directories yet.)
>
>filename/atomic/1
>filename/1
>
>no collision here, and SAMBA or whatever can make filename/1 look like
>filename:1 or whatever you
>want.
What about the case where in your example "filename" is a directory? - How
do you propose to handle that there might be a directory called atomic
inside directory filename and there might be a file with the name 1 inside
both directories (filename and filename/atomic) and at the same time the
named stream 1 exists attached to the directory filename and the EA 1
exists as well?
Given above scenario:
How would you distinguish the file filename/1 from the named stream filename/1?
And how would you distinguish file filename/atomic/1 from EA filename/atomic/1
In both cases the string looks the same to me... and I don't see how this
would work.
Also if EAs were to be implemented as extended files/directories, do you
then suggest to use file/directory operations to work with them? (i.e.
open, read, write, close). - If yes, I would think that this is inferior to
the current API proposal where you have direct EA operations (ATR_*). - As
other people have said EAs are more like environment variables than
anything else and the API should be consistent with that. - Also how would
you handle operations on several/all EAs at once? - It would not seem
possible to do any more if file ops are used? - Or have I misunderstood
your proposal?
Regards,
Anton
--
"Education is what remains after one has forgotten everything he
learned in school." - Albert Einstein
--
Anton Altaparmakov Voice: +44-(0)1223-333541(lab)
Christ's College eMail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
Cambridge CB2 3BU ICQ: 8561279
United Kingdom WWW: http://www-stu.christs.cam.ac.uk/~aia21/
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
