Date: Wed, 28 Oct 1998 21:16:09 +0100 (CET) From: Andrzej Bialecki <abial@nask.pl> To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> Cc: small@FreeBSD.ORG, Terry Lambert <terry@whistle.com> Subject: Re: Unified Configuration Interface Message-ID: <Pine.BSF.4.02A.9810282100580.20375-100000@korin.warman.org.pl> In-Reply-To: <XFMail.981028203111.asmodai@wxs.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 28 Oct 1998, Jeroen Ruigrok/Asmodai wrote: > On 28-Oct-98 Andrzej Bialecki wrote: > > Hi, > > > > Ok, your remarks convinced me that the document I sent needed a lot of > > clarification. > > > > So, here's the corrected version. How about that? > Some requested changes to the updated lay-out (ye care to version the > HTML-page Andrzej?) : What do you mean? If you mean the $Id$ it will be filled once the file is in CVS, and I'll put it soon, let's say on more round of comments on general layout.. :-) > Numbering of the topmost headers as to ease reference to particular > entries in the commandtree (e.g. let's say network configuration is 2, > 2.2.4.1 would mean the IP address for a physical or virtual > networkinterface) It's easy to change, but the numbers will shift when we add or delete topmost branches until we settle with plausible set... > System configuration > > 4.Resource management > 1.Memory consumption > 2.Task priorities > 1.List / Modify > > I think we would need a 3rd option under Resource management that will tell us > how our different tables are doing. Might also be an option under 1.Memory > Consumption. Because we have had to replace switches and routers at work before > their MAC-table and Routing-table were reaching their limit. Hmmm... The "status" tree is for telling us how well we're doing. My intent here was that this subtree allow to _assign_ some resource limits. This should be fairly big tree (just see how many R/W items are in sysctl tree), but I went out of steam before I filled it in.. :-) > > Network configuration > > 4.Routes > 1.List > 2.Static > 1.Add / Delete / List > 1.(route expression) > 3.Dynamic > 1.IS-IS > 1.Add / Delete / List > 1.(route expression) > 2.NLSP > 1.Add / Delete / List > 1.(route expression) > 3.OSPF > 1.Add / Delete / List > 1.(route expression) > 4. .. > > Else we're going to shoot ourselves in the foot when we need to extend our > dynamic route capabilities. Well, more generally: 3. Dynamic (Enumeration of available protocols) 1.ADd /Delete /List because not always will a given box implement all of them. > 5.Network services > > 5.DHCP > 1.Add / Delete / List > 1.(ip range #) > 2.Reserve IP Address(es) > > 6.SNMP > 1.Add / Delete / List > 1.(community string) Whoa! This is certainly much, much more than this... If we use SNMP, it will be most probably ucd-snmp, which implements SNMPv2, and we'll need to add options for specifying what part of the tree are visible for which clients. > 7.Printing > 1.Local / Remote > 1.Printer > 1.Add > 2.Configuration > 1.Modify / List > 3.Delete 4. Disable / Enable > 2.Printerqueue > 1.View jobs > 2.Delete jobs > > 2.ACL Templates > 1.Add / Delete / Modify / List > 1.Name > 5.Authentication methods > +->TACACS, RADIUS and the likes? Yes. I didn't name them, but that's what I had in mind. Thanks for the comments! Andrzej Bialecki -------------------- ++-------++ ------------------------------------- <abial@nask.pl> ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- 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?Pine.BSF.4.02A.9810282100580.20375-100000>