Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!sci.ccny.cuny.edu!phri!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.unix.shell
Subject: Re: How to do <cmd> file | hold file (now cp)
Message-ID: <3402:Sep1309:52:1290@kramden.acf.nyu.edu>
Date: 13 Sep 90 09:52:12 GMT
References: <13611@hydra.gatech.EDU> <13613@hydra.gatech.EDU>
Organization: IR
Lines: 10

In article <13613@hydra.gatech.EDU> gt0178a@prism.gatech.EDU (BURNS) writes:
> And more to Leslie's point, by adding the chmod, its clear that neither cp
> or > change the attributes of the destination file:

Once again, we're talking about how cp should work. My conception of a
good cp is that it doesn't replace the contents of the destination file;
rather, it copies a given file into a new name, and unlinks that name if
it happens to exist already.

---Dan