kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update the pkg-message to be even less version-specific, and tell the user

Browse source 
that /etc/rc.d/named will handle everything for them.
This commit is contained in:
Doug Barton 2008-06-02 04:18:45 +00:00
parent 6e6ab4495a
commit 9f92d93730
Notes: svn2git 2021-03-31 03:12:20 +00:00 
svn path=/head/; revision=214165
3 changed files with 24 additions and 27 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
dns/bind94/pkg-message
View file

@ -5,15 +5,14 @@
* / ___ \| | | | | |___| |\ | | | | | |_| | |\ | *
* /_/ \_\_| |_| |_____|_| \_| |_| |___\___/|_| \_| *
* *
* BIND 9 requires a good source of randomness to operate. *
* It also requires configuration of rndc, including a *
* "secret" key. If you are running BIND 9 in a chroot *
* environment, make sure that there is a /dev/random device *
* in the chroot. *
* If you are running BIND 9 in a chroot environment, make *
* sure that there is a /dev/random device in the chroot. *
* *
* The easiest, and most secure way to configure rndc is *
* to run 'rndc-confgen -a' which will generate the proper *
* conf file, with a new random key, and appropriate file *
* permissions. *
* BIND 9 also requires configuration of rndc, including a *
* "secret" key. The easiest, and most secure way to configure *
* rndc is to run 'rndc-confgen -a' to generate the proper conf *
* file, with a new random key, and appropriate file permissions. *
* *
* The /etc/rc.d/named script in the base will do both for you. *
* *
*************************************************************************

17
dns/bind95/pkg-message
View file

@ -5,15 +5,14 @@
* / ___ \| | | | | |___| |\ | | | | | |_| | |\ | *
* /_/ \_\_| |_| |_____|_| \_| |_| |___\___/|_| \_| *
* *
* BIND 9 requires a good source of randomness to operate. *
* It also requires configuration of rndc, including a *
* "secret" key. If you are running BIND 9 in a chroot *
* environment, make sure that there is a /dev/random device *
* in the chroot. *
* If you are running BIND 9 in a chroot environment, make *
* sure that there is a /dev/random device in the chroot. *
* *
* The easiest, and most secure way to configure rndc is *
* to run 'rndc-confgen -a' which will generate the proper *
* conf file, with a new random key, and appropriate file *
* permissions. *
* BIND 9 also requires configuration of rndc, including a *
* "secret" key. The easiest, and most secure way to configure *
* rndc is to run 'rndc-confgen -a' to generate the proper conf *
* file, with a new random key, and appropriate file permissions. *
* *
* The /etc/rc.d/named script in the base will do both for you. *
* *
*************************************************************************

17
dns/bind96/pkg-message
View file

@ -5,15 +5,14 @@
* / ___ \| | | | | |___| |\ | | | | | |_| | |\ | *
* /_/ \_\_| |_| |_____|_| \_| |_| |___\___/|_| \_| *
* *
* BIND 9 requires a good source of randomness to operate. *
* It also requires configuration of rndc, including a *
* "secret" key. If you are running BIND 9 in a chroot *
* environment, make sure that there is a /dev/random device *
* in the chroot. *
* If you are running BIND 9 in a chroot environment, make *
* sure that there is a /dev/random device in the chroot. *
* *
* The easiest, and most secure way to configure rndc is *
* to run 'rndc-confgen -a' which will generate the proper *
* conf file, with a new random key, and appropriate file *
* permissions. *
* BIND 9 also requires configuration of rndc, including a *
* "secret" key. The easiest, and most secure way to configure *
* rndc is to run 'rndc-confgen -a' to generate the proper conf *
* file, with a new random key, and appropriate file permissions. *
* *
* The /etc/rc.d/named script in the base will do both for you. *
* *
*************************************************************************