Hi,
here is a first version of the new mandoc.db(5) file format, the
program makewhatis(8) writing it, and the programs man(1) and
apropos(1) reading it. This is not yet intended for commit,
i have only done insufficient testing, so i'm sure there are
still bugs. But i want to show it around ear
Yeah, I'm ok with this.
go for it
On Thu, Jun 30, 2016 at 6:59 AM, Brent Cook wrote:
> As a precedent, nc has a conversational, specific style of error
> reporting when a socketopt fails. With the IPv4/6-specific options, we
> refactored the code to the point that the error messages are less
>
On Thu, Jun 30, 2016 at 04:43:12PM +0100, Craig Skinner wrote:
> Hiya,
>
> On 2016-06-29 Wed 14:46 PM |, Craig Skinner wrote:
> > On 2016-06-28 Tue 15:27 PM |, Craig Skinner wrote:
> > > This diff presents 'Halt' and 'Reboot' buttons on the xdm screen.
> > >
> >
> > Now it closes the message box
Hiya,
On 2016-06-29 Wed 14:46 PM |, Craig Skinner wrote:
> On 2016-06-28 Tue 15:27 PM |, Craig Skinner wrote:
> > This diff presents 'Halt' and 'Reboot' buttons on the xdm screen.
> >
>
> Now it closes the message box + adds 'Hibernate' & 'Suspend' buttons.
>
> >
> > Adapted from http://cafim.
On systems where we do not have BN_ULLONG (notably Win64), BN_mod_word()
can return incorrect results if the supplied modulus is too big.
Note now that BN_mod_word may fail, like BN_div_word. Handle this
properly and document in the man page.
Thanks to Brian Smith for pointing out these fixes fro
On Thu, 30 Jun 2016 13:23:55 +0200, Alexander Bluhm wrote:
> SLIST_REMOVE() is traversing the list to find the element that has
> to be removed. I prefer a LIST instead of using that macro.
Agreed. Unless you are always removing the head, SLIST_REMOVE()
can be quite expensive.
- todd
As a precedent, nc has a conversational, specific style of error
reporting when a socketopt fails. With the IPv4/6-specific options, we
refactored the code to the point that the error messages are less
specific and maybe misleading (e.g. setting ToS on an IPv6 socket).
This patch makes the per-add
This is something I noticed while reviewing this report:
https://github.com/libressl-portable/portable/issues/200
In the event of a failure in _rs_allocate for rsx, we still return the
freed memory for rs. Not a huge deal since we subsequently abort in
_rs_init, but it looks strange on its own.
On Thu, Jun 30, 2016 at 11:05:06AM +0200, Martin Pieuchot wrote:
> While removing the KERNEL_LOCK() from bpf_tap() I figured out that a
> SLIST is enough for the list of descriptors, ok?
> @@ -1654,7 +1654,7 @@ bpfilter_create(int unit)
> void
> bpfilter_destroy(struct bpf_d *bd)
> {
> - LI
OK bluhm@
On Wed, Jun 29, 2016 at 12:19:00PM +0200, Martin Pieuchot wrote:
> On 20/06/16(Mon) 00:32, Alexander Bluhm wrote:
> > On Tue, Jun 14, 2016 at 12:02:34PM +0200, Martin Pieuchot wrote:
> > > --- netinet/in_pcb.c 19 Apr 2016 22:16:25 - 1.206
> > > +++ netinet/in_pcb.c 14
While removing the KERNEL_LOCK() from bpf_tap() I figured out that a
SLIST is enough for the list of descriptors, ok?
Index: net/bpf.c
===
RCS file: /cvs/src/sys/net/bpf.c,v
retrieving revision 1.142
diff -u -p -r1.142 bpf.c
--- net/b
On 28/06/16(Tue) 20:03, Jonathan Matthew wrote:
> Currently, art explicitly relies on the kernel lock to serialise updates. We
> need to allow route insertion during packet processing, which means avoiding
> the kernel lock is desirable. The diff below achieves that, adding a mutex
> per art root
12 matches
Mail list logo
