On 2020-08-17, Doug Moss wrote:
>
> Is it possible with OpenBSD i386 to use the parallel port for lcdproc?
>
> More specifically:
> Did something change at OpenBSD i386 between 5.9 and 6.0
> related to parallel port / lpt hardware permissions?
>
> Up to OpenBSD i386 5.9,
> I used to be able to
On Tue, Aug 11, 2020 at 2:07 AM Rupert Gallagher wrote:
>
> Omit the last line of the manual, because there is no need for it.
>
Well of course there's no need for it, but why on Earth should that
mean that it shouldn't be there?
--
Aaron Mason - Programmer, open source addict
I've taken my
You'll need to chown/chmod it narrowly to the uid who wants to use it.
You want to constrain use of the device driver as much as you can.
>Is it possible with OpenBSD i386 to use the parallel port for lcdproc?
>
>More specifically:
>Did something change at OpenBSD i386 between 5.9 and 6.0
Were you able to resolve this issue?
> On Jun 10, 2020, at 15:59, obs...@loopw.com wrote:
>
> I have a small fleet of protectli firewalls, all of them with em nics. Only
> the units i’ve upgraded to 6.7 are showing interface errors, where 6.6 is
> definitely not.
>
>
>> On Jun 8, 2020, at
> On 10 Aug 2020, at 14:00, Marko Cupać wrote:
>
>>> On 4 Aug 2020, at 17:04, Marko Cupać wrote:
>>>
>>> Hi,
>>>
>>> I have recently upgraded (actually installed from scratch and copied
>>> config files) one of my firewalls from 6.6 to 6.7, and (sys)patched
>>> it to 017_dix. Everything
Hi,
It depends on the workload. I'd have thought for most things the max
> really usable at the moment is probably somewhere in the region of 4-8
> cpu cores before kernel locking gets in the way too much.
>
> FWIW sparc64 ports builds are now done on T4 and they're really fast.
> I think (but am
On Sun, Aug 16, 2020 at 02:34:27PM -0400, trondd wrote:
> Oh, I see what you're doing. BOTH listen lines are active in the second
> server block. When you connect to port 443 with that config, which TLS
> settings does it use? I want to guess that because you're lisening on
> port 8000
On Sun, August 16, 2020 1:23 pm, hisacro wrote:
> Aug 16, 2020, 11:44 AM by tro...@kagu-tsuchi.com:
>
>> Because it's not the same IP and port anymore. You can only have one
>> thing listening on an ip+port
>
> I got a working httpd config with same IP and same Port
>
> server "domain.tld" {
>
Aug 16, 2020, 11:44 AM by tro...@kagu-tsuchi.com:
> Because it's not the same IP and port anymore. You can only have one
> thing listening on an ip+port
I got a working httpd config with same IP and same Port
server "domain.tld" {
listen on $ext_ip tls port 443
tls {
Aug 16, 2020, 7:50 AM by tro...@kagu-tsuchi.com:
>>On Sat, Aug 15, 2020 at 04:13:51PM -0700, hisacro wrote:
>
>> $ doas httpd -nv
>> server "sub.domain.tld": tls configuration mismatch on same address/port
>>
>> instead of defining same cipher and ecdhe, uncommenting
>> "listen on 0.0.0.0 port
On Sun, August 16, 2020 1:49 am, hisacro wrote:
> Aug 16, 2020, 7:50 AM by tro...@kagu-tsuchi.com:
>
>>>On Sat, Aug 15, 2020 at 04:13:51PM -0700, hisacro wrote:
>>
>>> $ doas httpd -nv
>>> server "sub.domain.tld": tls configuration mismatch on same
>>> address/port
>>>
>>> instead of defining same
11 matches
Mail list logo
