bug#5940: [PATCH] cp: treat selinux warnings consistently

2010-04-13 Thread Pádraig Brady
On 13/04/10 13:14, Pádraig Brady wrote: > I noticed some inconsistencies in how ENOTSUP errors were handled by cp. > > The attached should fix it up. I've just pushed this. cheers, Pádraig

bug#5941: tail bug

2010-04-13 Thread Pádraig Brady
Tags: notabug

bug#5942: 8.4 "kill" program fails to link on AIX 5.3

2010-04-13 Thread Pádraig Brady
On 13/04/10 22:36, Daniel Richard G. wrote: > Building coreutils-8.4 on a 64-bit AIX 5.3 system using GCC, I get this: > > gmake[1]: Entering directory `/tmp/coreutils-build/src' > CCLD kill > ld: 0711-317 ERROR: Undefined symbol: .pthread_once > ld: 0711-317 ERROR: Undefined symbol: .pthrea

bug#5942: 8.4 "kill" program fails to link on AIX 5.3

2010-04-13 Thread Daniel Richard G.
Building coreutils-8.4 on a 64-bit AIX 5.3 system using GCC, I get this: gmake[1]: Entering directory `/tmp/coreutils-build/src' CCLD kill ld: 0711-317 ERROR: Undefined symbol: .pthread_once ld: 0711-317 ERROR: Undefined symbol: .pthread_getspecific ld: 0711-317 ERROR: Undefined symbol: .pth

bug#5941: tail bug

2010-04-13 Thread Andreas Schwab
Eric Kever writes: > I've created a file 'foo', and used tail -f to follow the changes to that > file. > I then wrote 'test' to the file and saved it, and tail reported 'test', > which is fine. > I then deleted 'test' and saved the file, and tail reported 'tail: foo: > file truncated', which is f

bug#5941: tail bug

2010-04-13 Thread Eric Blake
On 04/13/2010 02:16 PM, Eric Kever wrote: > I've created a file 'foo', and used tail -f to follow the changes to > that file. > I then wrote 'test' to the file and saved it, and tail reported 'test', > which is fine. > I then deleted 'test' and saved the file, and tail reported 'tail: foo: > file t

bug#5941: tail bug

2010-04-13 Thread Eric Kever
I've created a file 'foo', and used tail -f to follow the changes to that file. I then wrote 'test' to the file and saved it, and tail reported 'test', which is fine. I then deleted 'test' and saved the file, and tail reported 'tail: foo: file truncated', which is fine. I then wrote 'test' again

bug#5940: [PATCH] cp: treat selinux warnings consistently

2010-04-13 Thread Pádraig Brady
I noticed some inconsistencies in how ENOTSUP errors were handled by cp. $ dd bs=1M count=10 if=/dev/zero of=t.vfat $ mkfs.vfat t.vfat $ mkdir m.vfat $ sudo mount -o loop t.vfat m.vfat $ ./src/cp --preserve=all a m.vfat/ ./src/cp: setting attribute `user.foo' for `user.foo': Permission denied ./sr

bug#5918: [dd] conv=sparse option

2010-04-13 Thread H. Langos
On Sat, Apr 10, 2010 at 04:33:07PM +0100, Pádraig Brady wrote: > On 10/04/10 01:28, Heinrich Langos wrote: > > Hello Andreas, Samuel and list, > > > > sorry to pick up such an old thread, but I stumbled upon it while > > looking for an efficient way to "re-sparse" files that contain a > > lot of

bug#5918: [dd] conv=sparse option

2010-04-13 Thread H. Langos
On Sat, Apr 10, 2010 at 06:46:13PM +0200, Samuel Thibault wrote: > Pádraig Brady, le Sat 10 Apr 2010 16:33:07 +0100, a écrit : > > On 10/04/10 01:28, Heinrich Langos wrote: > > > a) "dd" will maintain an existing of=target file including the inode > > >number, thus respecting existing hard lin