Hi Matthew,
Can we avoid things like pid_t * __restrict and char * const
please? Many brains parse the * as a multiplication operator when
it is surrounded by spaces on either side. Even the POSIX standard
used the pid_t *restrict and char *const style.
Thanks,
Mark
hi,there tech
i bought an ipad 3 from this site, the price is good, tech
the site also sell other kinds electronincs,computer,digital
camera,iphone... tech
the shipping is free, maybe it is a good chance for you tech
si t e : urs.com
23:10:41
[demime 1.01d removed an attachment of type image/jpeg which had a name of
tazararse.jpg]
[demime 1.01d removed an attachment of type image/jpeg which had a name of
dmedianista.jpg]
[demime 1.01d removed an attachment of type image/jpeg which had a name of
tbonicamente.jpg]
My co-worker was troubleshooting why some of our unittests (that work on
multiple operating systems and architectures) failed on OpenBSD and saw
that if you call srandom(0) to initialize the RNG, random() will always
return 0. (I was able to reproduce this.)
If this is expected behaviour,
On 2012/03/21 12:37, Jeremy C. Reed wrote:
My co-worker was troubleshooting why some of our unittests (that work on
multiple operating systems and architectures) failed on OpenBSD and saw
that if you call srandom(0) to initialize the RNG, random() will always
return 0. (I was able to
My co-worker was troubleshooting why some of our unittests (that work on
multiple operating systems and architectures) failed on OpenBSD and saw
that if you call srandom(0) to initialize the RNG, random() will always
return 0. (I was able to reproduce this.)
If this is expected
On 2012/03/21 17:41, Stuart Henderson wrote:
On 2012/03/21 12:37, Jeremy C. Reed wrote:
My co-worker was troubleshooting why some of our unittests (that work on
multiple operating systems and architectures) failed on OpenBSD and saw
that if you call srandom(0) to initialize the RNG,
On 21/03/12 1:37 PM, Jeremy C. Reed wrote:
My co-worker was troubleshooting why some of our unittests (that work on
multiple operating systems and architectures) failed on OpenBSD and saw
that if you call srandom(0) to initialize the RNG, random() will always
return 0. (I was able to reproduce
On Wed, Mar 21, 2012 at 12:37:47PM -0500, Jeremy C. Reed wrote:
My co-worker was troubleshooting why some of our unittests (that work on
multiple operating systems and architectures) failed on OpenBSD and saw
that if you call srandom(0) to initialize the RNG, random() will always
return 0.
Hi Jeremy,
On Wed, Mar 21, 2012 at 12:37:47PM -0500, Jeremy C. Reed wrote:
| My co-worker was troubleshooting why some of our unittests (that work on
| multiple operating systems and architectures) failed on OpenBSD and saw
| that if you call srandom(0) to initialize the RNG, random() will
Hello tech@.
In KERNEL MODIFICATION section:
...
When invoked, the kernel identification is first shown.
# config -e -o bsd.new /bsd
OpenBSD 2.6-beta (GENERIC.rz0) #0: Mon Oct 4 03:57:22 MEST 1999
root@winona:/usr/src/sys/arch/pmax/compile/GENERIC.rz0
On Wed, Mar 21, 2012, Alexey E. Suslikov wrote:
The kernel is too old (pre OpenBSD 2.6) and cannot support all of the
functionality needed by the -e option.
Isn't that OpenBSD 2.6-beta pmap arch config example somewhat exotic and
outdated? So about too old pre OpenBSD 2.6 kernel comment.
Hi,
i did not find a place where it is documented explicitly how to use a
certificate chain with relayd.
Should this be documented? Or maybe in ssl(8)?
/Benno
Index: relayd.conf.5
===
RCS file:
On 2012/03/21 20:51, Stuart Henderson wrote:
On 2012/03/21 15:38, Todd T. Fries wrote:
Separately, I'd also love to be able to specify the certificate by name
per relay, as sometimes a given relayd instance might receive redirected
traffic for multiple external addresses. Sure, with
14 matches
Mail list logo
