Re: [PATCH -v4] random: introduce getrandom(2) system call

2014-07-30 Thread Bob Beck
Pavel. I have bit 'ol enterprise daemon running with established file descriptors serving thousands of connections which periodically require entropy. Now I run out of descriptors. I can't establish new connections. but I should now halt all the other ones that require entropy? I should raise

Re: [PATCH -v4] random: introduce getrandom(2) system call

2014-07-30 Thread Bob Beck
Pavel. I have bit 'ol enterprise daemon running with established file descriptors serving thousands of connections which periodically require entropy. Now I run out of descriptors. I can't establish new connections. but I should now halt all the other ones that require entropy? I should raise

Re: [PATCH, RFC] random: introduce getrandom(2) system call

2014-07-17 Thread Bob Beck
convention in other system calls? On Thu, Jul 17, 2014 at 11:34 AM, Theodore Ts'o wrote: > On Thu, Jul 17, 2014 at 11:05:01AM -0600, Bob Beck wrote: >> Hi Ted, yeah I understand the reasoning, it would be good if there was >> a way to influence the various libc people to >&g

Re: [PATCH, RFC] random: introduce getrandom(2) system call

2014-07-17 Thread Bob Beck
Or perhaps to put that another way, since you don't do minherit - maybe a FORK_ZERO for madvise? or a similar way to do that? On Thu, Jul 17, 2014 at 11:46 AM, Bob Beck wrote: > And thanks btw. > > I don't suppose you guys know who we should talk to about possibly > getting MAP_

Re: [PATCH, RFC] random: introduce getrandom(2) system call

2014-07-17 Thread Bob Beck
And thanks btw. I don't suppose you guys know who we should talk to about possibly getting MAP_INHERIT_ZERO minherit() support? On Thu, Jul 17, 2014 at 11:45 AM, Bob Beck wrote: > we have diffs pending that will do the syscall method until we start > to see it in libc :) > > So bas

Re: [PATCH, RFC] random: introduce getrandom(2) system call

2014-07-17 Thread Bob Beck
we have diffs pending that will do the syscall method until we start to see it in libc :) So basically we're going to put that in right away :) On Thu, Jul 17, 2014 at 11:34 AM, Theodore Ts'o wrote: > On Thu, Jul 17, 2014 at 11:05:01AM -0600, Bob Beck wrote: >> Hi Ted, yeah I u

Re: [PATCH, RFC] random: introduce getrandom(2) system call

2014-07-17 Thread Bob Beck
Hi Ted, yeah I understand the reasoning, it would be good if there was a way to influence the various libc people to ensure they manage to provide a getentropy(). On Thu, Jul 17, 2014 at 11:01 AM, Theodore Ts'o wrote: > On Thu, Jul 17, 2014 at 09:12:15AM -0700, Christoph Hellwig wrote: >> On

Re: [PATCH, RFC] random: introduce getrandom(2) system call

2014-07-17 Thread Bob Beck
Hi Ted, yeah I understand the reasoning, it would be good if there was a way to influence the various libc people to ensure they manage to provide a getentropy(). On Thu, Jul 17, 2014 at 11:01 AM, Theodore Ts'o ty...@mit.edu wrote: On Thu, Jul 17, 2014 at 09:12:15AM -0700, Christoph Hellwig

Re: [PATCH, RFC] random: introduce getrandom(2) system call

2014-07-17 Thread Bob Beck
we have diffs pending that will do the syscall method until we start to see it in libc :) So basically we're going to put that in right away :) On Thu, Jul 17, 2014 at 11:34 AM, Theodore Ts'o ty...@mit.edu wrote: On Thu, Jul 17, 2014 at 11:05:01AM -0600, Bob Beck wrote: Hi Ted, yeah I

Re: [PATCH, RFC] random: introduce getrandom(2) system call

2014-07-17 Thread Bob Beck
And thanks btw. I don't suppose you guys know who we should talk to about possibly getting MAP_INHERIT_ZERO minherit() support? On Thu, Jul 17, 2014 at 11:45 AM, Bob Beck b...@openbsd.org wrote: we have diffs pending that will do the syscall method until we start to see it in libc :) So

Re: [PATCH, RFC] random: introduce getrandom(2) system call

2014-07-17 Thread Bob Beck
Or perhaps to put that another way, since you don't do minherit - maybe a FORK_ZERO for madvise? or a similar way to do that? On Thu, Jul 17, 2014 at 11:46 AM, Bob Beck b...@openbsd.org wrote: And thanks btw. I don't suppose you guys know who we should talk to about possibly getting

Re: [PATCH, RFC] random: introduce getrandom(2) system call

2014-07-17 Thread Bob Beck
convention in other system calls? On Thu, Jul 17, 2014 at 11:34 AM, Theodore Ts'o ty...@mit.edu wrote: On Thu, Jul 17, 2014 at 11:05:01AM -0600, Bob Beck wrote: Hi Ted, yeah I understand the reasoning, it would be good if there was a way to influence the various libc people to ensure they manage

r.kernel.org

2007-09-01 Thread Bob Beck
>I urge developers to not bait into this and just leave this alone. >Those involved know what they are doing and have a strong team of >attorneys watching their backs. Any *necessary* discussions are be >done privately. > > Luis What? when we talk about the ethics of cooperating

Re: Fwd: That whole "Linux stealing our code" thing

2007-09-01 Thread Bob Beck
>As a free software user and developer, the question I have is how come >the Linux community feels that they can take the BSD code that was >reverse-engineered at OpenBSD, and put a more restrictive licence onto >it, such that there will be no possibility of the changes going back >to OpenBSD,

[EMAIL PROTECTED]: I respect the GPL immensely, really I do - but I believe this type of action weakens us all.]

2007-09-01 Thread Bob Beck
- Forwarded message from Bob Beck <[EMAIL PROTECTED]> - From: Bob Beck <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: I respect the GPL immensely, really I do - but I believe this type of action weakens us all. X-Spam-Checker-Version: SpamAssassin 3.1.8

[EMAIL PROTECTED]: I respect the GPL immensely, really I do - but I believe this type of action weakens us all.]

2007-09-01 Thread Bob Beck
- Forwarded message from Bob Beck [EMAIL PROTECTED] - From: Bob Beck [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: I respect the GPL immensely, really I do - but I believe this type of action weakens us all. X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13

Re: Fwd: That whole Linux stealing our code thing

2007-09-01 Thread Bob Beck
As a free software user and developer, the question I have is how come the Linux community feels that they can take the BSD code that was reverse-engineered at OpenBSD, and put a more restrictive licence onto it, such that there will be no possibility of the changes going back to OpenBSD, given

r.kernel.org

2007-09-01 Thread Bob Beck
I urge developers to not bait into this and just leave this alone. Those involved know what they are doing and have a strong team of attorneys watching their backs. Any *necessary* discussions are be done privately. Luis What? when we talk about the ethics of cooperating development