Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!act.news.telstra.net!vic.news.telstra.net!news.mira.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.uwa.edu.au!disco.iinet.net.au!news.tower.com.au!news.it.com.au!nexus.it.com.au!nexus.it.com.au!not-for-mail
From: sjm@it.com.au (Simon Mackinlay)
Newsgroups: comp.os.linux.development.system,comp.unix.bsd.freebsd.misc
Subject: Re: Ideal filesystem
Followup-To: comp.os.linux.development.system,comp.unix.bsd.freebsd.misc
Date: 3 Apr 1996 17:46:04 +0800
Organization: Deliberately disorganised.
Lines: 36
Message-ID: <4jthcs$3dn@nexus.it.com.au>
References: <4gejrb$ogj@floyd.sw.oz.au> <3140C968.20699696@netcom.com> <4ia7im$i4m@usenet.srv.cis.pitt.edu> <4if9gb$4kh@park.uvsc.edu> <4iibd2$ng@EARTH.baylor.edu> <4ir7tc$5uf@park.uvsc.edu> <31530CC6.266C03EF@ids2.idsonline.com> <4j0ccn$ftv@park.uvsc.edu>
NNTP-Posting-Host: localhost
X-Newsreader: TIN [UNIX 1.3 950515BETA PL0]
Xref: euryale.cc.adfa.oz.au comp.os.linux.development.system:20662 comp.unix.bsd.freebsd.misc:16632
[On cold.system, Terry Lambert (terry@lambert.org) bellowed unto all...]
{snip snip snip}
> I don't understand why a resource file for an application must
> have a seperate entry in the file system name space. An EA,
> after all, is a sub-namespace that is *not* exported into the
> general file system namespace.
{snip snip snip}
I don't understand why people are considering changes
to the underlying filing system when it's fairly obvious
that the answer to maintaining meta data lies in a well
designed and written library.
A good API for maintaining meta data will _free_ you from
the specifics of how that data is physically stored;
anyone with any experience with databases certainly ought
to know this.
Who would like to explain to me how to centralise meta
data in a networked environment, when meta data is stored
in streams on disks? I don't care which machine in the
lab I use, but I'm buggered if I want my desktop to walk
about when I change seats.
A good library for meta data manipulation deals with this
gracefully - simply allow it to know about users, and
hosts in the metaopen() call.
I haven't seen a good argument for streamed files yet
that stands against the force of argument for putting the
required functionality into a common library.
--
Simon (sjm@it.com.au)
strength through elegance /// beauty in intelligence