Date: Tue, 27 Mar 2007 15:24:13 +0300 From: "Reko Turja" <reko.turja@liukuma.net> To: "Don O'Neil" <lists@lizardhill.com>, <freebsd-questions@freebsd.org> Subject: Re: Updating Bind & OpenSSL on 6.1-Stable/Release Message-ID: <031101c7706a$d4763770$0a0aa8c0@rivendell> References: <005d01c76fdd$e67f33a0$0400020a@mickey> <023801c76fe6$0f78e190$0a0aa8c0@rivendell> <008f01c77007$cfca1d80$0400020a@mickey>
next in thread | previous in thread | raw e-mail | index | archive | help
>I did... So I linked it to /etc/named.conf.... Everything works great >now... > > My question is howver, why are the ports setup different than the > original > install? I would think that the port build would be set with the > same > options as the original install that came with the OS... I've seen > this Mainly because FreeBSD is a complete system, not a kernel and mishmash of separate utilities like some other OS'es out there. Basically this means that you should upgrade supplied userland programs by using the usual cvsup the latest sources and buildworld procedure, rather than using the ports for upgrading. The versions of BIND/Sendmail/SSL in the ports are mainly in there for users who need new features or something not available in the versions installed with the operating system base. The separate install lets you bail out if something stops working with the replacements installed from ports and of course helps preventing breaking the interdependencies and stuff in the OS supplied userland. -Reko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?031101c7706a$d4763770$0a0aa8c0>