From owner-freebsd-current@FreeBSD.ORG Thu Oct 18 11:43:05 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 624BE16A417 for ; Thu, 18 Oct 2007 11:43:05 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (lindfield.ch [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 2DF9413C45D for ; Thu, 18 Oct 2007 11:43:05 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:62527 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IiTmJ-0005Te-Gi for freebsd-current@freebsd.org; Thu, 18 Oct 2007 11:43:03 +0000 Message-ID: <471746C7.20306@conducive.net> Date: Thu, 18 Oct 2007 07:43:03 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <00bd01c810ec$10371230$0c00a8c0@Artem> <8cb6106e0710171143m3dff7546o457192ede76e6598@mail.gmail.com> <012c01c810f3$aafeecf0$0c00a8c0@Artem> <20071017193615.GO9006@server.vk2pj.dyndns.org> <471667DB.1010601@conducive.net> <47170FF1.3050602@moneybookers.com> In-Reply-To: <47170FF1.3050602@moneybookers.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Broken su in current - trying to fix myself, help needed! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Oct 2007 11:43:05 -0000 Stefan Lambrev wrote: > Hi, > *snip* >> I will not be surprised if it occurs when building as an 'ordinary >> user' and does NOT occur when building as root.... >> >> BNL (BSD's Not Linux).... >> > I see something similar on all ports that have OPTIONS (make config). > Here is example (do this as user member of wheel, but not root): > Stop right there. '..NOT root'?? Why would I DO that? I'd *expect* a port to have problems if not invoked as EUID 'root' ls -lF /usr/ports// Owner of the entire tree is 'root' with rwx and rw-. Group and 'others' do not have 'w' privs, only 'r--'. Note a 'make' cycle creates a ~/work/ within that tree. When invoked as root. Cannot do so otherwise. HTH do you expect to write the results output by ./configure to a dirtree you do not have the privilege to write to *at all*? pkg_add and pkgsrc work a bit diferently w/r their workspace, but these, too can be expected to encounter problems if invoked by other than 'root'. If nothing else breaks first, they can neither install to the various ~/lib, ~/libexec, ~/bin, ~/sbin or even ~/etc dirtrees, nor update /var/db/pkg. Read ls -lF on those critters, and you'll see why. IF/AS/WHEN you want to take an advance look at what *would* transpire in a build w/o doing it as 'root', you need to open the tarball(s) elsewhere, where your current EUID *does* have rwx privs. I mkdir (and own) /usr/local/src/ for that purpose. As good a name as any ..but BSD's (still) Not Linux Bill