On 09/10/10 21:58, Martin McCormick wrote:
After successfully installing bind97 from a package on
to a new server, I do a cvs-sup of the system to get the latest
patches in to the kernel. After discovering that bind97 had been
replaced with bind9.6.1, I looked in /usr/src and there is a
contrib/bind9 directory. What is the safest way to disable that
build without adversly effecting the rest of the update?
The reason for doing these things in this order is that
I would like to get bind running as quickly as possible since it
takes a couple of hours or more to get the world built when we
could be doing DNS.
Since I am not using that version of bind, not getting
it built is no problem. I don't even care if it gets built so
long as it does not end up in /usr/sbin to clobber the new
bind9.7.
If your ports version of named is in /usr/sbin you must have enabled the
REPLACE_BASE option in the port. From man src.conf
WITHOUT_BIND
Setting this variable will prevent any part of BIND from being
built. When set, it also enforces the following options:
[list of sub options snipped]
Add
WITHOUT_BIND= true
into /etc/src.conf, and the next time you rebuild the world the base
system bind will be left out of it.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
