On 2016-09-12, Lawrence Wieser wrote:
> I have a CyberPower UPS that my OpenBSD 5.8 system sees just fine at uhidev0
> on upd0. But the `usbhid-ups` driver for NUT is unable to talk to it.
>
> There are a handful of older comments in the lists that offer a couple of
> alternatives. One involved di
On Sun, 11 Sep 2016 21:35:46 -0400, Lawrence Wieser wrote:
> I have a CyberPower UPS that my OpenBSD 5.8 system sees just fine at uhidev0
> on upd0. But the `usbhid-ups` driver for NUT is unable to talk to it.
I'm successfully using a CyberPower CP1000PFCLCD with NUT and have
no problems with the
I have a CyberPower UPS that my OpenBSD 5.8 system sees just fine at uhidev0
on upd0. But the `usbhid-ups` driver for NUT is unable to talk to it.
There are a handful of older comments in the lists that offer a couple of
alternatives. One involved disabling the upd driver and messing with usb
quir
K K [kk...@outlook.com] wrote:
> I thought Intel, but I speak out of impressions, not backed by any facts.
>
David Gwynne who is working on the Myricom driver recommends the intel card
if that helps
> What is the take of OpenBSD developers on this?
> Are they any plans?
>
There's a lot of wor
Just did a fresh install of 6.0/amd64 on my HP 250 G4 laptop with
Celeron N3050 CPU. 5.9 was working, but 6.0 panics on the first boot
immediately after installing base sets.
I took pictures with cellphone digital camera; it's the only one I have.
The first images are cut off a little, so I took
> I think Intel and Myricom are going to be the best-supported 10GbE on
> OpenBSD at the moment.
I thought Intel, but I speak out of impressions, not backed by any facts.
> The best performance today will be with a processor that packs a lot
> of punch into a smaller number of cores. I'm using X
On 11.9.2016. 19:17, K wrote:
> All,
>
> This message is a call for people who are interested to benchmark commodity
> hardware with the goal of pushing as much PPS as possible through OpenBSD.
> The initial target is to reach 10 Mpps at 64 bytes (or more precisely 84
> bytes with interpacket gap)
On 09/11/16 19:46, K K wrote:
> // Previous email bounced, so I resend it. Sorry for duplicate //
Just curious, if you look at the bounce, would that be a
DMARC-worshipper failing to understand mailing list mail?
I'm researching what will likely be a longish, fact-based rant on the
subject.
- P
K [k...@protonmail.com] wrote:
> All,
>
> This message is a call for people who are interested to benchmark commodity
> hardware with the goal of pushing as much PPS as possible through OpenBSD.
> The initial target is to reach 10 Mpps at 64 bytes (or more precisely 84
> bytes with interpacket gap
// Previous email bounced, so I resend it. Sorry for duplicate //
All,
This message is a call for people who are interested to benchmark commodity
hardware with the goal of pushing as much PPS as possible through OpenBSD.
The initial target is to reach 10 Mpps at 64 bytes (or more precisely 84
by
All,
This message is a call for people who are interested to benchmark commodity
hardware with the goal of pushing as much PPS as possible through OpenBSD.
The initial target is to reach 10 Mpps at 64 bytes (or more precisely 84
bytes with interpacket gap) and if the experiment proves to be succes
On Saturday 10 Sep 2016 13:54:50 Theo de Raadt wrote:
> Summary: The OP has a learning disability. He should probably stay in
> Linux land, where the field is large, and his inability can remain
> hidden. See, once again I am not insulting Linux.
You sell OpenBSD short somewhat.
I've vast amo
Hi,
I'm moving to OpenBSD for primary use, I'll have to keep a Windows OS
for some specific purposes also.
Just thanks for the development of OpenBSD, it's very easy to use since
logical and well documented, I've been enjoying it for the past years
for what it deserved to do.
Also looked
Am 09.09.2016 um 20:16 schrieb Stuart Henderson:
On 2016/09/09 18:01, Holger Glaess wrote:
On 2016-09-09, Holger Glaess wrote:
inet6 2001:4dd0:af15:483d:20d:48ff:fe26:7a1f -> prefixlen 64
autoconf pltime 559190 vltime 2546390
inet6 2001:4dd0:af15:cbd9:20d:48ff:fe26:7a1f ->
14 matches
Mail list logo
