[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bad cp -a behaviour
From: |
Paul Eggert |
Subject: |
Re: Bad cp -a behaviour |
Date: |
Sat, 07 Aug 2004 19:54:04 -0700 |
User-agent: |
Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) |
Andreas Schwab <address@hidden> writes:
> Tim Waugh <address@hidden> writes:
>
>> The problem seems to be that when a destination file is written it is
>> done so by opening the file without removing it first. If it is a
>> hardlink to a previous destination file from the same command it will
>> be overwritten.
>
> This is required by POSIX.
POSIX doesn't specify the behavior of "cp -a", so it can't require the
current coreutils behavior. It's quite possible that we need to
change the behavior of "cp -a" to make it more useful for its intended
purpose of making archives.
However, I don't understand what the undesired behavior is.
(Like Philip Rowlands, I can't access the original bug report.)
- Bad cp -a behaviour, Tim Waugh, 2004/08/07
- Re: Bad cp -a behaviour, Andreas Schwab, 2004/08/07
- Re: Bad cp -a behaviour,
Paul Eggert <=
- Re: Bad cp -a behaviour, Philip Rowlands, 2004/08/07
- Re: Bad cp -a behaviour, Tim Waugh, 2004/08/10
- Re: Bad cp -a behaviour, Philip Rowlands, 2004/08/11
- Re: Bad cp -a behaviour, Tim Waugh, 2004/08/11
- Re: Bad cp -a behaviour, Philip Rowlands, 2004/08/11
- Re: Bad cp -a behaviour, Tim Waugh, 2004/08/11
- Re: Bad cp -a behaviour, Paul Eggert, 2004/08/11
- Re: Bad cp -a behaviour, Tim Waugh, 2004/08/12
- Re: Bad cp -a behaviour, Philip Rowlands, 2004/08/12
- Re: Bad cp -a behaviour, Andreas Schwab, 2004/08/12