Re: touch and utimens troubles on new/old software combinations

Eric Blake <[EMAIL PROTECTED]> writes: > I could also work on a patch like this - basically, gnulib/m4/utimens.m4 > could check whether futimens/utimensat fail with ENOSYS, and if so, treat > them as though they were not declared. But then you lose the ability to > adjust timestamps to the nanose

Re: cp doc bug

Bruno Haible <[EMAIL PROTECTED]> wrote: > "cp --help" says > > --preserve[=ATTR_LIST] preserve the specified attributes (default: > mode,ownership,timestamps), if possible > additional attributes: context, links, all > > but

Re: cp -p and metadata

Bruno Haible <[EMAIL PROTECTED]> wrote: > This blog > > http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/ > has an explanation of all the kinds of file metadata that exists on MacOS X: > resource forks, creation date, ACLs, extended attributes. > > S

Re: rebased timeout patch

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Jim Meyering on 6/3/2008 12:12 AM: | | * src/nice.c (program_name): Remove "const" in this one case, | to avoid the warning it introduced. Couldn't we instead use argv[0] instead of program_name in that instance, since it is still in sco

Re: touch and utimens troubles on new/old software combinations

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Andreas Schwab on 6/3/2008 2:00 AM: | | You would also lose the capability to build on a system with an old | kernel, but new glibc (eg in a chroot), and getting the same result as | if building on the target system. Runtime configure ch

Re: rebased timeout patch

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 6/3/2008 12:12 AM: > | > | * src/nice.c (program_name): Remove "const" in this one case, > | to avoid the warning it introduced. > > Couldn't we instead use argv[0] instead of program_name in that instance, > since it is still in

Re: cp and SELinux context

Jim Meyering wrote: > > --preserve[=ATTR_LIST] preserve the specified attributes (default: > > mode,ownership,timestamps), if possible > > additional attributes: context, links, all > > ... it's the SELinux context, Why does

[patch #6532] tail -u -- unbuffered output

URL: Summary: tail -u -- unbuffered output Project: GNU Core Utilities Submitted by: jnweiger Submitted on: Tuesday 06/03/2008 at 15:14 Category: None Priority: 5 - No

Re: [patch #6532] tail -u -- unbuffered output

Juergen Weigert <[EMAIL PROTECTED]> wrote: > when tail's stdout is not a terminal, stdio library fools us by buffering > large chunks of data. > This patch adds an option to run in unbuffered mode, > Implemented as straightforward use of fflush(). > > Date: Tuesday 06/03/2008 at 15:14 Name: tail-u

Re: cp and SELinux context

Bruno Haible <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >> > --preserve[=ATTR_LIST] preserve the specified attributes (default: >> > mode,ownership,timestamps), if possible >> > additional attributes: context, links, a