| To: | yyy@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: File system namespace resolution proposal |
| From: | "Clive D.W. Feather" <yyyyy@xxxxxxxxx> |
| Date: | Mon, 26 Feb 2001 10:10:27 +0000 |
| Cc: | yyyyy@xxxxxxxxxxxx, yyyyyyyyyyyyyy@xxxxxxxxxxxxx |
| References: | <200102240503.VAA06637@spartan.eng.sun.com> |
yyy@xxxxxxxxxxxxxxxxxxx said: >>>> Problem Statement: >>>> Current system implementors are looking for ways to associate extended >>>> attributes with files in the file system namespace. [...] > It isn't a kludge to allow one particular implementation. Then what is it for ? If it's purely a reserved namespace for the implementation, then I can agree that we should reserve such a space. The best proposal I've seen so far is that names beginning ".#" (dot then hash) are reserved. However, reserving such a namespace says *nothing* about making such files special in any way; it's merely a set of names that the application programmer and user must avoid. *IF* the proposal includes giving these files special semantics (e.g. they get deleted automatically when rmdir() is called) then I'm much less happy with the idea. I would want to see very specific proposals. -- Clive D.W. Feather | Work: <yyyyy@xxxxxxxxx> | Tel: +44 20 8371 1138 Internet Expert | Home: <yyyyy@xxxxxxxxxx> | Fax: +44 20 8371 1037 Demon Internet | WWW: http://www.davros.org | DFax: +44 20 8371 4037 Thus plc | | Mobile: +44 7973 377646 |
| Previous by Date: | Re: File system namespace resolution proposal, Clive D.W. Feather |
|---|---|
| Next by Date: | Re: File system namespace resolution proposal, schilling |
| Previous by Thread: | Re: File system namespace resolution proposal, dwc |
| Next by Thread: | Re: File system namespace resolution proposal, Stefan Monnier |
| Indexes: | [Date] [Thread] [All Lists] |