On Fri, Feb 10, 2012 at 09:37:30AM +, YAMAMOTO Takashi wrote:
On Mon, Feb 06, 2012 at 09:51:19AM +, Emmanuel Dreyfus wrote:
Here is public disuccsion about extended attributs namespaces, following
a private request from yamt@
Which of the two models does OS X use?
hi,
Manuel Bouyer bou...@antioche.eu.org wrote:
I'm not sure you can even read them: on freebsd user.foo.bar will be stored
as name foo.bar in (integer) namespace user. When we'll read it we'll
find foo in (integer) namespace user but we don't know which namespace
it really belongs to (as
hi,
I updated my patches after fixing a sever bug that caused fallout in lots
of (apparently unrelated) atf tests by fooling ld.elf_so into insecure
mode, thus not allowing LD_PRELOAD and breaking all the rump clients...
On Fri, Feb 10, 2012 at 11:20:38AM +, YAMAMOTO Takashi wrote:
is it safe to release exec_lock?
Good catch - I'll defer the release untill the child has done it's rw_enter().
Martin
On Fri, 10 Feb 2012, YAMAMOTO Takashi wrote:
how about the following mapping?
xattr name string - ufs on-disk
system.foo - SYSTEM foo
others.bar - USER others.bar
Looks reasonable, but then which of the following?
a) user.user.baz - USER user.baz
b)
Alan Barrett a...@cequrux.com wrote:
how about the following mapping?
xattr name string - ufs on-disk
system.foo - SYSTEM foo
others.bar - USER others.bar
Looks reasonable, but then which of the following?
a)user.user.baz - USER user.baz
b)user.baz
On Feb 10, 2012, at 11:04 PM, Mouse wrote:
I find myself wanting something I'm tentatively calling O_NOACCESS,
which is basically open for neither read nor write. (I want this
mostly so I can open a --x directory for fchdir() purposes.)
Looking at sys_open(), I see that one of the first
Why not use O_DIRECTORY (which is part of -current) and add that to
flags?
Backporting that might be a better alternative. What are its
semantics?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email!
