From owner-freebsd-small Wed Oct 7 07:42:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01612 for freebsd-small-outgoing; Wed, 7 Oct 1998 07:42:50 -0700 (PDT) (envelope-from owner-freebsd-small@FreeBSD.ORG) Received: from samizdat.uucom.com (samizdat.uucom.com [198.202.217.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01595 for ; Wed, 7 Oct 1998 07:42:48 -0700 (PDT) (envelope-from cshenton@uucom.com) Received: (from cshenton@localhost) by samizdat.uucom.com (8.9.0/8.9.0) id KAA26198; Wed, 7 Oct 1998 10:42:40 -0400 To: Jeroen Ruigrok/Asmodai Cc: FreeBSD Small , Andrzej Bialecki Subject: Re: picoBSD Goals References: From: Chris Shenton Date: 07 Oct 1998 10:42:40 -0400 In-Reply-To: Jeroen Ruigrok/Asmodai's message of Tue, 06 Oct 1998 23:56:52 +0200 Message-ID: <86af381li7.fsf@samizdat.uucom.com> Lines: 42 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm looking at PicoBSD as an outsider rather than a coder -- looks like it could be very useful/interesting/fun. Just some views on what I'd like in a tiny net-centric OS. Jeroen Ruigrok/Asmodai writes: > 3) Addition of wide accepted routing protocols at first, maybe expanded > with lesser used protocols in traditional *NIX environments, IPX/SPX, XNS, > X.25 and what else spring to mind. > 4) Security is a prerequisite for configuration safeguarding. > 6) Webbased interface for configuration. > > 9) Decide on configuration file formats, filenames and directories. > > 10) Getting rid of *sh's and implement own UI/shell for configuration. I'd want routing/bridging first, with PPP dial; multipoint PPP a la "mpd" would be a win. Then I'd want firewall features, at least router-style ACL capability, and NAT would be neat. I'd be happy if it had sshd instead of telnet/rsh/ftp. I don't need a web interface, unless it consumes LESS critical resources (disk, mem) than a text file or curses GUI. I would think a web i/f would be more difficult to secure, unless you're doing SSL and that seems large. I personally don't need IPX, X.25, Appletalk, UUCP, etc. Is the intention that I could build a PicoBSD image and just choose what functionality I want in a kernel config file? Like: enable router, bridge, ssh, ipfw, snmp disable ipx, atalk, wwwizard Would be nice to chop-and-change what everyone wants their box to do, based on their boot device (e.g., if I only have a floppy) and memory available (4MB isn't gonna do SSL :-) Cool stuff, thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message