Warren L Dodge [EMAIL PROTECTED] wrote:
I have built coreutils-6.12 on a GNU/Linux RedHat3 system. When I use
the cp command with the --preserve=mode,timestamps switch there is a
problem where a copy to a nfs mounted file system does not set the
timesamp properly.
I show examples below where
Warren L Dodge [EMAIL PROTECTED] writes:
I have built coreutils-6.12 on a GNU/Linux RedHat3 system. When I use
the cp command with the --preserve=mode,timestamps switch there is a
problem where a copy to a nfs mounted file system does not set the
timesamp properly.
That looks like that old
Jim Meyering [EMAIL PROTECTED] wrote:
Warren L Dodge [EMAIL PROTECTED] wrote:
I have built coreutils-6.12 on a GNU/Linux RedHat3 system. When I use
the cp command with the --preserve=mode,timestamps switch there is a
problem where a copy to a nfs mounted file system does not set the
timesamp
Bruno Haible [EMAIL PROTECTED] wrote:
Jim Meyering wrote:
... if SIGPIPE is blocked or ignored.
which is not generally recommended.
In some contexts. Some environments (mis-configured login/csh) have
resulted in the default SIGPIPE handler being SIG_IGN.
I agree that having SIGPIPE
Jim Meyering wrote:
You can distinguish close_stream and close_stdout. close_stream is library
code,
close_stdout is not. What about a 'bool ignore_epipe' that influences the
behaviour of close_stdout? Whereas the library code that called close_stream
has to check against EOF/EPIPE
% touch foo foo
% cp -u foo foo echo yes
cp: `foo' and `foo' are the same file
I expected that since -u says
-u, --update
copy only when the SOURCE file is newer than the
destination file or when the destination file is missing
it would not attempt to copy
A few tools are required to build coreutils from a git checkout, but
not checked in a friendly way. This patch adds checks to bootstrap
and configure.
Oh, and updates automake to 1.10.1, which appears to work.
diff --git a/bootstrap b/bootstrap
index 438a145..0232ae9 100755
--- a/bootstrap
