Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!pro-beagle.cts.com!mmunz
From: mmunz@pro-beagle.cts.com (Mark Munz)
Newsgroups: comp.sys.apple
Subject: Re: A Shrinkit(tm) reply..
Message-ID: <8910222319.AA22736@trout.nosc.mil>
Date: 22 Oct 89 21:16:10 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 16

Network Comment: to #11990 by gem.mps.ohio-state.edu!uakari.primate.wisc.edu!uwm.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!krb20699@tut.cis.ohio-state.edu


>     I think I can stand to use a simple NuFX archiver, regardless 
> of how spiffy it is.  I'd actually prefer less overhead as long as 
> it did the actual job well.  Resource-fork archiving isn't a major 
> issue.  The only forked files I've ever seen have been CDEVS.  
> I'll admit, if you archive CDEVs a lot, resource-support is 
> necessary.  Otherwise...

True, currently there aren't many applications using resources, but 
my guess is that will change in the future. More products will utilize
resources wherever possible..  so although resource-fork archiving isn't
that important RIGHT NOW, it is definitely needed in the very near future.

Mark Munz