From owner-freebsd-small Wed Nov 3 11:17:32 1999 Delivered-To: freebsd-small@freebsd.org Received: from cricket.diploma.ru (cricket.diploma.ru [193.232.112.129]) by hub.freebsd.org (Postfix) with ESMTP id 77B9E14CE0 for ; Wed, 3 Nov 1999 11:17:13 -0800 (PST) (envelope-from sh@diploma.ru) Received: from sh (localhost [127.0.0.1]) by cricket.diploma.ru (8.9.1/8.9.1) with SMTP id VAA14777 for ; Wed, 3 Nov 1999 21:58:55 +0300 (MSK) Message-ID: <001a01bf2630$4b88b780$0185d2c3@sh.uniinc.com> From: "Sergey Hlupnov" To: Subject: Re: hello list -- picoBSD anyone? Date: Wed, 3 Nov 1999 22:18:53 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What you mean under picoBSD ? Basically it is just a bunch of scripts to automate assemling of crunched binaries, custom kernel and preparing 1-2 floppy images. As soon as we get new FreeBSD, it's just matter of time to create `light' floppy-based custom system. The only way we can customize it - bios or raw boot, set of software, set of drivers and configs, service scripts. _Everything_ you need is some practice with `crunchgen' and understanding startup procedure (that may be well learned trying to create own picoBSD :-) And of course quick look at picoBSD scripts (kvm stuff, creating MFS image ect...) After that you choose set of binaries you'll need and have fun fitting it on a single 1.44 or 2x1.44. I had some time with it and made few varients - 2x1.44 with perl, httpd, lynx, LAN, tcpdump, nmap, satan ; 1x1.44 with simplest remote access (async, pppd) server ; 1x1.44 with sendmail/bind. Email me if you want try it. It is still not enough tested :-) Best regards, Sergey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message