Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 673122 - net-dns/bind: Files and paths naming inconsistency
Summary: net-dns/bind: Files and paths naming inconsistency
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Christian Ruppert (idl0r)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-14 10:15 UTC by Vlad K.
Modified: 2019-10-24 16:33 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vlad K. 2018-12-14 10:15:16 UTC
The Bind server and package is internally inconsistent with regards to naming:

* /etc/init.d/named
* /etc/conf.d/named
* /etc/env/10bind
* /etc/bind/named.conf  (dir is "bind" but file is "named")
* /var/bind/  (the chroot)
* /var/log/named/
* /run/named/

* /usr/share/doc/bind...   but the manpages are "named"

And UID/GID is named.

Considering such a breaking change, if anything is violating POLA (Principle of Least Astonishment) it is this inconsistency. I propose the bind-aid be pulled hard and fast. It will hurt for a short while, but then things will remain consistent, users will adapt.

I propose we settle with "named" because that's where most of these names are, and the upstream is using it too in the default example config:

* /etc/namedb/named.conf
* /var/named/
* /var/log/named/
* /run/named/
* "named" service already is, so is UID and GID, manpages
Comment 1 Mikle Kolyada (RETIRED) archtester Gentoo Infrastructure gentoo-dev Security 2019-10-20 07:58:21 UTC
bind is the server while the "name" is the daemon, that is ok.
Comment 2 Martin 2019-10-23 18:57:30 UTC
Noted for the bind and name(d) (daemon) naming.

To the casual systems admin, there is a very high expectation of consistency... Hence to match what is commonly the case for other entries in /etc/init.d and /etc/conf.d, for named, there is a natural expectation for a matching /etc/named for any further config and setup details... Instead we have /etc/bind which requires 'further understanding' to know where to look...

To follow the Principle Of Least Surprise, can we have a benign

ln -s /etc/bind /etc/named

as a helpful fix and an easy work-around?


(Or at the very least a special note on the first line of /etc/conf.d/named to helpfully explain how named is underneath bind?)


Thanks,
Martin

(He who has wasted deadline time to get out of a bind!)
Comment 3 Vlad K. 2019-10-24 06:54:34 UTC
(In reply to Mikle Kolyada from comment #1)
> bind is the server while the "name" is the daemon, that is ok.

Well, see, that is the whole reason this issue is raised. Pick one. Because, why is "bind" in etc but "named" in var(log)? What's the difference? Are you refering to the server or to the daemon when you're configuring it in /etc/?

What about variable data? Is it bind the server or named the daemon? And why is then, BOTH? var/bind  BUT .... var/log/named

And then, within the configuration itself, you have inconsistency as well. /etc/bind/ BUT.... /etc/conf.d/named  .... why? Why are the two different? Does one configure the server and one the daemon? Which is which?

This is pure nonsense and you know it. If you don't wanna fix it because you're lazy or don't feel like it, fine, just say so and don't pretend you know better.
Comment 4 Martin 2019-10-24 16:33:18 UTC
(In reply to Vlad K. from comment #3)
> (In reply to Mikle Kolyada from comment #1)
> > bind is the server while the "name" is the daemon, that is ok.
> 
> Well, see, that is the whole reason this issue is raised. Pick one. Because,
> why is "bind" in etc but "named" in var(log)? What's the difference? Are you
> refering to the server or to the daemon...

> This is pure nonsense and you know it. If you don't wanna fix it because
> you're lazy or don't feel like it, fine, just say so...

Care enough to fork a new ebuild? And maintain it?

That certainly ain't lazy.

Now, please engage some thought and some scheme to make such changes such that noone else will waste time when whatever changes are made? Do you have a scheme?


More positively: Please make a new ebuild for this with a good and clear name such that people can then choose between your named naming or the existing ebuild. Then maintain it.

Or please add the workaround:

ln -s /etc/bind /etc/named


Please also add the patch to update the config files to note the naming?

Many thanks,

And many thanks to the existing maintainer.


Regards,
Martin