List 'bind-users' closed to public posts
Mike Diehn
mdiehn at mindspring.com
Tue Jan 30 01:34:27 UTC 2001
I just upgraded all my Solaris 7 DNS servers from 8.2.2p7 to
9.1.0. Corporate policy requires me to compile from source on a
development system, make a Solaris package of the result and then
install that package on the production DNS servers. Can't have
compilation systems in production, etc. Good policy, I think.
Anyway, I needed to "fake" an installation into a package base
directory in order to facilitate my making the solaris package.
So a regular "make install" wouldn't work. Neither would
altering --prefix in the "./configure."
Got a hint from the list to look at DESTDIR.
My first few tries to use it didn't work. I tried it as an
environmental variable in the shell while doing configure, make,
etc.. I tried defining it in the top level Makefile. Then,
after a "make distclean," in the top level Makefile.in.
No luck. "make install" kept putting the files in the regular
places. A bit confusing. Many variations of the above, many
failures.
After some frustration, I found that while DESTDIR appears in the
top level Makefile.in, it gets promptly redefined when the
@BIND9_MAKE_RULES@ causes make/rules.in to be sucked up during
the "./configure".
Finally figured out that I had to add the value for DESTDIR to
make/rules.in before running ./configure.
Worked like a champ.
Here are some other gotcha's I found for installing this release
on *very* stock Solaris 7:
- your old pal "ndc" has been replaced with "rndc." The
control pipe that ndc used to use doesn't have a place in the
new world, it seems. the doc/misc/migration file mentions
this but doesn't mention that ....
- named.conf needs to have a new statement in the 'controls
section' and needs to have a 'keys' clause in order to have
9.1.0 work with rndc something like 8.2.* works with ndc.
- rndc can't start your named for you now.
These two make perfect sense once you understand the
difference between "ndc" and "rndc", but unless you think
about it before-hand, you'll spend quite a bit of time trying
to figure out why things don't quite work anymore.
the 'Administrator Reference Manual' sheds some light on all
this. Check it out.
- BIND 9.1.0 seems to assume you'll have a /var/run directory
for named's pid file, even in Solaris, which doesn't
traditionally have one.
You can probably get around this somehow, but again, unless
you're aware of it at the outset, it may cramp your style.
- BIND 9.1.0 seems to assume the named.conf will be in /etc.
Yeah, I know, that's traditional, and it's also probably easy
to get around, but a lot of us are used to haveing named look
for named.conf in other places. Just something I mention in
case someone wonders about it like I did.
Cheers,
Mike
More information about the bind-users
mailing list