Mike Gerdts wrote:
On 10/30/06, Darren J Moffat Darren.Moffat at sun.com wrote:
James Carlson wrote:
Why, other than the returning an error we already have 5 such privileges
in the basic set. Now in each of those cases (proc_info, proc_session,
proc_fork, proc_exec, file_link_any) there is a
Assuming we do steps 1 and 2 above, do we get into any problems with
POSIX compliance if the default basic privilege set does not include
PRIV_SYS_SYNC?
There is no such thing as a default basic set.
There's a basic set and there's the default set users get when
they login; they are
On Fri 03 Nov 2006 at 10:34AM, Casper.Dik at sun.com wrote:
Assuming we do steps 1 and 2 above, do we get into any problems with
POSIX compliance if the default basic privilege set does not include
PRIV_SYS_SYNC?
There is no such thing as a default basic set.
There's a basic set and
John, if you've done the contributor agreement, I can certainly help you
with this putback.
Bonnie Corwin wrote:
Hi John,
I assume you mean 6363303. I'll add this to the table.
You might want to go ahead and submit a contributor agreement.
Then you'll be all set when someone picks
