From owner-freebsd-arch@FreeBSD.ORG Tue Jun 26 16:17:37 2012 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BEB291065670 for ; Tue, 26 Jun 2012 16:17:37 +0000 (UTC) (envelope-from sjg@juniper.net) Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by mx1.freebsd.org (Postfix) with ESMTP id 953368FC1A for ; Tue, 26 Jun 2012 16:17:36 +0000 (UTC) Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKT+ngngXKwyvOTYmD+1pp+Aq7t9ovZNlG@postini.com; Tue, 26 Jun 2012 09:17:37 PDT Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB03-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 26 Jun 2012 09:16:07 -0700 Received: from chaos.jnpr.net (chaos.jnpr.net [172.24.29.229]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id q5QGG5h45630; Tue, 26 Jun 2012 09:16:05 -0700 (PDT) (envelope-from sjg@juniper.net) Received: from chaos.jnpr.net (localhost [127.0.0.1]) by chaos.jnpr.net (Postfix) with ESMTP id 5082A58081; Tue, 26 Jun 2012 09:16:05 -0700 (PDT) To: Tim Kientzle In-Reply-To: References: <20120626063017.D05DA58081@chaos.jnpr.net> <86wr2uwdgf.fsf@ds4.des.no> Comments: In-reply-to: Tim Kientzle message dated "Tue, 26 Jun 2012 08:18:05 -0700." From: "Simon J. Gerraty" X-Mailer: MH-E 7.82+cvs; nmh 1.3; GNU Emacs 22.3.1 Date: Tue, 26 Jun 2012 09:16:05 -0700 Message-ID: <20120626161605.5082A58081@chaos.jnpr.net> MIME-Version: 1.0 Content-Type: text/plain Cc: =?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?= , freebsd-arch@freebsd.org, sjg@juniper.net Subject: Re: Allow user install X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2012 16:17:37 -0000 On Tue, 26 Jun 2012 08:18:05 -0700, Tim Kientzle writes: >Better idea: have the build write a textual description of the >tar entries. That description can then be fed to tar to build >the actual tarball. Yes, that's what we do - manifest files that tar and other tools use to produce the install images. >The description format that tar already supports is a variant >mtree format borrowed from NetBSD. Each line specifies >the tar entry fields (filename, owner, permissions, etc) and >the filename where the file contents are stored. Yes, we've added that support to makefs - I believe it is already in -current. There's still quite a bit to do.