Re: request for testing: rbootd timeout fix

2016-04-15 Thread Philip Guenther
On Thu, Apr 14, 2016 at 3:15 PM, Martin Natano wrote: > In rbootd a struct bpf_timeval (with 32bit tv_sec) is copied to a struct > timeval (with 64 tv_sec) via bcopy(). This most likely causes > connections to not time out correctly in rbootd. I don't have an HP > machine to test this with. Who ow

Re: inteldrm diff that requires testing

2016-04-15 Thread Philip Guenther
On Fri, Apr 15, 2016 at 8:01 AM, Mark Kettenis wrote: > The diff below makes the HDMI output on Intel Bay Trail machines work. > Very useful for machines like the Lenovo Ideacentre Stick 300. But > this needs to be tested on other hardware as well. Especially on > machines with external displays

Re: librthread: don't change thread flags after fork()

2016-04-15 Thread Philip Guenther
Ping? Is no one using the GNUstep port? On Sun, Apr 10, 2016 at 10:05 PM, Philip Guenther wrote: > > The libpthread fork() wrapper makes two changes to the flags for the > process: it clears the 'detached' flag and sets the 'original' flag. I > now believe those are both wrong and should be le

Re: better rm / diff

2016-04-15 Thread Ted Unangst
Todd C. Miller wrote: > On Fri, 15 Apr 2016 14:04:20 -0400, "Ted Unangst" wrote: > > > I think this is a more reliable way of detecting rm -rf /. > > Previous effort was reverted due to false positives. > > I think it makes more sense to just check st_dev and st_ino. > Otherwise there is a race t

smu(4) fan speed

2016-04-15 Thread Marcus Glocker
Yesterday I've installed macppc -current on a G5. Since OF_getprop() for the 'unmanage-value' parameter fails on it, smu(4) sets the fan speed to 'max-value' instead, which is 3200RPM in my case. This makes the G5 sound louder than my vacuum cleaner. First I thought 'unmanage-value' is a typo and

Re: better rm / diff

2016-04-15 Thread Todd C. Miller
On Fri, 15 Apr 2016 14:04:20 -0400, "Ted Unangst" wrote: > I think this is a more reliable way of detecting rm -rf /. > Previous effort was reverted due to false positives. I think it makes more sense to just check st_dev and st_ino. Otherwise there is a race that can cause the check to fail due

better rm / diff

2016-04-15 Thread Ted Unangst
I think this is a more reliable way of detecting rm -rf /. Previous effort was reverted due to false positives. Index: rm.c === RCS file: /cvs/src/bin/rm/rm.c,v retrieving revision 1.36 diff -u -p -r1.36 rm.c --- rm.c1 Feb 201

intro.2 mention of pledge(2)

2016-04-15 Thread Rob Pierce
Does this make sense? Rob Index: intro.2 === RCS file: /cvs/src/lib/libc/sys/intro.2,v retrieving revision 1.63 diff -u -p -r1.63 intro.2 --- intro.2 6 Mar 2016 22:32:09 - 1.63 +++ intro.2 15 Apr 2016 16:26:24 -

inteldrm diff that requires testing

2016-04-15 Thread Mark Kettenis
The diff below makes the HDMI output on Intel Bay Trail machines work. Very useful for machines like the Lenovo Ideacentre Stick 300. But this needs to be tested on other hardware as well. Especially on machines with external displays. Index: intel_i2c.c

Re: less handrolled mbuf freeing code in uipc_mbuf.c

2016-04-15 Thread Mike Belopuhov
On 15 April 2016 at 07:35, David Gwynne wrote: > m_freem checks for NULL so the caller doesnt have to. > > ml_purge and m_purge were invented after some of the mq and ml code > was written, so fix that code to use the "new" functions. > > ok? > OK mikeb

Re: httpd: $DOCUMENT_URI macro fix for FastCGI

2016-04-15 Thread Christopher Zimmermann
On 2016-04-14 Tim Baumgard wrote: > > Christopher Zimmermann wrote: > > Tim Baumgard wrote: > >> According to convention and httpd.conf(5), the $DOCUMENT_URI macro > >> for FastCGI calls should expand to the request path instead of the > >> path alias. > > > > FastCGI / CGI is poorly document

Re: Any reason there's no way to persist pledge(2) state across exec?

2016-04-15 Thread Theo de Raadt
>What's the use for this? What program could use it? EXACTLY. Any proposal like yours requires a justification, so SHOW a program which needs it right now. At least show one. >On Sun, Apr 10, 2016 at 08:48:08AM -0700, Brennan Vincent wrote: >> Subject basically says it all. I think some could

Re: Pledge error handling

2016-04-15 Thread Theo de Raadt
>I noticed there are (at least 2) diferent ways to handle a pledge error (eg= >: /usr/src/usr.bin/): >If (pledge(args, NULL) =3D=3D -1) >. err(1, "pledge"); (wc; w; ..) >. perror("pledge"); exit(EXIT_CODE); (vi; openssl; ...) > >I am not familiar with the case of use of each function but perror + e