Run newvers.sh with umask 007 to work around permission issues that

cause 'make release' fail the first time around after building GENERIC
if /usr/obj/ wasn't cleaned out properly. The proper fix would be to
implement privdrop for kernel builds but this is trickier than it looks
at first sight.

discussed with deraadt

diff --git a/share/man/man8/release.8 b/share/man/man8/release.8
index 7974752..ca243c2 100644 (file)
--- a/share/man/man8/release.8
+++ b/share/man/man8/release.8
@@ -1,4 +1,4 @@
-.\"    $OpenBSD: release.8,v 1.91 2017/12/23 16:20:21 sthen Exp $
+.\"    $OpenBSD: release.8,v 1.92 2018/02/06 08:42:33 tb Exp $
 .\"
 .\"    Copyright (c) 2000 Marco S. Hyman
 .\"    Copyright (c) 2016 Theo Buehler <tb@openbsd.org>
@@ -10,7 +10,7 @@
 .\"    LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
 .\"    FOR A PARTICULAR PURPOSE.
 .\"
-.Dd $Mdocdate: December 23 2017 $
+.Dd $Mdocdate: February 6 2018 $
 .Dt RELEASE 8
 .Os
 .Sh NAME
@@ -130,11 +130,6 @@ The build process will place the object files in a tree under
 .Pa /usr/obj .
 This directory must be owned by build:wobj with mode 770.
 .Pp
-The first time, the
-.Pa /usr/obj
-directory
-.Em must be
-cleaned out completely before proceeding to avoid permission issues.
 After a successful
 .Nm
 build, this is no longer needed.

diff --git a/sys/conf/newvers.sh b/sys/conf/newvers.sh
index f681581..e8e62d4 100644 (file)
--- a/sys/conf/newvers.sh
+++ b/sys/conf/newvers.sh
@@ -1,6 +1,6 @@
 #!/bin/sh -
 #
-#      $OpenBSD: newvers.sh,v 1.157 2017/10/04 17:59:41 benno Exp $
+#      $OpenBSD: newvers.sh,v 1.158 2018/02/06 08:42:33 tb Exp $
 #      $NetBSD: newvers.sh,v 1.17.2.1 1995/10/12 05:17:11 jtc Exp $
 #
 # Copyright (c) 1984, 1986, 1990, 1993
@@ -32,6 +32,8 @@
 #
 #      @(#)newvers.sh  8.1 (Berkeley) 4/20/94
 
+umask 007
+
 if [ ! -r version -o ! -s version ]
 then
        echo 0 > version