OpenBSD 5.7 errata:
http://www.openbsd.org/errata57.html#015_relayd
015: RELIABILITY FIX: September 28, 2015 All architectures
Various problems were identified in relayd and merged back from current to
5.7 in this maintanance update.
This patch is for 5.7 only, it fixes reliability problems
On Mon, Sep 14, 2015 at 04:52:07PM +0200, Alexis de BRUYN wrote:
> Hi Paul,
>
> I have tried the last -current/octeon (and 5.7/octeon) on a D-Link DSR-500N
> (HW A1), but the bootoctlinux command failed.
>
> Regards,
Wow, a reply to a one and a half year-old email! :-)
I think you need to
On 2015 Sep 28 (Mon) at 22:23:49 +0200 (+0200), Matthieu Herrb wrote:
:On Wed, Sep 16, 2015 at 02:37:38AM -0600, David Coppa wrote:
:>
:> Hi!
:>
:> Here's an update to libxcb-1.11.1
:>
:> Changes:
:>
:> - Expose 64-bit sequence numbers for XLib
:> - Call _xcb_wake_up_next_reader from
On 2015/09/29 14:27, Peter Hessler wrote:
> On 2015 Sep 28 (Mon) at 22:23:49 +0200 (+0200), Matthieu Herrb wrote:
> :On Wed, Sep 16, 2015 at 02:37:38AM -0600, David Coppa wrote:
> :>
> :> Hi!
> :>
> :> Here's an update to libxcb-1.11.1
> :>
> :> Changes:
> :>
> :> - Expose 64-bit sequence
Hello,
I've tried Richard's patch on sparc. I took a brief look at its source code.
It's essentially what PF is doing on Solaris.
The checksum handling in PF on systems with HW assisted checksums is getting
tricky for local (out)bound packets. The approach we take on Solaris is as
follows:
On 2015/09/29 13:53, David Coppa wrote:
> > The diff looks ok, but we currently don't have anything in xenocara
> > using the new functions. Do you know any application in ports that
> > would use it if available ?
>
> I don't know, I've just followed the "rule" new functions->minor bump.
>
>
On Mon, Sep 28, 2015 at 10:23 PM, Matthieu Herrb wrote:
> On Wed, Sep 16, 2015 at 02:37:38AM -0600, David Coppa wrote:
>>
>> Hi!
>>
>> Here's an update to libxcb-1.11.1
>>
>> Changes:
>>
>> - Expose 64-bit sequence numbers for XLib
>> - Call _xcb_wake_up_next_reader from
On 09/29/15 14:38, Paul Irofti wrote:
On Mon, Sep 14, 2015 at 04:52:07PM +0200, Alexis de BRUYN wrote:
Hi Paul,
I have tried the last -current/octeon (and 5.7/octeon) on a D-Link DSR-500N
(HW A1), but the bootoctlinux command failed.
Regards,
Wow, a reply to a one and a half year-old email!
On Tue, Sep 29, 2015 at 01:34:03PM +0100, Stuart Henderson wrote:
> On 2015/09/29 14:27, Peter Hessler wrote:
> > On 2015 Sep 28 (Mon) at 22:23:49 +0200 (+0200), Matthieu Herrb wrote:
> > :On Wed, Sep 16, 2015 at 02:37:38AM -0600, David Coppa wrote:
> > :>
> > :> Hi!
> > :>
> > :> Here's an
* Alexandr Nedvedicky [2015-09-29 12:17]:
> I have not looked at current checksum handling at PF on OpenBSD, so can't tell
> exactly what's going on there. I feel PF does not bother too much with
> updating
> the checksum, when it changes the packet. It seems to
The last diff only had +'s, so restore the balance. Since the sad
demise of art, san, and lmc, there is some crisco that can be flensed.
The diff has ^L's in so there's a risk it may get mangled with
quoted-unreadable encoding, so I've put a copy at
http://junkpile.org/sppp-decisco.diff
Index:
This diff teachs sppp/pppoe(4) to set ifq priority on control frames
(LCP, PAP/CHAP, the various pppoe PADx). These cannot be set the normal
way because these non-IP frames aren't fed through PF.
It's done using a #define which is currently set to a high priority as
that's what is normally wanted
Apologies for not including dmesg in original email.
OpenBSD 5.8-current (RAMDISK_CD) #1271: Tue Sep 29 10:30:11 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 117374976 (111MB)
avail mem = 112254976 (107MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS
Hi,
While installing openbsd on vmware using today's snapshot 29-sep-2015, I
get the following message on the final part of the install process, leaving
the system in an unusable state (not booting normally after installing from
bsd.rd).
The hypervisor is running esx 5.1.0
Guest settings:
128mb
On 29.9.2015. 1:00, Hrvoje Popovski wrote:
> On 28.9.2015. 23:53, Mark Kettenis wrote:
>> This diff makes the tx completion path run without the kernel lock
>> held. With this change, the interrupt handler will not grab the
>> kernel lock under normal circumstances. The diff follows the same
>>
15 matches
Mail list logo