Re: [PATCH] Update link to the VMware backdoor docs

Bump. Index: src/sys/dev/pv/vmt.c === RCS file: /cvs/src/sys/dev/pv/vmt.c,v retrieving revision 1.12 diff -u -p -r1.12 vmt.c --- src/sys/dev/pv/vmt.c3 Feb 2017 08:23:01 - 1.12 +++ src/sys/dev/pv/vmt.c1 Mar 2017

Re: kern_pledge: sysctl abort printing

> >From my /var/log/messages: > > Jun 1 22:10:25 idefix /bsd: dig(9111): sysctl 2: 1 13 16 0 -32064 32639 > Jun 1 22:10:25 idefix /bsd: dig(9111): syscall 202 "" > Jun 1 22:10:57 idefix /bsd: dig(56469): sysctl 2: 1 13 0 0 -129840 32639 > Jun 1 22:10:57 idefix /bsd: dig(56469): syscall 202 ""

kern_pledge: sysctl abort printing

>From my /var/log/messages: Jun 1 22:10:25 idefix /bsd: dig(9111): sysctl 2: 1 13 16 0 -32064 32639 Jun 1 22:10:25 idefix /bsd: dig(9111): syscall 202 "" Jun 1 22:10:57 idefix /bsd: dig(56469): sysctl 2: 1 13 0 0 -129840 32639 Jun 1 22:10:57 idefix /bsd: dig(56469): syscall 202 "" Jun 1

i386 clang: fix binutils build

On i386, binutils-2.17/gas fails to build with clang: /usr/src/gnu/usr.bin/binutils-2.17/gas/config/tc-i386.c:2107:53: error: signed shift result (0x1) requires 34 bits to represent, but 'offsetT' (aka 'long') only has 32 bits [-Werror,-Wshift-overflow] &&

Re: Correction for www/faq/faq10.html - yptest is dead

On Fri, Jun 02, 2017 at 02:04:41PM -0400, Kurt Mosiejczuk wrote: > Was looking over the YP section of the FAQ and was intrigued to learn of > yptest(8). Except it was sent to the attic years ago. So this eliminates > its mention as a useful YP debugging tool. fixed, thanks! > > Index:

Correction for www/faq/faq10.html - yptest is dead

Was looking over the YP section of the FAQ and was intrigued to learn of yptest(8). Except it was sent to the attic years ago. So this eliminates its mention as a useful YP debugging tool. Index: faq/faq10.html === RCS file:

Re: Question on getcwd(3) behavior on OpenBSD

On Fri, Jun 02, 2017 at 04:37:08PM +0200, Alexander Bochmann wrote: > > to OpenBSD 6.1. I've found out that git will abort in one scenario > > where there is a directory in the tree where the user has execute > > permissions but not read permissions. > Did you use the git version from ports

brconfig: Unify/fix strtoul(3) handling

Besides fixing a tautological 'v < 0' and using more descriptive/less errorprone sizeof(target) this patch unifies strtoul(3) handling both logically and cosmetically. Index: brconfig.c === RCS file:

ksh(1): custom completion for command containing hyphens

Hi, Custom completions in ksh is currently limited to commands that does not contain hyphens since such a character cannot be part of an identifier. We could cheat and replace hyphens with underscores upon performing completions. The motivation behind this is that I want to add completions for

Re: Question on getcwd(3) behavior on OpenBSD

...on Wed, May 31, 2017 at 02:46:59PM -0400, Kurt Mosiejczuk wrote: > to OpenBSD 6.1. I've found out that git will abort in one scenario > where there is a directory in the tree where the user has execute > permissions but not read permissions. Did you use the git version from ports

Re: fortune(6): fix an infinite loop

On Fri, Jun 02, 2017 at 04:02:02PM +0200, Frederic Cambus wrote: > Hi tech@, > > When invoking fortune with the -l option (to get long dictums only), > the program gets stuck in an infinite loop because fortlen() doesn't > return the fortune length correctly. > > Comments? OK? nice, ok note

fortune(6): fix an infinite loop

Hi tech@, When invoking fortune with the -l option (to get long dictums only), the program gets stuck in an infinite loop because fortlen() doesn't return the fortune length correctly. Comments? OK? Index: games/fortune/fortune/fortune.c

Re: backport from clang trunk

On Fri, Jun 02, 2017 at 12:18:06PM +0200, Marc Espie wrote: > I managed to get this one in. > > the rationale being that -Wno-#warnings, while highly descriptive, is a total > bitch to pass through shell-scripts, configure, makefiles... and gcc names > the same option -Wno-cpp anyway. > > >

Re: backport from clang trunk

> Date: Fri, 2 Jun 2017 12:18:06 +0200 > From: Marc Espie > > I managed to get this one in. > > the rationale being that -Wno-#warnings, while highly descriptive, is a total > bitch to pass through shell-scripts, configure, makefiles... and gcc names > the same option -Wno-cpp

backport from clang trunk

I managed to get this one in. the rationale being that -Wno-#warnings, while highly descriptive, is a total bitch to pass through shell-scripts, configure, makefiles... and gcc names the same option -Wno-cpp anyway. okay ? Index: DiagnosticGroups.td