Re: USB Printer Prebloms

On Tue, Mar 03, 2020 at 10:57:03PM -0700, Duncan Patton a Campbell wrote: > > I've had problems getting an old Brother printer to work (again) > and have managed to locate/understand? the source of the problems. > > 1. ulpt must be disabled: > # config -ef /bsd > ukc> disable ulpt > ukc> quit >

Re: Time jumping forward issue under OpenBSD 6.6 VMM

‐‐‐ Original Message ‐‐‐ On Tuesday, March 3, 2020 8:52 PM, Jordan Geoghegan wrote: > The clocks are basically broken on vmm. The pvclock stuff is definitely > an improvement, but it's still not there. There's still a ways to go > before we have proper, reasonably accurate clocks for vmm

octeon splassert: yield: want 0 have 1

hi i get often this message "splassert: yield: want 0 have 1" in my dmesg. did i have somthing to care ? my hardware ist an edgerouter 6p . holger Copyright (c) 1982, 1986, 1989, 1991, 1993     The Regents of the University of California.  All rights reserved. Copyright (c)

USB Printer Prebloms

I've had problems getting an old Brother printer to work (again) and have managed to locate/understand? the source of the problems. 1. ulpt must be disabled: # config -ef /bsd ukc> disable ulpt ukc> quit 2. modifying the kernel changes the kernel checksum so to get it to relink sha256 -h

Pledge Policy for Tset Binary

Hi, I was looking at the pledge policy for the tset binary and I was wondering why wpath is necessary. I removed the group from the pledge and did some basic tests with the utility and there was no error. Removing any of the other groups produces an error so they seem necessary. Any assistance

Hardening browser

Hi, in the following message: https://marc.info/?l=openbsd-misc=158110613210895=2 Theo discourages to use unveil instead of chroot. I asked if he suggests the same for the browser but he asked that chroot is onlye for *root*. Then what should I do to hardening the most exposed piece of code that

Re: Time jumping forward issue under OpenBSD 6.6 VMM

On 2020-03-03 07:43, mabi wrote: Hello, I am running an OpenBSD 6.6 VMM server with a few virtual machines also running 6.6 and noticed that one of them which is running Dovecot 2.3.9 package outputs the following warning every few 10-15 seconds: dovecot: imap: Warning: Time jumped

Re: Time jumping forward issue under OpenBSD 6.6 VMM

‐‐‐ Original Message ‐‐‐ On Tuesday, March 3, 2020 5:58 PM, Ian Gregory wrote: > I've had similar issues with timekeeping within guests of VMM, > although there are improvements in -current with the pvclock time > source. Since the fix below I now see occasional instances of the >

Re: Having PF enabled breaks up rsync (and scp) over ssh connections

Jyri Hovila [Turvamies.fi] [jyri.hov...@turvamies.fi] wrote: > Hello everyone! > > Now here's a mysterious one -- I've been working on this for weeks and still > have no clue what's causing it. > > "client_loop: send disconnect: Broken pipe > > As soon as I disable pf entirely, the problem

Re: Time jumping forward issue under OpenBSD 6.6 VMM

On Tue, 3 Mar 2020 at 15:47, mabi wrote: > It looks like there is a time issue on that VM although I am running the > default ntpd of OpenBSD 6.6 and I have added the following parameter into my > /etc/sysctl.conf on that VM: > > kern.timecounter.hardware=tsc I've had similar issues with

Re: man to render pure text? (or a pipe in vi macros ?)

hello Ingo, > > rare cases. so i finally think it's not worth ... col -b is an elegant > > solution. > Premature optimization is evil. this case isn't about optimizing, it's about slowing down 99.999% to add a case that already have an elegant and simple solution. but as i said: i don't

Re: man to render pure text? (or a pipe in vi macros ?)

Hi Marc, Marc Chantreux wrote on Tue, Mar 03, 2020 at 10:05:41AM +0100: > Ingo Schwarze wrote: >> :map K yw:E /tmp/vi.keyword.$$p!!xargs man >> >> i get: >> >> Error detected while processing function >> line 30: >> E132: Function call depth is higher than 'maxfuncdepth' > it's a

Time jumping forward issue under OpenBSD 6.6 VMM

Hello, I am running an OpenBSD 6.6 VMM server with a few virtual machines also running 6.6 and noticed that one of them which is running Dovecot 2.3.9 package outputs the following warning every few 10-15 seconds: dovecot: imap: Warning: Time jumped forwards 28.294585 seconds It looks like

Re: Web documentation available offline by default?

On 2020-03-02, Peter N. M. Hansteen wrote: > I was thinking of the probably quite unlikely event that somebody who wants > this > comes up with an actually reproducible way that could be turned into an > otherwise > unremarkable make target. >From experience with other generated files: it

Re: upgrade i386 kernel to amd64

On 2020-03-02, Justin Muir wrote: > Hello all, > > Running GENERIC i386 kernel on on a 64-bit amd machine. Just wondering > whether an upgrade amd64 is warranted. Any opinions? Generally yes, unless you are low on memory. > If so, just upgrade system? Re-compile kernel? Other options? Do NOT

Re: man to render pure text? (or a pipe in vi macros ?)

Le 02/03/2020 à 17:59, Marc Chantreux a écrit : i felt dumb reading this as i gave a try to the mandoc man. but i just double checked: man mandoc|col -b|grep -w col Hmmm, here I have it though: https://man.openbsd.org/mandoc In the “ASCII Output” paragraph. -- David

Re: man to render pure text? (or a pipe in vi macros ?)

hello Ingo, > :map K yw:E /tmp/vi.keyword.$$p!!xargs man > > i get: > > Error detected while processing function > line 30: > E132: Function call depth is higher than 'maxfuncdepth' > Press ENTER or type command to continue it's a bug in the :E command, i reported it there: