[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev Why use copy and not move when saving 'd'ownloaded files?
|
From: |
Thomas E. Dickey |
|
Subject: |
Re: lynx-dev Why use copy and not move when saving 'd'ownloaded files? |
|
Date: |
Wed, 2 Aug 2000 16:15:34 -0400 (EDT) |
On Wed, 2 Aug 2000, Klaus Weide wrote:
> On Mon, 24 Jul 2000 address@hidden wrote:
> > In a recent note, Kim DeVaughn said:
> > > On Sun, Jul 23, 2000, Frederic L. W. Meunier (address@hidden) said:
> > > | I'd suggest using move since you can have problems with space.
> > >
> > > You can only *really* mv(1) a file if both the source and destination
> > > are on the same file system
> >
> > Furthermore, Lynx's use of cp(1) rather than mv(1) allows the user
> > to save a file to multiple destinations, if desired, without
> > re-fetching from the net.
>
> That is the major reason why lynx uses cp, as I understand it.
actually I had a different impression - much of the odd features in lynx
originated on VMS; in this case there are some odd problems copying
files that are better left to the system's copy utility.
But agreed - the main reason for using cp rather than trying to rename
it is to allow subsequent use. It would be nice to know what files
are currently in-use though - the history page doesn't quite do that.
--
T.E.Dickey <address@hidden>
http://dickey.his.com
ftp://dickey.his.com
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden