Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!zephyr.ens.tek.com!uw-beaver!ubc-cs!van-bc! From: lphillips@lpami.wimsey.bc.ca (Larry Phillips) Newsgroups: comp.sys.amiga Subject: Re: cp-mv-rm1.1 command substitute Message-ID: <1849@lpami.wimsey.bc.ca> Date: 4 Aug 90 15:55:00 GMT Lines: 37 Return-Path: To: van-bc!rnews In <1844@lpami.wimsey.bc.ca>, lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes: >In <13618@cbmvax.commodore.com>, andy@cbmvax.commodore.com (Andy Finkel) writes: >>In article <1837@lpami.wimsey.bc.ca> lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes: >>>In , hclausen@adspdk.CBMNET (Henrik Clausen) writes: >>>>>In article <2666@mindlink.UUCP> a218@mindlink.UUCP (Charlie Gibbs) writes: >>>do. That means that it can't be counted on. It makes file dates and comments >>>useless to have the default behaviour the way it is. >>> >>>-larry >> >>The eternal debate. Ah, well. You know, BSD Unix does the same thing. >>(gives a copy of a file a new filedate) and people don't claim file dates >>are useless on Unix systems. Well, maybe they do :-) > >There are 3 file dates on BSD files, I think; created, last modified, and >last accessed. Would be nice to have this in Amigados, if there was room. Ooops! I have been informed that the three dates in question have been in every version of Unix since V7, and that they are: time of last modification time of last access time of last *file attribute or contents change* My original point remains valid. Thanks to Guy Harris for pointing this out. -larry -- Sex is better than logic, but I can't prove it. +-----------------------------------------------------------------------+ | // Larry Phillips | | \X/ lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips | | COMPUSERVE: 76703,4322 -or- 76703.4322@compuserve.com | +-----------------------------------------------------------------------+