Xref: utzoo comp.sources.bugs:2907 comp.compression:560
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!news.cs.indiana.edu!rutgers!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.sources.bugs,comp.compression
Subject: Re: Problem with compress
Message-ID: <26085:May1416:52:3491@kramden.acf.nyu.edu>
Date: 14 May 91 16:52:34 GMT
Article-I.D.: kramden.26085:May1416:52:3491
References: <1991May14.044431.23932@sparky.IMD.Sterling.COM>
Organization: IR
Lines: 15

(I'm not sure whether this is appropriate for comp.compression.)

In article <1991May14.044431.23932@sparky.IMD.Sterling.COM> kent@sparky.IMD.Sterling.COM (Kent Landfield) writes:
> I received an interesting question today, one I had never really considered.
> "How does compress deal with symbolic links ?"

compress isn't a BSD program. It uses stat(), and its behavior makes
perfect sense.

I think compressors should ignore problems like this. They shouldn't
open files, they shouldn't close files, they shouldn't do anything but
read data and write compressed data. This also makes them more portable.
A separate, system-dependent program can do the dirty work.

---Dan