From owner-freebsd-small@FreeBSD.ORG Mon Aug 21 19:11:11 2006 Return-Path: X-Original-To: freebsd-small@freebsd.org Delivered-To: freebsd-small@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34B2516A535 for ; Mon, 21 Aug 2006 19:11:11 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 231FB43D64 for ; Mon, 21 Aug 2006 19:11:09 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k7LJ8Xma024178; Mon, 21 Aug 2006 13:08:36 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 21 Aug 2006 13:08:39 -0600 (MDT) Message-Id: <20060821.130839.-1975969605.imp@bsdimp.com> To: phocking@no-wire.net From: "M. Warner Losh" In-Reply-To: <44D8BF49.1070008@no-wire.net> References: <200608081032.35725.rmiranda@digitalrelay.ca> <44D8BF49.1070008@no-wire.net> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 21 Aug 2006 13:08:36 -0600 (MDT) Cc: freebsd-small@freebsd.org Subject: Re: Ports and Mondifications X-BeenThere: freebsd-small@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Aug 2006 19:11:11 -0000 In message: <44D8BF49.1070008@no-wire.net> Phill Hocking writes: : You can do it the way phk does : http://lists.freebsd.org/pipermail/freebsd-current/2005-October/056974.html : Basically this is the tough part. Any port that adds a user will fail. : It's easier to just mount the image, cp over the packages, and then : upload it to your running device. You also could just add them to the : /usr/obj/wherever and run the last few steps of nanobsd.sh too. At work, we do all kinds of hand-stands to build an image and get users added to it in the right order... We have a chroot where we build the product. We build ports, which add users to the chroot, then make packages that we installed into a subdir of that. Once we've built and installed all the ports in the chroot, we copy the password files to the destination and then install packages into there. This is somewhat convoluted, but does work well in practice... The one problem that we've started seeing lately is with cross building.. Warner