From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 18:35:52 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC16616A4CE for ; Fri, 21 Jan 2005 18:35:52 +0000 (GMT) Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [211.29.132.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 172A043D54 for ; Fri, 21 Jan 2005 18:35:52 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j0LIZlM0006613 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 22 Jan 2005 05:35:48 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j0LIZkxP072616; Sat, 22 Jan 2005 05:35:46 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j0LIZkT6072615; Sat, 22 Jan 2005 05:35:46 +1100 (EST) (envelope-from pjeremy) Date: Sat, 22 Jan 2005 05:35:46 +1100 From: Peter Jeremy To: Ryan Sommers Message-ID: <20050121183546.GC68808@cirb503493.alcatel.com.au> References: <20050121151747.GA36660@obiwan.tataz.chchile.org> <50158.208.4.77.66.1106323175.squirrel@208.4.77.66> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50158.208.4.77.66.1106323175.squirrel@208.4.77.66> User-Agent: Mutt/1.4.2i cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re: Cannot install kernel as user X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Fri, 21 Jan 2005 18:35:53 -0000 On Fri, 2005-Jan-21 08:59:35 -0700, Ryan Sommers wrote: >> I thought about adding a flag such as NO_INSTALLCHOWN in both >> kern.post.mk and kmod.mk. What do you think of the idea ? >> >> I saw there are KMODOWN and KMODGRP in kmod.mk, but it seems there is >> no similar facility in kern.post.mk. Maybe it would be worth having >> KERNOWN and KERNGRP as well. >> >> I can submit a patch if asked. Yes please. >I'm trying to think where this would be useful outside your particular >situation. I'm not sure there is a lot of use. > >The official way to do what you are looking to do is to mount it the other >way. On the build machine export the src/obj directories and mount them on >the target machine. Then execute your make install from the target >machine. Otherwise you run into problems like you are running into. >Especially if you're running an install as a non-root user. Except that this is only guaranteed to work if the build machine and target machine are running the same kernel and the build machine's userland is executable on the target machine. (This is because the first part of the buildworld builds tools against the current userland). As an example, if my build machine is a PIII (build with CPUTYPE=p3) then I can't mount src/obj onto an i486 and run installworld - it will try to execute non-i486 instructions. -- Peter Jeremy