[patch] macppc.html and sparc64.html old devices

2016-05-14 Thread Bryan Vyhmeister
I was just looking at macppc.html and noticed that lmc(4) was listed along with art(4) as available WAN adapters and both were sent to the bit bucket in the sky 13 months and 19 months ago respectively. I checked the other platform pages and found lmc(4) also listed on sparc64.html. Since we don't

powerpc/libc: kill __cerror

2016-05-14 Thread Philip Guenther
Now that the TIB conversion is complete, it's safe to convert powerpc to setting errno directly in the syscall stub without having to go through a separate function __cerror (which was itself using __errno!). This has made it through a build and is working on building sets right now. ok? Phi

Re: Is loss of read-only /usr permanent?

2016-05-14 Thread lists
Sat, 14 May 2016 12:25:47 -0400 RD Thrush > On 05/14/16 04:34, Craig Skinner wrote: > > Hi RD/all, > > > > On 2016-05-13 Fri 17:16 PM |, RD Thrush wrote: > >> > >> # cp -p /etc/fstab /etc/fstab.orig > >> # sed -e 's,/usr ffs rw,/usr ffs ro,' /etc/fstab > >> # shutdown -f now > >> Shutdown NOW!

Re: Headers cleanup + use getprogname() for test(1)

2016-05-14 Thread Philip Guenther
On Sat, May 14, 2016 at 2:28 AM, Mark Kettenis wrote: >> Date: Sat, 14 May 2016 13:08:54 +0200 >> From: Frederic Cambus >> >> Hi tech@, >> >> Headers cleanup + use getprogname() for test(1) > > *Never* include directly. +1 > And despite some of the noises guenther@ made recenly, I don't think

Re: Is loss of read-only /usr permanent?

2016-05-14 Thread Kevin Chadwick
> Finally, the read only file systems on a writable medium susceptible > to all sorts of failure modes is a silly silly useless trick. This > does not provide any real technical benefit but your own discomfort. > Pipe it down a bit will you. I use ro root, /dev in tmpfs and /usr ro as well as an

Re: Is loss of read-only /usr permanent?

2016-05-14 Thread lists
Sat, 14 May 2016 12:24:50 -0400 RD Thrush > On 05/13/16 23:34, Theo de Raadt wrote: > >> The report is fairly easy to reproduce. Make the /usr filesystem > >> read-only in /etc/fstab, go to single user mode and exit back to > >> multi-user. I've appended a transcript. > > > > This does not ma

Re: Is loss of read-only /usr permanent?

2016-05-14 Thread Theo de Raadt
> Thanks, that would work fine. It may be useful as a note in the upgrade guide > for 6.0 for those (apparently few of us) who have a read-only /usr. The documentation describes the system as it is shipped. It does not spend hundreds of pages satisfying tweakers.

Re: Is loss of read-only /usr permanent?

2016-05-14 Thread RD Thrush
On 05/13/16 19:37, Edgar Pettijohn wrote: >> On May 13, 2016, at 4:16 PM, RD Thrush wrote: >> >> On 05/13/16 11:07, Theo de Raadt wrote: Since the anti-ROP mechanism in libc [2] was added in late April, -current with read-only /usr produces something like the following message: re-

Re: Is loss of read-only /usr permanent?

2016-05-14 Thread RD Thrush
On 05/13/16 23:34, Theo de Raadt wrote: >> The report is fairly easy to reproduce. Make the /usr filesystem >> read-only in /etc/fstab, go to single user mode and exit back to >> multi-user. I've appended a transcript. > > This does not matter. It is your configuration. It is not the default.

Re: Is loss of read-only /usr permanent?

2016-05-14 Thread RD Thrush
On 05/13/16 19:40, Chris Cappuccio wrote: > RD Thrush [openbsd-t...@thrush.com] wrote: >> On 05/13/16 11:07, Theo de Raadt wrote: Since the anti-ROP mechanism in libc [2] was added in late April, -current with read-only /usr produces something like the following message: re-ordering

Re: Is loss of read-only /usr permanent?

2016-05-14 Thread RD Thrush
On 05/14/16 04:34, Craig Skinner wrote: > Hi RD/all, > > On 2016-05-13 Fri 17:16 PM |, RD Thrush wrote: >> >> # cp -p /etc/fstab /etc/fstab.orig >> # sed -e 's,/usr ffs rw,/usr ffs ro,' /etc/fstab >> # shutdown -f now >> Shutdown NOW! >> shutdown: [pid 82541] > > Something like this in /etc/rc mi

Re: opendev and pledge: "privsep" for dumpfs(8)

2016-05-14 Thread Theo de Raadt
> > Must say the forking and piping seems to be a bit silly for a program > > like this. Certainly adds alot of complexity. Why not simply call > > opendev up front for each filesystem, creating a list of names and > > filedescriptors before you pledge, and then iterate over that list > > afterwa

Re: opendev and pledge: "privsep" for dumpfs(8)

2016-05-14 Thread Theo de Raadt
> Must say the forking and piping seems to be a bit silly for a program > like this. Certainly adds alot of complexity. Why not simply call > opendev up front for each filesystem, creating a list of names and > filedescriptors before you pledge, and then iterate over that list > afterwards? > >

Re: opendev and pledge: "privsep" for dumpfs(8)

2016-05-14 Thread Mark Kettenis
> Date: Sat, 14 May 2016 17:07:45 +0200 > From: Theo Buehler > > Here's a new version with lots of help and input from semarie, thanks! > Besides lots of small tweaks, the main improvements are: > > * fork one pledged child per fs which reads the data. > * pipe the data to the unpledged parent t

Re: opendev and pledge: "privsep" for dumpfs(8)

2016-05-14 Thread Theo Buehler
Here's a new version with lots of help and input from semarie, thanks! Besides lots of small tweaks, the main improvements are: * fork one pledged child per fs which reads the data. * pipe the data to the unpledged parent that dumps it to stdout. * parent waits for current child, then calls opende

wsmouse_input: hidms, pms

2016-05-14 Thread Ulf Brosziewski
The new input-processing functions of wsmouse seem to work well for touchpads, and it might be time to update the mouse drivers now. I start with the two drivers that I could test myself, hidms (ums) and pms. Please note that hidms can mix, in principle, absolute and relative coordinates. The new

Re: Is loss of read-only /usr permanent?

2016-05-14 Thread lists
Fri, 13 May 2016 17:16:19 -0400 RD Thrush > On 05/13/16 11:07, Theo de Raadt wrote: > >> Since the anti-ROP mechanism in libc [2] was added in late April, -current > >> with read-only /usr produces something like the following message: > >> re-ordering libraries:install: /usr/lib/INS@OPOjn7ck17:

Re: Is loss of read-only /usr permanent?

2016-05-14 Thread lists
Fri, 13 May 2016 18:55:58 -0500 Chris Bennett > I think you are totally missing the point that Theo just made. You too. > Marking partitions as read-only is useful, when and only when > appropriate. Expand on a wrong idea does not make it right. Your advice is hurting naive readers. This thre

Use proper bool types in /usr/games

2016-05-14 Thread Frederic Cambus
Hi tech@, Proper bool types for fortune(6) and monop(6). Index: games/fortune/fortune/fortune.c === RCS file: /cvs/src/games/fortune/fortune/fortune.c,v retrieving revision 1.55 diff -u -p -r1.55 fortune.c --- games/fortune/fortune/f

Re: Headers cleanup + use getprogname() for test(1)

2016-05-14 Thread Mark Kettenis
> Date: Sat, 14 May 2016 13:08:54 +0200 > From: Frederic Cambus > > Hi tech@, > > Headers cleanup + use getprogname() for test(1) *Never* include directly. And despite some of the noises guenther@ made recenly, I don't think we have made the decision to drop __progname in favour of getprognam

Headers cleanup + use getprogname() for test(1)

2016-05-14 Thread Frederic Cambus
Hi tech@, Headers cleanup + use getprogname() for test(1) Index: bin/test/test.c === RCS file: /cvs/src/bin/test/test.c,v retrieving revision 1.16 diff -u -p -r1.16 test.c --- bin/test/test.c 13 Jan 2016 13:13:04 - 1.16

Re: Is loss of read-only /usr permanent?

2016-05-14 Thread Craig Skinner
Hi RD/all, On 2016-05-13 Fri 17:16 PM |, RD Thrush wrote: > > # cp -p /etc/fstab /etc/fstab.orig > # sed -e 's,/usr ffs rw,/usr ffs ro,' /etc/fstab > # shutdown -f now > Shutdown NOW! > shutdown: [pid 82541] Something like this in /etc/rc might help here: rebuildlibs() { mount -d /usr |