Re: Openat() and fexecve() committed
- From: Garrett Wollman <wollman@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 31 Mar 2008 11:57:48 -0400 (EDT)
In article <20080331153006.GK21209@xxxxxxxxxxxxxxxxxxxxxxxxx>,
kostikbel@xxxxxxxxx writes:
This is a notice for the list that the implementation of the openat(2)
and accompanied syscalls, among them fexecve(2), as specified in The
Open Group document titled "Extended API Set Part 2", is committed today
into the HEAD. Besides (now) FreeBSD, the functionality is implemented
on Linux, and I believe that it originated on Solaris.
Please note that the exact requirements for these functions have been
altered somewhat in the Austin Group, so additional work is likely to
be required for POSIX.1-2008 compliance.
gives the error EACCESS on both Linux and FreeBSD, and succeeds on Solaris.
The Solaris behaviour seems to be specified in the document cited above.
There are arguments in support of the both observed behaviour.
I believe this is one of the issues which was addressed in the
standardization process.
-GAWollman
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: Openat() and fexecve() committed
- From: Kostik Belousov
- Re: Openat() and fexecve() committed
- References:
- Openat() and fexecve() committed
- From: Kostik Belousov
- Openat() and fexecve() committed
- Prev by Date: Kernel page fault with the following non-sleepable locks held...
- Next by Date: Re: Openat() and fexecve() committed
- Previous by thread: Openat() and fexecve() committed
- Next by thread: Re: Openat() and fexecve() committed
- Index(es):