From owner-freebsd-small Mon Jul 24 22:21:21 2000 Delivered-To: freebsd-small@freebsd.org Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by hub.freebsd.org (Postfix) with ESMTP id DDEC937B693 for ; Mon, 24 Jul 2000 22:21:14 -0700 (PDT) (envelope-from jhix@mindspring.com) Received: from jhix.mindspring.com (user-33qtgov.dialup.mindspring.com [199.174.195.31]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id BAA02806; Tue, 25 Jul 2000 01:21:10 -0400 (EDT) Received: from jhix (jhix@localhost [127.0.0.1]) by jhix.mindspring.com (8.9.3/8.9.2) with ESMTP id WAA05741; Mon, 24 Jul 2000 22:23:37 -0700 (PDT) (envelope-from jhix@jhix.mindspring.com) Message-Id: <200007250523.WAA05741@mindspring.com> To: "Jeffrey S. Sharp" Cc: freebsd-small@FreeBSD.ORG, jhix@jhix.mindspring.com Subject: Re: TinyBSD kit progress report In-Reply-To: Your message of "Mon, 24 Jul 2000 23:12:27 CDT." Date: Mon, 24 Jul 2000 22:23:37 -0700 From: W Gerald Hicks Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've been wondering a bit, after someone brought it up a while back: what > are the chances of the TinyBSD kit making it into the FreeBSD source tree > once it's good enough? It seems to me that it would be a lot more interesting to have the ports/build frameworks set up to accomodate building "these things" out of the src/ tree. In other words, I believe that picobsd needs to come out of src/release and am not in favor of repeating its history. This is not a strike against these variants however; I sincerely believe that they would be more actively maintained as "ports" and also permit wider participation than the current situation does. I prototyped an "outside the tree" variant once and even got it to boot but ran into other problems related to the severe breakage that has been present with PicoBSD for a long time now. ports/itsybsd anyone? :-) Cheers, Jerry Hicks gehicks@cisco.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message