From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 13 05:58:57 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B281106564A for ; Sun, 13 Feb 2011 05:58:57 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 4EF3E8FC12 for ; Sun, 13 Feb 2011 05:58:57 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p1D5gLc9079964 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 12 Feb 2011 21:42:24 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <4D576F49.5030201@freebsd.org> Date: Sat, 12 Feb 2011 21:42:33 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: perryh@pluto.rain.com References: <201102111909.p1BJ9UAE097045@fire.js.berklix.net> <66758C9D-DCE2-4381-A4B1-956A48423CDD@kientzle.com> <4d5753d7.BT5wqP8CnfTD02s8%perryh@pluto.rain.com> In-Reply-To: <4d5753d7.BT5wqP8CnfTD02s8%perryh@pluto.rain.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: jhs@berklix.com, hackers@freebsd.org Subject: Re: memstick.img is bloated with 7% 2K blocks of nulls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2011 05:58:57 -0000 On 2/12/11 7:45 PM, perryh@pluto.rain.com wrote: > Tim Kientzle wrote: > >> The strategy used by libarchive's recent ISO writer >> is to concatenate the file bodies into a temp file >> (with minimal padding between entries to meet alignment >> requirements) while storing directory information >> in memory. The final output then consists of the >> directory information followed by the concatenated >> file bodies. >> >> I suspect a similar strategy could be used to lay >> out and write a read-only optimized UFS image ... >> I think it's probably feasible but I doubt very >> much of the existing UFS code can be recycled for >> such a project. > There was at one time a capability in mkfs(8) -- which no > longer even exists as a separate entity, having been absorbed > into newfs(8) -- to pre-populate the filesystem with specified > content. Dunno if it was ever in any BSD release -- it's not > mentioned in the 4.2BSD-derived SunOS 4.1.1 manpage -- so > I may be remembering it from Bell Labs 6th edition on the PDP-11. man makefs > The code to collect and write all of an existing filesystem's > directories, followed by all of its files, exists in dump(8). > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >