From owner-freebsd-small Tue Jul 25 1:15:12 2000 Delivered-To: freebsd-small@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6D4C637BB7E for ; Tue, 25 Jul 2000 01:15:09 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id CAA24766; Tue, 25 Jul 2000 02:15:06 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id CAA17951; Tue, 25 Jul 2000 02:14:44 -0600 (MDT) Message-Id: <200007250814.CAA17951@harmony.village.org> To: W Gerald Hicks Subject: Re: TinyBSD kit progress report Cc: "Jeffrey S. Sharp" , freebsd-small@FreeBSD.ORG In-reply-to: Your message of "Tue, 25 Jul 2000 01:04:00 PDT." <200007250804.BAA06013@mindspring.com> References: <200007250804.BAA06013@mindspring.com> Date: Tue, 25 Jul 2000 02:14:43 -0600 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For what it is worth, I've had excellent luck with a config file plus a shell script on a freshly built world in creating bootable CF images in the 13M-16M range. It works really well. It isn't 1 floppy, doesn't do compression, etc. A compressed image will likely fit on a 4MB flash part. I did things this way so that the parts would be easily updatable in the field. One drawback of this approach is that I build directly onto the media I'm creating. If there's interest, I can see if I can release this stuff. It has been very useful at Timing Solutions. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message