Date: Wed, 23 Sep 1998 13:22:25 -0700 (PDT) From: David Wolfskill <dhw@whistle.com> To: billf@chc-chimes.com Cc: freebsd-net@FreeBSD.ORG Subject: Re: How to enable SNMP on a FreeBSD router ? Message-ID: <199809232022.NAA06963@pau-amma.whistle.com> In-Reply-To: <Pine.HPP.3.96.980923100613.23721B-100000@hp9000.chc-chimes.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>Date: Wed, 23 Sep 1998 10:16:13 -0400 (EDT) >From: Bill Fumerola <billf@chc-chimes.com> >I don't know if it's because of lack of knowledge on the ports system or >something else, but whenever I hear(see?) someone recommend software for >FreeBSD it's always from the software's distro site. >PLEASE PLEASE PLEASE RECOMMEND FROM THE PORTS COLLECTION. Although I appreciate the suggestion & the sentiment behind it, in my case, I'll readily admit that it's a lack of familiarity with FreeBSD's "ports" collection -- and a lack of familiarity with customizing software from within the "port". The vast majority of my UNIX experience is in environments other than FreeBSD, and I still have a need to support some non-FreeBSD systems. In such cases, it's useful to be able to have a degree of assurance that I've got the relevant options configured properly. If I'm doing something FreeBSD-specific, the ports are often useful. If I'm not, they're less so. And if I'm tinkering with the most recent snapshot of a development version of something (such as amanda), the ports collection -- as far as I can tell -- isn't relevant. I'm certainly willing to be corrected, but my available time for learning FreeBSD-specific ways of doing things I've been doing since '86 (and that still basically work) is pretty limited. david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809232022.NAA06963>