From owner-freebsd-small Mon Oct 16 14:38:31 2000 Delivered-To: freebsd-small@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id B1E4D37B502 for ; Mon, 16 Oct 2000 14:38:23 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id RAA87407; Mon, 16 Oct 2000 17:38:46 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Mon, 16 Oct 2000 17:38:46 -0400 (EDT) From: "Brandon D. Valentine" To: Roman Shterenzon Cc: freebsd-small@freebsd.org Subject: picobsd build In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Oct 2000, Roman Shterenzon wrote: >The PicoBSD is broken a bit. >Look for my patches that I sent to small if you can't build it or use it. Can someone tell me what all is involved in getting PicoBSD builds working under RELENG_4 and point me to any uncommitted patches I might need? I'd like to get it working. Actually I don't even necessarily need PicoBSD working. Is there a way to build tinyware without PicoBSD mechanisms? I'd like to populate a filesystem image with bootblocks, a kernel, and the tinyware apps + a few others compiled from ports. I'd appreciate any pointers. -- Brandon D. Valentine "Few things are harder to put up with than the annoyance of a good example." -- Mark Twain, Pudd'nhead Wilson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message