Si no podes visualizar este mail, ingresa a:
http://news1.bonuscupon.com.ar/r.html?uid=1.27.295h.128.gydionacve
The expensive random(4) devices referred to don't exist any longer
and aren't described in that man page, but it's probably worth
mentioning how arc4random(3) is different from rand(3) etc.
Index: arc4random.3
===
RCS file: /cvs/src/l
Index: share/man/man4/pflog.4
===
RCS file: /cvs/src/share/man/man4/pflog.4,v
retrieving revision 1.10
diff -u -r1.10 pflog.4
--- share/man/man4/pflog.4 31 May 2007 19:19:51 - 1.10
+++ share/man/man4/pflog.4 26 Jul 2
I have a system with two network interfaces (em0 and em1), running dhcp
on both. Both dhcp servers provide me with a nameserver, but only one
of them works (I can't fix this). There is a config file for dhclient
I can use, but it only supports the supersede keyword. I don't want
to statically con
I like this on first read. In fact I thought this already existed.
I'll actually look more closely at the code tomorrow.
Ken
On Thu, Jul 26, 2012 at 10:09:28PM -0400, Ted Unangst wrote:
> I have a system with two network interfaces (em0 and em1), running dhcp
> on both. Both dhcp servers pro
On Thu, Jul 26, 2012 at 10:09:28PM -0400, Ted Unangst wrote:
> I have a system with two network interfaces (em0 and em1), running dhcp
> on both. Both dhcp servers provide me with a nameserver, but only one
> of them works (I can't fix this). There is a config file for dhclient
> I can use, but it
On Mon, 23 Jul 2012 20:45:17 +0400
Alexander Polakov wrote:
> This diff reduces IPI traffic for a case when process A is sending
> a lot of signals to process B running on a different CPU. userret()
> delivers all process signals at once, so there is no need to send
> an interrupt for every signa
On Fri, Jul 27, 2012 at 00:42, Brynet wrote:
> On Thu, Jul 26, 2012 at 10:09:28PM -0400, Ted Unangst wrote:
>> I have a system with two network interfaces (em0 and em1), running dhcp
>> on both. Both dhcp servers provide me with a nameserver, but only one
>> of them works (I can't fix this). There
One can set a dhclient-script to ignore things and then call
the real dhclient-script, but I like this diff better.
Penned by Kenneth R Westerback on 20120726 21:43.39, we have:
| I like this on first read. In fact I thought this already existed.
| I'll actually look more closely at the
Ted Unangst wrote:
>[...] I just want to say "pretend this option did not arrive."
>
>Diff below adds a little support for an ignore keyword. Like
>supersede, except don't actually use the supplied value.
Put another way, dhclient has a "default permit" policy (it will use
any nameserver informat
10 matches
Mail list logo
