Date: Wed, 28 Oct 1998 21:54:53 +0100 (CET) From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: Andrzej Bialecki <abial@nask.pl> Cc: Terry Lambert <terry@whistle.com>, small@FreeBSD.ORG Subject: Re: Unified Configuration Interface Message-ID: <XFMail.981028215453.asmodai@wxs.nl> In-Reply-To: <Pine.BSF.4.02A.9810282100580.20375-100000@korin.warman.org.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On 28-Oct-98 Andrzej Bialecki wrote: > On Wed, 28 Oct 1998, Jeroen Ruigrok/Asmodai wrote: > >> On 28-Oct-98 Andrzej Bialecki wrote: >> 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.. :-) Ahh ok, problem solved ;) >> 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... Yeah, I know, just wanted to express a handy X-reference idea ;) >> 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.. :-) Talk about low pressure *G* Djeez, I missed the Status tree? Hmm *looking again* >> 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. 100% right Andrzej, I forgot about ennumeration ;) >> 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. Exactly, I think we're going to need multiple documents ;) Btw I have holiday next 2 weeks or so, I will work on the dutch docs along with some technical propositional documents like the UCI.html document. > Yes. I didn't name them, but that's what I had in mind. OK, then I know we're on the same wavelength =) > Thanks for the comments! Thanks for starting picoBSD ;) Let's conquer the world now... LOL! --- 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.981028215453.asmodai>