| To: | Jason Zions <yyyyyyyy@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: File system namespace resolution proposal |
| From: | "Clive D.W. Feather" <yyyyy@xxxxxxxxx> |
| Date: | Wed, 28 Feb 2001 09:05:53 +0000 |
| Cc: | "'yyyyyyyyy@xxxxxxxxxxxx'" <yyyyyyyyy@xxxxxxxxxxxx>, yyy@xxxxxxxxxxxxxxxxxxx, yyyyyyyyyyyyyy@xxxxxxxxxxxxx, yyyyyyy@xxxxxxxxxxxxxxxxxxxxx |
| References: | <87C80E823E824644BCB711D6348262B501378239@red-msg-05.redmond.corp.microsoft.com> |
Jason Zions said: >>>Fine, so those are properties of the filing system. The right place to put >>>them is in the inode - of course, you'd need extra functionality *or* extra >>>fields somewhere like "struct stat". >>If there was an istat() that can stat a specific inode and there is a >>st_ishadow (shadow inode) field in the main stat data you could hold such >>data inside a shadow inode. > > That assumes your filesystem is based on inodes. There are existing > POSIX-conforming implementations whose filesystems are not based on inodes. True. However, you could provide extra functionality - even based on struct stat - that worked no matter how it was implemented. -- 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: rand(), Andrew Josey |
|---|---|
| Next by Date: | Re: File system namespace resolution proposal, Clive D.W. Feather |
| Previous by Thread: | RE: File system namespace resolution proposal, Jason Zions |
| Next by Thread: | RE: File system namespace resolution proposal, Bruce Korb |
| Indexes: | [Date] [Thread] [All Lists] |