hi,
I'd like to suggest that zonec is renamed to nsd-zonec to limit the command line "namespace" that NSD uses.
what do other users think about this?
jakob
+1
Paul
This would occupy namespace even more, as it would claim both zonec and nsd-zonec.
Why is this a problem? It would just mean that 'zonec' is taken. First come first serve. Does it cause confusion with all the other zonec's?
I'd leave it as is.
Roy
Hi Jakob,
My initial reaction to this suggestion:
I'd like to suggest that zonec is renamed to nsd-zonec to limit the command
line "namespace" that NSD uses.
what do other users think about this?
The naming of nsd components is all historic and ad-hoc. To create
a "structured" name space might not be a bad idea, but should at
least allow for a transition period. It might be useful to add
nsd-zonec as an alias with the up coming release (3.2.4) and remove
the zonec sec with a major bump in the release (say 3.3.0) so there
is time to have people adjust. And while we are at it, we should
then do that a similar operation for nsdc towards nsd-control.
jaap
+1
+1
+1
It's not just about the NSD versions. You need to consider all the
distros. Debian maintainer will have to provide aliases for next
stable with warning and remove alias just after next+1 stable is out.
Generally I am against such renaming just "for cleaning up". Does the
"zonec" clash with something else? And please at least don't rename
nsdc to nsd-control.
Ondrej