Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!olivea!uunet!van-bc!jtc
From: jtc@van-bc.wimsey.bc.ca (J.T. Conklin)
Newsgroups: comp.unix.sysv386
Subject: Re: ESIX compress(1) broken (was: Re: Using Interactive TPWB...)
Keywords: ESIX compress
Message-ID: <1294@van-bc.wimsey.bc.ca>
Date: 10 Jan 91 23:58:17 GMT
References: <1991Jan6.225758.27472@portia.Stanford.EDU> <1991Jan7.154351.16652@jwt.UUCP> <1991Jan8.222044.9602@unixland.uucp>
Organization: SEAC Software Engineering, Vancouver, B.C., Canada
Lines: 15

In article <1991Jan8.222044.9602@unixland.uucp> bill@unixland.uucp (Bill Heiser) writes:
>In article <1991Jan7.154351.16652@jwt.UUCP> john@jwt.UUCP (John Temples) writes:
>>When I first installed B news on my ESIX system several months ago, I
>>copied /usr/bin/compress to /usr/lib/news, rather than compiling the
>
>I just threw the Esix 'compress' in the dumper and installed another
>"working" compress in its place.  So far, so good...

Since ESIX's compress' use of -u, and REAL compress' use of -d, don't
conflict, it seems the best method rationalizing the situation is to
hack the compress source so it recognizes both flags.  That way, both
net.software and ESIX installation disks should continue to work.

-- 
J.T. Conklin	jtc@wimsey.bc.ca, ...!{uunet,ubc-cs}!van-bc!jtc