Date: Thu, 6 Mar 2003 02:17:19 +0100 From: Brad Knowles <brad.knowles@skynet.be> To: Philip Paeps <philip@paeps.cx> Cc: "FreeBSD-Current (E-mail)" <freebsd-current@freebsd.org> Subject: Re: Plea for base system trim Message-ID: <a05200f2cba8c51ba7edb@[146.106.12.76]> In-Reply-To: <20030306010724.GE621@juno.home.paeps.cx> References: <2F03DF3DDE57D411AFF4009027B8C36704129AE6@exchange-uk.isltd.insign ia.com> <20030305015947.M18288@znfgre.tberna.bet> <20030305232641.GC621@juno.home.paeps.cx> <20030305163732.Y50404@12-234-22-23.pyvrag.nggov.pbz> <20030306010724.GE621@juno.home.paeps.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
At 2:07 AM +0100 2003/03/06, Philip Paeps wrote:
> Speaking of ndc, I think that's a BIND8-ism.
Indeed, it is. With BIND-9, ndc won't even work -- Unix sockets
aren't supported, and IP sockets are secured with crypto keys.
> Could the port be
> convinced to symlink it to rndc when set to replace the base, or
> would that confuse other things? Currently, I'm just aliasing it
> in my shell, but that seems a bit hackish :-)
That could potentially be done, but keep in mind that there are
some things that ndc can do that rndc can't -- "ndc start" being one
of the big ones.
--
Brad Knowles, <brad.knowles@skynet.be>
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.
GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a05200f2cba8c51ba7edb>