*BSD News Article 63792


Return to BSD News archive

#! rnews 2423 bsd
Newsgroups: comp.os.linux.development.system,comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.nla.gov.au!act.news.telstra.net!psgrain!newsfeed.internetmci.com!howland.reston.ans.net!ix.netcom.com!netcom.com!kalessin
From: Adam Megacz <kalessin@netcom.com>
Subject: Re: Ideal filesystem
Content-Type: text/plain; charset=us-ascii
Message-ID: <314C89B0.6673E487@netcom.com>
Sender: kalessin@netcom16.netcom.com
Content-Transfer-Encoding: 7bit
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
References: <4h7t5i$qoh@park.uvsc.edu> <DnoqB4.2sy@pe1chl.ampr.org> <glDH59i00YUvFFjspX@andrew.cmu. <314A470D.CCE53F0@netcom.com> <4ifob7$otg@gidora.kralizec.net.au>
Mime-Version: 1.0
Date: Sun, 17 Mar 1996 21:52:48 GMT
X-Mailer: Mozilla 2.0 (X11; I; Linux 1.2.13 i486)
Lines: 35
Xref: euryale.cc.adfa.oz.au comp.os.linux.development.system:19613 comp.unix.bsd.freebsd.misc:15634

Andrew Reilly wrote:
> 
> Adam Megacz <kalessin@netcom.com> wrote:
> >That's exactly what EA's are - the data is stored as a stream on the
> >disk, but the application sees it as a miniature filesystem - a
> >hierarchy.
> 
> And so the question has to be asked: "What's wrong with the filesystem
> hierarchy we have at the moment?"  (See my previous post on the Acorn
> RISC-OS solution to the resource fork problem.) 
Except that RISC-OS can't attach attributes to binary files that aren't applications (i.e., word
processor files, pixmaps, etc) an EA structure would be able to. BTW, we could implement EA's by
like thus: If you made a call to the kernel requesting to open the following file

    /usr/bin/groff//filetype

the kernel would return to you a stream containing the "filetype" EA on the file
"/usr/bin/groff". In other words, let's keep the existing file access commands - just extend the
syntax of a pathname to include EA's using "//" or some other character.  Just think of what we
could do with symlinks in EAs!!!


> If you go introducing resource
> forks or whatever, then you'll need something other than "tar" to do
> backups and file transfers.
Tar works just dandy in OS/2, and it saves all the EA's. I believe Tar has extra space allocated
in the file format for ACL's (Access Control Lists) that is *really* just a space for OS-specific
inode crap.

  - Adam

-- 
Adam Megacz <kalessin@netcom.com>
Website ftp://ftp.netcom.com/pub/ka/kalessin/adam.html
Linux - OS/2