[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: |
pg |
Subject: |
Re: lynx-dev Why use copy and not move when saving 'd'ownloaded files? |
Date: |
Mon, 24 Jul 2000 05:50:50 -0600 (MDT) |
In a recent note, Kim DeVaughn said:
> Date: Mon, 24 Jul 2000 00:53:34 -0600
>
> 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 (on most, if not all UNIX's). If they are
>
> I've no idea how VMS, OS/390, DOS, etc, handle (the equivalent of) a
OS/390 fits the pattern.
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.
-- gil
--
StorageTek
INFORMATION made POWERFUL
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden