Date: Wed, 07 Oct 1998 21:53:47 +0200 From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: Chris Shenton <cshenton@uucom.com> Cc: FreeBSD Small <freebsd-small@FreeBSD.ORG>, Andrzej Bialecki <abial@nask.pl> Subject: Re: picoBSD Goals Message-ID: <771898EF14E6.AAD5AD4@smtp01.wxs.nl> In-Reply-To: <86af381li7.fsf@samizdat.uucom.com> References: <Jeroen Ruigrok/Asmodai's message of Tue, 06 Oct 1998 23:56:52 %2B0200> <Version.32.19981006233741.010123a0@pop.wxs.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
At 16:42 07-10-98 , Chris Shenton wrote:
>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.
Indeed, although I have no idea what I started with some of my remarks
since I joined the list a week or two ago ;)
I now see more and more posts, that's good... Hope that makes Andrzej happy ;)
>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.
is mpd a FreeBSD standard or is it a package out there on the web? If so,
have an URL handy ?
>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.
Well, obviously as I am starting to see now thanks to some on this list,
picoBSD is already used in commercial environments where there will be
(l)users administrating the system that don't know jack of command line
configuration or that aren't willing to learn.
>I personally don't need IPX, X.25, Appletalk, UUCP, etc.
So these could make it to the selection menu for custom picoBSD's? I myself
need IPX, as we run a Novell orientated network which uses some NetWare/IP,
but we have to wait for the implementation of NetWare 5 before we can
migrate...
>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
Well that's what I am aiming to with my customising/plug-in/modular setup
idea. Just enable that which ye like and leave out the rest...
>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.
That's what gives us a woody ;)
Jeroen Ruigrok van der Werven / Asmodai <asmodai(at)wxs.nl>
ICQ-UIN: 1564317 .:. Ninth Circle Enterprises
Network/Security Specialist
/==|| FreeBSD and picoBSD, the Power to Serve ||==\
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-small" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?771898EF14E6.AAD5AD4>