From owner-freebsd-small Mon Feb 4 9: 1:44 2002 Delivered-To: freebsd-small@freebsd.org Received: from okc-65-28-129-29.mmcable.com (okc-65-28-129-29.mmcable.com [65.28.129.29]) by hub.freebsd.org (Postfix) with ESMTP id 0F40A37B429 for ; Mon, 4 Feb 2002 09:01:38 -0800 (PST) Received: from localhost (jss@localhost) by okc-65-28-129-29.mmcable.com (8.11.6/8.11.6) with ESMTP id g14Gt7l38985; Mon, 4 Feb 2002 10:55:07 -0600 (CST) (envelope-from jss@subatomix.com) Date: Mon, 4 Feb 2002 10:55:06 -0600 (CST) From: "Jeffrey S. Sharp" To: gerry link Cc: freebsd-small@FreeBSD.ORG Subject: Re: picoBSD: newbies question In-Reply-To: <20020204083700.YDVO27419.mta10.onebox.com@onebox.com> Message-ID: <20020204104809.V38977-100000@kenny.subatomix.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 4 Feb 2002, gerry link wrote: > Basic question I guess I have is, should I actually invest time into > Pico, or simply go with Free/Open? You should simply go with FreeBSD itself. It is almost dirt-simple to make your own tiny distro, mainly because all of the source you need is in once place under a common build system. I'm no UNIX expert, but I learned how to do it in one day by reading the pico scripts. I think that nowadays PicoBSD should be viewed as more of a learning tool than the last word on small FreeBSD. Most of the people using fmall FreeBSD in production today have their own custom system for building it. I had a toolkit I was working on and almost got to public release, but I left the employer who was paying me to do it and have not had time to work on it again. It will be finished...someyear. -- Jeffrey S. Sharp jss@subatomix.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message