Date: Tue, 06 Oct 1998 23:56:52 +0200 From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: FreeBSD Small <freebsd-small@FreeBSD.ORG> Cc: Andrzej Bialecki <abial@nask.pl> Subject: picoBSD Goals Message-ID: <Version.32.19981006233741.010123a0@pop.wxs.nl>
next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
mayhaps unneeded and redundant, if so, just say so, but I think we need
some more light in the darkness if we are going to make it all work alright.
As far as I can see it the goals below are either my understanding of
people's requests or my ideas of what might have a future for picoBSD...
Please feel free to comment on it, enhance it, even delete it or add to it ;)
Clear goals and ideas for picoBSD:
1) Small OS with emphasis on networking and all related to networking such
as routing, bridging & dial solutions, but not limited to those afore
mentioned topics.
2) Use of the FreeBSD STABLE, RELEASE and CURRENT/BETA kernels for picoBSD
basis.
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.
5) Hierarchical grouping structure of command set that allows for clear
and useful configuration. Starting from toplevel generic classifications
down to very specific configurations. Also, command set versioning
independant from kernel versioning.
E.g.: --- Dialing
|
--- User
|
--- Networking
| |
| --- IP
| |
| --- IPX
|
--- Miscellaneous
(Note, above is a very rough idea of how it COULD be, this is going to be
one of the better discussions on the list which I foresee in near future ;)
6) Webbased interface for configuration. In my opinion a nice addition to
the whole, except in my eyes not that high a priority at this moment, but
if/when we are going to start work on the command set we need to check the
usefulness on the webinterface too, although that might work totally
independant of the command set.
7) Deletion of many subdirectories and commands and a restructuring of the
remaining directories in order to create some order for the picoBSD kernel.
8) Make online configuration easy to retrieve info from, not like IOS'
list of data, but instead grouped and formatted.
9) Decide on configuration file formats, filenames and directories.
10) Getting rid of *sh's and implement own UI/shell for configuration.
Please respond, add, etc...
flames: /dev/null ;)
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 ||==\
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.0 for non-commercial use <http://www.pgp.com>;
iQA/AwUBNhqEFYY752GnxADpEQKxpACcDN4FezNhoh7HpM7i9MG/7vuWYd8AoOdl
wagmhbZl3f5WIo+q4Q5fAaBP
=GWIc
-----END PGP SIGNATURE-----
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?Version.32.19981006233741.010123a0>