Relayd bug and uncommitted fix

2015-07-28 Thread trondd
There has been an outstanding relayd bug reported to bugs@ with a patch. I've been maintaining this fix locally for some time. Did it just fall through the cracks or is there a reason it hasn't been applied? http://marc.info/?l=openbsd-bugs&m=142644133217938&w=2 I use this functionality as a su

Re: audio: recover after missed interrupts

2015-07-28 Thread Alexey Suslikov
Alexandre Ratchov caoua.org> writes: > DPRINTFN(1, "%s: rec ptr wrapped, moving %d blocs\n", > DPRINTFN(1, "%s: play ptr wrapped, moving %d blocs\n", "blocs" in above DPRINTFNs should be "blocks", I think.

Re: Do not hide actual error for setusercontext

2015-07-28 Thread Vadim Zhukov
2015-07-28 16:59 GMT+03:00 Ted Unangst : > Vadim Zhukov wrote: >> I see no point in hidding underlying error message from user. >> Found while preparing chroot for doas run tests. >> >> Okay? > > setusercontext(3) doesn't say anything about setting errno, so it's not clear > it will always be set o

Re: doas keepenv fix

2015-07-28 Thread Ted Unangst
Vadim Zhukov wrote: > This fixes (as t-run-keepenv-path says) the problem found be Ze Loff: > http://marc.info/?l=openbsd-misc&m=143807620616845&w=2 > > Okay? ah, oops. that was supposed to be --nextras i think, but it's clearer this way. > -- > WBR, > Vadim Zhukov > > > Index: doas.c >

Re: Do not hide actual error for setusercontext

2015-07-28 Thread Ted Unangst
Vadim Zhukov wrote: > I see no point in hidding underlying error message from user. > Found while preparing chroot for doas run tests. > > Okay? setusercontext(3) doesn't say anything about setting errno, so it's not clear it will always be set or to a correct value.

Re: Do not hide actual error for setusercontext

2015-07-28 Thread Marc Espie
On Tue, Jul 28, 2015 at 04:10:37PM +0300, Vadim Zhukov wrote: > I see no point in hidding underlying error message from user. > Found while preparing chroot for doas run tests. > > Okay? > > -- > WBR, > Vadim Zhukov > > > Index: doas.c > ===

Re: softdep by default on AMD64

2015-07-28 Thread Chris Cappuccio
?? ?? [art.is...@yandex.ru] wrote: > On Fri, Jul 24, 2015 at 07:56:07AM +0100, Nicholas Marriott wrote: > > "generally reliable" HAHAHAHAHA > > Why irony? It's more or less true for ALL modern computing system. Think of it as a selling point. OpenBSD ffs softdep: On the cuttin

Do not hide actual error for setusercontext

2015-07-28 Thread Vadim Zhukov
I see no point in hidding underlying error message from user. Found while preparing chroot for doas run tests. Okay? -- WBR, Vadim Zhukov Index: doas.c === RCS file: /cvs/src/usr.bin/doas/doas.c,v retrieving revision 1.27 diff -u

doas keepenv fix

2015-07-28 Thread Vadim Zhukov
This fixes (as t-run-keepenv-path says) the problem found be Ze Loff: http://marc.info/?l=openbsd-misc&m=143807620616845&w=2 Okay? -- WBR, Vadim Zhukov Index: doas.c === RCS file: /cvs/src/usr.bin/doas/doas.c,v retrieving revision

Re: ppp(4) tweaks

2015-07-28 Thread Stefan Sperling
On Tue, Jul 28, 2015 at 01:50:01PM +0100, Stuart Henderson wrote: > Users looking for information about PPP on OpenBSD can easily get the > wrong impression that IPv6 is not supported at all for any PPP interfaces. > > - add Xr to relevant manpages for the other PPP implementations > - specificall

ppp(4) tweaks

2015-07-28 Thread Stuart Henderson
Users looking for information about PPP on OpenBSD can easily get the wrong impression that IPv6 is not supported at all for any PPP interfaces. - add Xr to relevant manpages for the other PPP implementations - specifically call out the fact that pppoe(4) supports IPv6 OK? Index: ppp.4 =

azalia: rework buffer position reporting code

2015-07-28 Thread Alexandre Ratchov
This diff simplifies the code that reads the DMA pointer and calls the audio(4) driver accordingly. - use simpler (and less) data structures, which makes the code shorter. - if multiple interrupts are missed, call audio(4) as many times as we missed interrupts (unless the pointer wrapped, whi

audio: ioctl to fetch snapshot of counters

2015-07-28 Thread Alexandre Ratchov
There are 4 audio counters, and we've one ioctl() to get each. So userland has to call the ioctl() one by one, and must take care to handle cases when a counters are inconsistent (i.e. don't belong to the same time). Inconsistencies are extreamly rare produce so the code is hard to test. This diff

Re: audio: recover after missed interrupts

2015-07-28 Thread Mike Larkin
On Mon, Jul 27, 2015 at 07:51:15PM +0200, Alexandre Ratchov wrote: > Sometimes the system may miss enough audio interrupts for DMA > pointers to wrap, which makes upper layers misbahave. > > This diff makes the audio driver properly recover, by detecting and > compensating for the missed interrupt