On Sat, Jul 13, 2013 at 7:40 AM, meino.cra...@gmx.de wrote:
/dev/root on / type ext4
(rw,noatime,user_xattr,commit=60,barrier=1,data=ordered)
You don't have a separate mount for /tmp, so the above would be pertinent.
And it shows support for xattr, so you should be good
--
Douglas J Hunley
On Sat, Jul 13, 2013 at 1:19 AM, meino.cra...@gmx.de wrote:
How can I pratically proof the availability of xattr on the filesystem
of /tmp -- beside checking the kernel config.
Is your /tmp a tmpfs? What's the output of 'mount' please?
--
Douglas J Hunley (doug.hun...@gmail.com)
Twitter:
Douglas J Hunley doug.hun...@gmail.com [13-07-13 13:36]:
On Sat, Jul 13, 2013 at 1:19 AM, meino.cra...@gmx.de wrote:
How can I pratically proof the availability of xattr on the filesystem
of /tmp -- beside checking the kernel config.
Is your /tmp a tmpfs? What's the output of 'mount'
On 13 July 2013, at 12:40, meino.cra...@gmx.de wrote:
...
I also removed (as an experiement) the acl and xattr use flags
from rsyncno success (the original settings only remove the
xattr-flags).
Again, Meino, you're not stating clearly enough what you've done.
Did you unset these USE
Stroller strol...@stellar.eclipse.co.uk [13-07-12 00:51]:
On 11 July 2013, at 19:58, meino.cra...@gmx.de wrote:
...
beaglebone:/rootKrm -v
rm: remove regular empty file ‘/tmp/foobar123’? yes
removed ‘/tmp/foobar123’
...
Everything was done as root.
I think this is the output
On Wed, Jul 10, 2013 at 12:06 PM, meino.cra...@gmx.de wrote:
is this a newly added feature, which is needed? Since three days
(about) before it works like a charm. Beside updateing my system, I
did nothing to change the filesytem (ext4 if I remember correctly)
or such ...
Any ideas, what
On 9 July 2013, at 18:28, meino.cra...@gmx.de wrote:
...
receiving incremental file list
timestamp.chk
rsync: failed to set permissions on /tmp/.tmpNBwK63.n6Acda: Function not
implemented (38)
I can't say the problem is related to xattrs, but when posting an error with a
message like this
Stroller strol...@stellar.eclipse.co.uk [13-07-11 18:12]:
On 9 July 2013, at 18:28, meino.cra...@gmx.de wrote:
...
receiving incremental file list
timestamp.chk
rsync: failed to set permissions on /tmp/.tmpNBwK63.n6Acda: Function not
implemented (38)
I can't say the problem is
On 11 July 2013, at 19:58, meino.cra...@gmx.de wrote:
...
beaglebone:/rootKrm -v
rm: remove regular empty file ‘/tmp/foobar123’? yes
removed ‘/tmp/foobar123’
...
Everything was done as root.
I think this is the output of `rm -vi $file` not `rm -v $file` - this suggests
you have at least
On Tue, Jul 9, 2013 at 1:28 PM, meino.cra...@gmx.de wrote:
rsync: failed to set permissions on /tmp/.tmpNBwK63.n6Acda: Function not
implemented (38)
You don't have POSIX ACL )xattr) support on whatever fs you have for /tmp ?
--
Douglas J Hunley (doug.hun...@gmail.com)
Twitter: @hunleyd
Douglas J Hunley doug.hun...@gmail.com [13-07-10 17:24]:
On Tue, Jul 9, 2013 at 1:28 PM, meino.cra...@gmx.de wrote:
rsync: failed to set permissions on /tmp/.tmpNBwK63.n6Acda: Function not
implemented (38)
You don't have POSIX ACL )xattr) support on whatever fs you have for /tmp ?
Hi,
eix-syncing my Beaglebone results in some strange output
and no eix-sync at all.
Especially those
rsync: failed to set permissions on /tmp/.tmpNBwK63.n6Acda: Function not
implemented (38)
are mysterious.
I added the complete log below.
I dont want to trigger a ban of my IP for too
12 matches
Mail list logo
