From owner-freebsd-current Tue May 28 08:35:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA07470 for current-outgoing; Tue, 28 May 1996 08:35:34 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA07457 for ; Tue, 28 May 1996 08:35:29 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA19970; Tue, 28 May 1996 11:35:23 -0400 Date: Tue, 28 May 1996 11:35:23 -0400 From: Garrett Wollman Message-Id: <9605281535.AA19970@halloran-eldar.lcs.mit.edu> To: "Marc G. Fournier" Cc: current@FreeBSD.org Subject: snmp for FreeBSD... In-Reply-To: References: Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: > What would it take to get the agent and the support programs > included in FreeBSD 2.2, working towards snmp manageablililty? I'm > willing to work at maintaining it and keeping it up to date, but I > think something like this should be "integrated into" the Operating > System, not an extra... At this point, I would be more inclined to leave it as a `port'. While I agree that this is functionality that we will eventually want integrated, I'm a bit concerned that we might be drawn into the SNMPv2 morass and all its attendant nightmares. I would prefer for that issue to become settled, and a good daemon implemnentation found which has well-constructed security mechanisms, before we try to integrate it into the system itself. That said, if there are any specific features which the agent would like to get from the operating system, I'm more than happy to consider them. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant