Date: Tue, 20 Oct 1998 23:08:38 +0200 (CEST) From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: picoBSD <freebsd-small@FreeBSD.ORG>, Andrzej Bialecki <abial@nask.pl> Subject: More picoBSD ideas Message-ID: <XFMail.981020230838.asmodai@wxs.nl>
next in thread | raw e-mail | index | archive | help
Hi all, I am currently almost completely switched over to FreeBSD, now to get my Eudora mail archives under XFMail. Any ideas if they are interchangeable like Pine <> Eudora? (NOTE: where using statements such as 'picoBSD's lpr program' it is not a suggestion that it isn't FreeBSD's one or that I am trying to degrade FreeBSD, merely being too lazy to keep typing picoBSD/FreeBSD ;) The following is/are merely (a) rough sketch/suggestions in an effort to try to set goals in near and longterm future and to co-ordinate the effort which is picoBSD, which in my eyes has a great future ahead of itself. Hope ye all share this view and appreciate the things I am trying to get clear for us all. Here we go, some food for the mind, as always, comments and additions please: Configuration ------------- Modular set-up with something akin to a bootdisk/bootprom which would allow for a networked/linked installation which obviously allows for very customized set-ups. Sources publicly available through the CVS-tree. Versioning ---------- Same as normal FreeBSD where applicable, e.g.: CURRENT, RELEASE & STABLE. Use of own versioning encouraged to denote current state of the picoBSD kernel and other stuff. (NOTE: I speak of the picoBSD kernel because the FreeBSD kernel is crunched and shrunken in other ways.) Networking ---------- Standard FreeBSD networking support (TCP/IP, Ethernet, (additions please)) trying to get X.25, XNS, etc back into FreeBSD/picoBSD to make one of the best networking OS's even more versatile (additions/requests). Profiles -------- Allow for creation of accounts that have settable level of control/configuration over the device. Allow deletion of initial master account: yes/no? Allow rename of initial master account: yes/no? Management and Control ---------------------- SNMPv1, SNMPv2, RMON, serial line, telnet, ssh, (additions) Routing ------- RIP, RIPv2, OSPF/OSPFv2, BGP, IGMP, CGMP, PIM, QoS, NLSP (if it is usable beyond Novell NetWare scope), (additions) Authentication -------------- RADIUS, TACACS, XTACACS, PAP, CHAP, Kerberos Services -------- Use of picoBSD/FreeBSD lpr/lpd/lpq for networked printing. UI/Frontend ----------- Complete replacement of standard sh and cohorts. Support for autocompletion. Maybe use of W for graphical frontend akin to X-Window System. Use of a small httpd for Web-based configuration. 'picoBSD Team' responsibilities ------------------------------- Andrzej as Team-leader ;) To make sure current code used for the picoBSD packages/modules are screened for any security holes and if they are patched accordingly to the known and unknown bugs with homemade patches or by recognised patches. Decide upon courses in which areas picoBSD can manifest itself. --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist FreeBSD & 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?XFMail.981020230838.asmodai>