Re: [PATCH] column(1): -r to right justify

2018-07-08 Thread Ingo Schwarze
Hi Job, Job Snijders wrote on Wed, Jul 04, 2018 at 02:09:56PM +0200: > Following some back and forth on how disklabel output should be > formatted, I proposed to Kenneth to extend the column(1) utility. > All that was missing is the ability to right justify. I'm not totally sure we should add

Re: if_enc.c: "rdomain" is more descriptive than "id"

2018-07-08 Thread Sebastian Benoit
Jeremie Courreges-Anglas(j...@wxcvbn.org) on 2018.07.08 15:26:33 +0200: > > Maybe not very important, but "id" sounds a tad too generic to me, and > it looks like we're really dealing with an rdomain here, so here's a diff. > > Thoughts? yes please, if only for making searching easier > ok?

Re: xenodm: source Xsetup before initializing the greeter

2018-07-08 Thread Jeremie Courreges-Anglas
On Sun, Jul 08 2018, Matthieu Herrb wrote: > Hi, > > prompted by a question by weerd@ who wanted to be able to rotate the > screen of his gpd win *before* the Xenodm greeter is displayed, I came > up with this (simple) patch that sources the Xsetup_0 script before > initializing the greeter

Re: Fix a kernelpanic when playing with rdomain(4) and enc(4)

2018-07-08 Thread Jeremie Courreges-Anglas
On Sun, Jun 24 2018, Denis Fondras wrote: > When removing enc(4) interface from rdomain, the kernel panics randomly > (memcpy() seems to copy outside of the mallocarray() boundaries) with > something > like : > > Data modified on freelist: word -35183699295756 of object 0x8059da80 >

Re: systat(1) iostat vs. iostat(1)

2018-07-08 Thread Sebastian Benoit
yes, its bytes. ok benno@ Jason McIntyre(j...@kerhand.co.uk) on 2018.07.07 17:20:19 +0100: > On Sat, Jul 07, 2018 at 08:28:52AM +0200, Marcus MERIGHI wrote: > > Hello, > > > > when I run 'iostat(1) sd1 1' I get the transfer speed in MB/s. Running > > 'systat(1) iostat 1' in parallel I get the

Re: Fix a kernelpanic when playing with rdomain(4) and enc(4)

2018-07-08 Thread Jeremie Courreges-Anglas
On Sun, Jul 08 2018, Jeremie Courreges-Anglas wrote: > On Sun, Jun 24 2018, Denis Fondras wrote: >> When removing enc(4) interface from rdomain, the kernel panics randomly >> (memcpy() seems to copy outside of the mallocarray() boundaries) with >> something >> like : >> >> Data modified on

Re: Fix a kernelpanic when playing with rdomain(4) and enc(4)

2018-07-08 Thread Denis Fondras
OK denis@ On Sun, Jul 08, 2018 at 02:04:56PM +0200, Jeremie Courreges-Anglas wrote: > On Sun, Jul 08 2018, Jeremie Courreges-Anglas wrote: > > On Sun, Jun 24 2018, Denis Fondras wrote: > >> When removing enc(4) interface from rdomain, the kernel panics randomly > >> (memcpy() seems to copy

Re: systat(1) iostat vs. iostat(1)

2018-07-08 Thread Jason McIntyre
On Sat, Jul 07, 2018 at 08:28:52AM +0200, Marcus MERIGHI wrote: > Hello, > > when I run 'iostat(1) sd1 1' I get the transfer speed in MB/s. Running > 'systat(1) iostat 1' in parallel I get the transfer speed in bytes, as > calculations show. Therefore adjust the manual of systat(1): > kilobytes

if_enc.c: "rdomain" is more descriptive than "id"

2018-07-08 Thread Jeremie Courreges-Anglas
Maybe not very important, but "id" sounds a tad too generic to me, and it looks like we're really dealing with an rdomain here, so here's a diff. Thoughts? ok? Index: net/if_enc.c === RCS file: /cvs/src/sys/net/if_enc.c,v

xenodm: source Xsetup before initializing the greeter

2018-07-08 Thread Matthieu Herrb
Hi, prompted by a question by weerd@ who wanted to be able to rotate the screen of his gpd win *before* the Xenodm greeter is displayed, I came up with this (simple) patch that sources the Xsetup_0 script before initializing the greeter widget. I can't think of any down sides of doing this, and

netstart(8): check for root privileges

2018-07-08 Thread Theo Buehler
When running netstart as regular user, the output looks something like this: $ sh /etc/netstart iwn0 /etc/netstart[226]: /etc/soii.key: cannot open $(<) input sysctl: net.inet6.ip6.soiikey: Operation not permitted ifconfig: SIOCS80211NWID: Operation not permitted ifconfig: SIOCS80211WPAPSK:

Re: [PATCH] column(1): -r to right justify

2018-07-08 Thread Ingo Schwarze
An afterthought... Ingo Schwarze wrote on Sun, Jul 08, 2018 at 08:22:34PM +0200: > If you opt for requiring an argument, > then you can use a cut(1)-like syntax: Alternatively, you can use a syntax similar to tbl(7) "Layout" lines: rrll which allows later extensions like r|rclnl That's

disable seemingly unsupported MSI for AMD 17h/Raven Ridge HD Audio in azalia.c

2018-07-08 Thread Thomas Frohwein
Hi, It appears that HD Audio from AMD's generation Ryzen can't handle MSI. This leads to the bug that I reported here: https://marc.info/?l=openbsd-bugs=151648196215922=2 Disabling MSI resolves the problem on my current system which is a Raven Ridge APU. I don't have the Summit Ridge hardware

Re: usbdevs & hub ports status

2018-07-08 Thread Martin Pieuchot
On 04/07/18(Wed) 17:00, Martin Pieuchot wrote: > Diff below adds support for printing USB ports status. It includes an > ABI change as we currently do not export port status/change to userland. > > I'd really like to export the current cached value to userland via the > USB_DEVICEINFO ioctl(2)

Patch for column number in doas error messages

2018-07-08 Thread Phil Eaton
Hey, Doas currently tells you the line but not the column for syntax errors. In the case of a missing newline at the end of a line I was confused. So I added the column number to the message as well. Also, is there any interest in relaxing the grammar so a trailing rule without a newline is ok?

Re: disable seemingly unsupported MSI for AMD 17h/Raven Ridge HD Audio in azalia.c

2018-07-08 Thread Jonathan Gray
On Sun, Jul 08, 2018 at 12:15:39PM -0700, Thomas Frohwein wrote: > Hi, > > It appears that HD Audio from AMD's generation Ryzen can't handle MSI. > This leads to the bug that I reported here: > > https://marc.info/?l=openbsd-bugs=151648196215922=2 > > Disabling MSI resolves the problem on my

broadcom netxtreme-c/e driver

2018-07-08 Thread Jonathan Matthew
This started out as a port of freebsd's bnxt driver, but along the way I had to rewrite the interesting bits. NetXtreme-C/E (BCM573xx and BCM574xx) is a different line of chips to NetXtreme II 10G (BCM577xx, which mje was working on), and luckily for me it's much easier to talk to. The reason

ber.c: simplify ber_read()

2018-07-08 Thread Jeremie Courreges-Anglas
When looking at the recent changes in this file I noticed that the presence of both ber_read() and ber_readbuf() was due to an incomplete cleanup from my part. revision 1.32 date: 2018/02/08 18:02:06; author: jca; state: Exp; lines: +6 -22; commitid: YNQMco5lCS8YEifQ; Kill ber.c