Here's another snapshot, prior to coreutils-7.6.
We've inherited quite a few changes from gnulib,
including one to fix the Solaris build failure.
coreutils snapshot:
http://meyering.net/cu/coreutils-ss.tar.gz 9.6 MB
http://meyering.net/cu/coreutils-ss.tar.xz 4.0 MB
http://meyering.
fsetxattr() is failing for me when the permissions are readonly
but the descriptor is writable as demonstrated by the program below.
I've tried this on ext3 and ext4 with libattr-2.4.43-3.fc11.i586
and linux-2.6.30.5-43.fc11.i586
Is this expected?
cheers,
Pádraig.
#include
#include
#include
#
On 2009-09-08 13:55 +0200, Jim Meyering wrote:
> Here's another snapshot, prior to coreutils-7.6.
All tests passed on Debian sid i386, including the (very) expensive and
root checks. :-)
Cheers,
Sven
Sven Joachim wrote:
> On 2009-09-08 13:55 +0200, Jim Meyering wrote:
>> Here's another snapshot, prior to coreutils-7.6.
>
> All tests passed on Debian sid i386, including the (very) expensive and
> root checks. :-)
Nice. Thanks!
Jim Meyering wrote:
> Here's another snapshot, prior to coreutils-7.6.
> We've inherited quite a few changes from gnulib,
> including one to fix the Solaris build failure.
Passed Skipped Failed
\-
Fedora core 5 x86 |
rerunning on local file systems:
Passed Skipped Failed
\-
Fedora core 5 x86 | 348 42 0
Fedora 11 x86 | 343 47 0
Solaris 10 x86| 328 62 0
X-debbugs-cc: bug-coreutils@gnu.org
Package: coreutils
Version: 7.5-3
Severity: minor
$ man mktemp|col -b|grep -C 3 'info coreutils'
The full documentation for mktemp is maintained as a Texinfo manual.
If the info and mktemp programs are prop
erly installed at your site, the comm
It would be really nice if cut(1) could split fields using whitespace
as a separator (as many other text tools do). Currently I use
$ awk '{ print $3, $4, $5 }'
for this sort of thing, but it seems relatively klutzy, as opposed to (say)
$ cut -w -f 3-5
Mike
On Tue, Sep 08, 2009 at 12:29:49PM +0100, P??draig Brady wrote:
> fsetxattr() is failing for me when the permissions are readonly
> but the descriptor is writable as demonstrated by the program below.
> I've tried this on ext3 and ext4 with libattr-2.4.43-3.fc11.i586
> and linux-2.6.30.5-43.fc11.i5
Hello,
at the moment inotify permits to add new files to be watched using their
path. There are situations where the file path is not know but a
descriptor is available. It would be desiderable to have the
possibility to use the inotify system even in these (rare) cases.
A concrete example of a
10 matches
Mail list logo