Article View: comp.sys.powerpc
Article #2496Re: Macintosh Resource Forks and the BeBox
From: Frank NIchols
Date: Tue, 24 Oct 1995 21:06
Date: Tue, 24 Oct 1995 21:06
17 lines
1534 bytes
1534 bytes
John Millington wrote: > Why not? By combining the forks, we could get back to a single-fork (i.e. > more "conventional" *shudder*) file system. No? Whats the point? All the various methods have pros and cons. None are obviously so much better than any other that it wins hands down. The only legitimate argument I have seen so far is that transfering files between systems with differing file structures is a PITA. So, how does this solution solve that? The destination system still has to have knowledge of the file structure it is looking at so it can figure out which parts it can/wants to use. Seems we are no better off with a single composite file structure than with the others being tossed about. I would like to suggest that we do away with files all together and move on to a object soup. Frank N
Technical Details
Message-ID:
<46k9if$keu@engineer.mrg.uswest.com>Path:
arc1-ca.pugleaf.net!engineer.mrg.uswest.com!usenetReferences:
<467ikg$fhf@dsm6.dsmnet.com> <davidf-2010951350480001@umslts1_63.umsl.edu> <60564050@sloppy.rt66.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!engineer.mrg.uswest.com!usenet From: Frank NIchols <"frank_nichols-contractor@msmgate"@msg.uswest.com> Newsgroups: comp.sys.powerpc,comp.sys.amiga.programmer,comp.sys.amiga.advocacy,comp.sys.mac.advocacy Subject: Re: Macintosh Resource Forks and the BeBox Date: Tue, 24 Oct 1995 21:06:06 +0000 Organization: U S WEST Marketing Resources Message-ID: <46k9if$keu@engineer.mrg.uswest.com> References: <467ikg$fhf@dsm6.dsmnet.com> <davidf-2010951350480001@umslts1_63.umsl.edu> <60564050@sloppy.rt66.com> NNTP-Posting-Host: invddp-10.mrg.uswest.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 2.0b1 (Macintosh; I; 68K)