On Thu, 6 Mar 2003, Philip Paeps wrote:
> Is it actually possible for one to build a custom release without the
> ``unnecessary'' BIND bits? I haven't grepped the source, forgive me,
> but what does 'NO_BIND=true' actually do? If I were to make a release
> like that, would that end me up without resolver as well?
It's not as thorough as I think it should be. I plan to get cracking on
this now that I've got my ports more or less whipped into shape
pre-freeze.
> Perhaps a NO_NSLOOKUP flag? ;-)
Yeah, I'll add that along with the PIGS_WILL_FLY flag.
> I just spotted those flags a few days ago. They're very useful.
Good news, thanks.
> Now my fiddling with the BIND port is reduced to making stuff live under
> /var/namedb instead of /etc/namedb as I like having / mounted read-only
> as much as possible.
One way you can do this fairly easily with PORT_REPLACES_BASE is to have
your chroot tree look something like this:
/var/named/<other stuff you need>
/var/named/etc/namedb/named.conf (etc)
Then have /etc/namedb be a symlink to /var/named/etc/namedb, with
'directory "/etc/namedb";' in your named.conf file. That way, both named
and ndc "see" the same picture of the system, in and out of the chroot
tree. I already use this at work, and I plan to add a lot of this config
to the base itself here pretty soon. But you can easily get a head start
on it now using what I described above.
Doug
--
This .signature sanitized for your protection
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
