Updating Bind & OpenSSL on 6.1-Stable/Release

[Kevin Kinsey]

Don O'Neil wrote:
> 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
> before, and it's annoying as heck when you go to patch/update something and
> it doesn't work because it's installing in a different location and looks
> for config files in different places. 
>

Because they are "ports"??

Kevin Kinsey

> -----Original Message-----
> From: Reko Turja [mailto:reko.turja at liukuma.net] 
> Sent: Monday, March 26, 2007 1:34 PM
> To: Don O'Neil; freebsd-questions at freebsd.org
> Subject: Re: Updating Bind & OpenSSL on 6.1-Stable/Release
> 
>> My bind install that came on the 6.1 installation runs from /usr/bin, 
>> whereas both the package and the source want to run from 
>> /usr/local/bin...
> 
> You should have named.conf in /etc/namedb unless there's something funny
> with the original install. Not sure if you need to run make-localhost script
> in that directory as I do it as a matter of principle each new system
> install anyway. If I update SSL/SSH/BIND I set the
> REPLACE_BASE/OVERWRITE_BASE knob (check the Makefile at ports dir for
> relevant knob name!) so the updated version will overwrite the older at /usr
> tree.
> 
> -Reko 


-- 
The San Diego Freeway.  Official Parking Lot of the 1984 Olympics!