On Mon, Feb 25, 2019 at 10:49:16AM +1000, David Gwynne wrote:
> the mcl2k2 pool, aka the intel mbuf cluster pool, gets set up to allocate
> at least 2048 + 2 bytes, which gets rounded up by 64 bytes to 2112
> bytes. this diff makes ix move the reception of packets to the end of
> the 2112 byte allo
Hmm,
somehow a leading space snuck in. Attached is the same diff without
leading space and it now applies cleanly.
Cheers
Matthias
On 24.02.2019 22:09, Matthias Schmidt wrote:
Hi,
while looking at signify's man page I noticed that the names of the
arguments in the EXAMPLES section chang
On Mon, Feb 25, 2019 at 10:37:40AM +1000, David Gwynne wrote:
>
>
> > On 22 Feb 2019, at 05:01, Martin Pieuchot wrote:
> >
> > On 21/02/19(Thu) 07:35, David Gwynne wrote:
> >>> On 20 Feb 2019, at 11:21 pm, Martin Pieuchot wrote:
> >>>
> >>> On 20/02/19(Wed) 14:44, David Gwynne wrote:
> I
i had to think a bit about what rw_lock returns, so i made this.
is this worth it?
Index: rwlock.9
===
RCS file: /cvs/src/share/man/man9/rwlock.9,v
retrieving revision 1.23
diff -u -p -r1.23 rwlock.9
--- rwlock.94 Jun 2018 04:52:
the mcl2k2 pool, aka the intel mbuf cluster pool, gets set up to allocate
at least 2048 + 2 bytes, which gets rounded up by 64 bytes to 2112
bytes. this diff makes ix move the reception of packets to the end of
the 2112 byte allocation so there's space left at the front of the mbuf.
this in turn m
> On 22 Feb 2019, at 05:01, Martin Pieuchot wrote:
>
> On 21/02/19(Thu) 07:35, David Gwynne wrote:
>>> On 20 Feb 2019, at 11:21 pm, Martin Pieuchot wrote:
>>>
>>> On 20/02/19(Wed) 14:44, David Gwynne wrote:
Index: sys/net/if.c
===
Stuart Henderson wrote:
> On 2019/02/23 18:02, Ted Unangst wrote:
> > signify -z adds a date= line to the header, but nothing reads it. It's also
> > not very useful, since it's outside the signature. It would still not be
> > useful, because nothing about the signify design cares about when someth
On Sun, 24 Feb 2019 11:40:10 +0100, Ingo Schwarze wrote:
> During the upcoming cleanup steps, let use retain full support for
> the first (ESC-[) syntax and lets us completely delete support for
> the second and third CSI syntaxes (single-byte CSI and UTF-8
> single-character two-byte CSI).
That
Hi,
while looking at signify's man page I noticed that the names of the
arguments in the EXAMPLES section change (newkey.sec vs key.sec, etc).
The diff harmonizes the examples. It makes it easier to follow the examples.
Cheers
Matthias
diff --git signify.1 signify.1
index de3b433e3b
Hi Marc,
I started dpb in emacs compilation mode (I know...) and observed these
errors:
Use of uninitialized value in concatenation (.) or string at
/usr/ports/infrastructure/lib/DPB/MiniCurses.pm line 279.
A little bit of digging revealed that $self->{home} is undefined, namely
making this chang
>> Date: Sun, 24 Feb 2019 10:44:25 -0500
>> From: Todd Mortimer
>>
>> A few weeks ago I noticed that firefox tabs were getting killed for
>> running afoul of pledge(2). It seems that the problem was some calls to
>> shmget(2) from the X swrast_dri.so lib that seem to have come from the
>> new mes
> Date: Sun, 24 Feb 2019 10:44:25 -0500
> From: Todd Mortimer
>
> A few weeks ago I noticed that firefox tabs were getting killed for
> running afoul of pledge(2). It seems that the problem was some calls to
> shmget(2) from the X swrast_dri.so lib that seem to have come from the
> new mesa code
On Fri, Feb 22, 2019 at 08:49:58PM +0100, Jan Klemkow wrote:
> Hi,
>
> The diff below adds support for the Dynastream "ANT USBStick2" to
> uscom(4). The device attached with the following message:
>
> uscom0 at uhub0 port 2 configuration 1 interface 0 "Dynastream Innovations
> ANT USBStick2" re
On Sun, Feb 24, 2019 at 10:44:25AM -0500, Todd Mortimer wrote:
> A few weeks ago I noticed that firefox tabs were getting killed for
> running afoul of pledge(2). It seems that the problem was some calls to
> shmget(2) from the X swrast_dri.so lib that seem to have come from the
> new mesa code tha
A few weeks ago I noticed that firefox tabs were getting killed for
running afoul of pledge(2). It seems that the problem was some calls to
shmget(2) from the X swrast_dri.so lib that seem to have come from the
new mesa code that was recently imported. Since the shm syscalls aren't
covered by any p
Hi,
I noticed some things in the strptime(3) implementing when parsing timezone
strings using the %z format string.
1. I noticed the tm_gmtoff value is not correctly set in some cases. It should
set tm_gmtoff to the offset from UTC in seconds (as described in mktime(3)).
2. The military/nautical
On Thu, Feb 14, 2019 at 09:38:33AM +0100, Matthieu Herrb wrote:
> On Mon, Feb 11, 2019 at 07:34:46AM +0100, Matthieu Herrb wrote:
> > Hi,
> >
> > I've recently imported xorgproto 2018.4 in xenocara. This is a package
> > the unifies all the previous *proto packages from X.Org (except
> > xcb-proto
On 2019/02/23 18:02, Ted Unangst wrote:
> signify -z adds a date= line to the header, but nothing reads it. It's also
> not very useful, since it's outside the signature. It would still not be
> useful, because nothing about the signify design cares about when something
> was signed. It does cause
On Sat, Feb 23 2019, Aaron Miller wrote:
> On February 23, 2019 2:50:46 AM PST, Jeremie Courreges-Anglas
> wrote:
>>On Sat, May 07 2016, Stefan Kempf wrote:
[...]
> Hi Jeremie,
>
> That is concerning. I'm on my phone and haven't had a chance to investigate,
> but from the code in the gdb out
Hi,
Stefan Sperling wrote on Sat, Feb 23, 2019 at 04:19:02PM +0100:
> Your diff looks good to me.
> And I can't see how it could make this situation any worse either.
thanks for checking; i committed the first patch.
To be able to continue with the less cleanup i started, i have to
explain som
20 matches
Mail list logo
