[re-adding the list]
On 02/05/2011 06:23 PM, Noel Kuntze wrote:
>> Look at 'man 2 uname'. On Linux, the uname.release version contains a
>> numeric string. The uname.version field is not documented as to it's
>> contents, but POSIX merely requires that release and version together
>> identify th
In coreutils 8.9 (latest), the following commands trigger an invalid
memory access.
cut -c1234567890- --output-d=: foo
cut -f1234567890- --output-d=: foo
cut -b1234567890- --output-d=: foo
The number 1234567890 is just a random number 'big enough' to make the
invalid access generate a segmentatio
Please ignore this. It's a duplicate submission of bug# 7992
It should be possible to specify a timezone such as
Europe/Rome for the date input. That works in TZ
to control the output, so it should work in the input too.
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org, www.gnu.org
Richard Stallman wrote:
> It should be possible to specify a timezone such as
> Europe/Rome for the date input. That works in TZ
> to control the output, so it should work in the input too.
For date input (using --date=STRING) you can use the TZ variable to
specify the input timezone. Here is an
Examination of the info documention for the coreutils-8.x
implementation of the touch command, and the POSIX (IEEE Std
1003.1-2001), does not make clear exactly what time is used when the
argument files exist, and no time specifier (-r or -t option) is
supplied.
For example,
touch first s
after upgrading from coreutils 8.9 to 8.10, the sparse handling in cp is
silently breaking on btrfs filesystems with the compressed option enabled.
using --sparse=never works fine, but "auto" or "always" tend to fail. the
cp/fiemap-2 test catches the issue nicely.
to reproduce (i'm using linu
On 02/07/2011 03:36 PM, Nelson H. F. Beebe wrote:
> Perhaps the coreutils manual page and info documentation could be
> updated to document what that implementation does, and discuss whether
> it agrees or differs from other implementations (and POSIX).
If A and B both exist, then "touch A B" migh
