From owner-freebsd-questions@FreeBSD.ORG Mon May 11 14:04:49 2015 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E4107CE2 for ; Mon, 11 May 2015 14:04:49 +0000 (UTC) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id C09D01706 for ; Mon, 11 May 2015 14:04:49 +0000 (UTC) Received: by be-well.ilk.org (Postfix, from userid 1147) id E7A0333C22; Mon, 11 May 2015 10:04:42 -0400 (EDT) From: Lowell Gilbert To: Polytropon Cc: David Banning , questions@freebsd.org Subject: Re: permissions and ownership of /usr/src References: <20150510190342.GA9986@skytracker.ca> <20150510234531.f2398880.freebsd@edvax.de> Date: Mon, 11 May 2015 10:04:42 -0400 In-Reply-To: <20150510234531.f2398880.freebsd@edvax.de> (Polytropon's message of "Sun, 10 May 2015 23:45:31 +0200") Message-ID: <44r3qnfbwl.fsf@be-well.ilk.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 May 2015 14:04:50 -0000 Polytropon writes: > On Sun, 10 May 2015 15:03:44 -0400, David Banning wrote: >> Can anyone tell me what the permissions - ownership are/should >> be for /usr/src ? > > /usr/src should belong to root:wheel and have rwxr-xr-x permissions > (those are the defaults). Does mergemaster indicate an error for > /usr/src itself or for a subdirectory thereof? Or, if the bandwidth isn't a big deal, remove the whole tree and do a fresh "svn checkout". Or remove the directory where the error is happening, and do an "svn update". But, basically, everything shown looks fine (assuming that svn is being run by root, which doesn't necessarily have to be the case), and the actual error message almost certainly indicated a more precise problem. > You probably can restore /usr/src by using the mtree specification > in /etc/mtree/BSD.usr.dist. mtree won't help. That's because the ownership of the source tree isn't very important, as long as untrusted users can't write to it. The truly paranoid might create a dedicated user with virtually no access rights *except* to the source tree. Group write access may needed in some setups as well.