Article View: comp.sources.bugs
Article #670Re: Problem with compress
From: Chip Salzenberg
Date: Sat, 18 May 1991 18:49
Date: Sat, 18 May 1991 18:49
14 lines
1166 bytes
1166 bytes
According to rickert@mp.cs.niu.edu (Neil Rickert):
> Am I alone in thinking that the way compress handles symlinks is just fine.
Apparently so.
>What I don't like is the way it handles hard links. What would be wrong with
>'compress foo' just creating the compressed 'foo.Z' and deleting 'foo', and
>'uncompress foo.Z' creating the uncompressed 'foo' and removing 'foo.Z'?
Compress has that behavior when invoked with the "-f" flag.
--
Brand X Industries Custodial, Refurbishing and Containment Service:
When You Never, Ever Want To See It Again [tm]
Chip Salzenberg <chip@tct.com>, <uunet!pdn!tct!chip>
Technical Details
Message-ID:
<2835774B.16DB@tct.com>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!rex!uflorida!screamer!tscs!tct!chipReferences:
<26085: May1416: 52: 3491@kramden.acf.nyu.edu> <1991May15.060236.26763@uunet.uu.net> <1991May15.173739.29874@mp.cs.niu.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!rex!uflorida!screamer!tscs!tct!chip From: chip@tct.com (Chip Salzenberg) Newsgroups: comp.sources.bugs,comp.compression Subject: Re: Problem with compress Message-ID: <2835774B.16DB@tct.com> Date: 18 May 91 18:49:46 GMT Article-I.D.: tct.2835774B.16DB References: <26085: May1416: 52: 3491@kramden.acf.nyu.edu> <1991May15.060236.26763@uunet.uu.net> <1991May15.173739.29874@mp.cs.niu.edu> Organization: Teltronics/TCT, Sarasota, FL Lines: 14