From owner-freebsd-current@FreeBSD.ORG Tue Jan 31 19:18:22 2006 Return-Path: X-Original-To: current@freebsd.org 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 4380E16A420; Tue, 31 Jan 2006 19:18:22 +0000 (GMT) (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 66BE343D6E; Tue, 31 Jan 2006 19:18:21 +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.3/8.13.3) with ESMTP id k0VJFlLq035762; Tue, 31 Jan 2006 12:15:48 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 31 Jan 2006 12:15:59 -0700 (MST) Message-Id: <20060131.121559.127178102.imp@bsdimp.com> To: rizzo@icir.org From: "M. Warner Losh" In-Reply-To: <20060131105224.A57698@xorpc.icir.org> References: <20060131105224.A57698@xorpc.icir.org> X-Mailer: Mew version 3.3 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]); Tue, 31 Jan 2006 12:15:49 -0700 (MST) Cc: current@freebsd.org, small@freebsd.org Subject: Re: [RFC] what do we do with picobsd ? 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: Tue, 31 Jan 2006 19:18:22 -0000 In message: <20060131105224.A57698@xorpc.icir.org> Luigi Rizzo writes: : [i am cc-ing -small because they are interested, but please : keep the discussion on -current] : : as the subject says... : : The picobsd script in the tree at the moment is broken in : several ways. It may work on 4.x, but not on newer releases. : : I have a fixed version (mostly the one i attached yesterday, with : a minor fix to handle the newer boot blocks) that works also : up to -current. Besides, it relies on ports/sysutils/makefs to build : the filesystem image so it can run without superuser privs. : : I know it is not ideal to have a piece of code in the main tree : that depends on an external port. Yet, better than have it broken. : : Now the options are: : : 1. do nothing and leave things broken; : : 2. commit the updated script, fix one or two sample targets, : and remove the others (all of this is in src/release/picobsd) : : 3. remove the entire src/release/picobsd tree and move it to : a port (question - do we want the old content of src/release/picobsd : in ports/foo/picobsd/files ? In any case, we need a place in : some repository to store these things) : : Option #3 is probably the best one, except that the exact 'config' : files are strongly tied to the target source tree you are using, : at least for major releases (libraries differ, application name : change, etc) and so I'd need to modify the script to reach the : templates for RELENG_7, RELENG_6... if they are not already in the : target source tree. Also, this requires a repocopy. : : However given that i don't have a lot of time at the moment, : i would compromise on option #2 for the time being, and move : to option #3 at a later (but unspecified) time. : : comments ? Given how intertwingled picobsd is to the underly OS, I think you are going to have a hard time getting to #3. #2 is fine with me. Warner