Re: AW: Debian/Ubuntu: Why was the service renamed from bind9 to named?

Erich Eckner Wed, 15 Apr 2020 00:19:10 -0700

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, 15 Apr 2020, Klaus Darilion wrote:

-----Ursprüngliche Nachricht-----
Von: bind-users <bind-users-boun...@lists.isc.org> Im Auftrag von Reindl
Harald
Gesendet: Mittwoch, 15. April 2020 09:05
An: bind-users@lists.isc.org
Betreff: Re: Debian/Ubuntu: Why was the service renamed from bind9 to
named?



Am 15.04.20 um 08:56 schrieb Reindl Harald:



Am 15.04.20 um 08:51 schrieb Klaus Darilion:

Hello!

What is the rationale of:

bind9 (1:9.13.6-1) experimental; urgency=medium
...
  * Rename the init scripts to named to match the name of the daemon


Since years, Debian and Ubuntu User, and plenty of scripts and

automation software (Puppet ...), know that the service is called "bind9". I
think it is very confusing and will cause lots of headaches once Ubuntu 18.04
or Debian 11 is released.


So I really do not understand this renaming.

The software is "Bind 9". The package is "bind9". The service for long time

was "bind9". The config is in /etc/bind. Only the binary is named. So it would
have made more sense to rename the binary. (actually the binary is not so
important for end users: they install the package and manage the service and
usually do not have to worry about the name of the binary).


It would be great if you undo this change before release of 18.04


you confuse the upstream project with your distribution

bind9 was completly wrong in the debian world as well as apache2 for
httpd, on sane distributions it's "httpt" and "named" all the years
beause it's nonsense to throw vesions in service names


BTW in case Debian/Ubuntu when they do RTFM it wouldn't be an issue at all

[root@srv-rhsoft:~]$ systemctl status sddm
● sddm.service - Simple Desktop Display Manager
   Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor
preset: enabled)
  Drop-In: /etc/systemd/system/display-manager.service.d

[root@srv-rhsoft:~]$ systemctl status display-manager.service
● sddm.service - Simple Desktop Display Manager
   Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor
preset: enabled)
  Drop-In: /etc/systemd/system/display-manager.service.d
           └─security.conf, start-before.conf

[root@srv-rhsoft:~]$ cat /usr/lib/systemd/system/sddm.service
[Unit]
Description=Simple Desktop Display Manager
Conflicts=getty@tty1.service
After=getty@tty1.service systemd-logind.service

[Service]
ExecStart=/usr/bin/sddm
Restart=always
EnvironmentFile=-/etc/sysconfig/sddm

[Install]
Alias=display-manager.service


Can you please describe what you want to point out? I can not follow you.

You can set aliases in the service file and call the service whatever youlike (multiple names possible, too). I admit, this has nothing to do withthe package name.

Though: you should complain to debian/ubuntu/..., not upstream (=here)about package name changes.

Regarding version numbers: In the world, where I come from (arch linux),version numbers are only appended for *legacy* packages - e.g. "bind9"would be valid, if there is a "bind" package, that has a higher versionthan 9. Btw.: bind is packaged as "bind" for years on arch linux.


regards,
Erich


Klaus
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Re: AW: Debian/Ubuntu: Why was the service renamed from bind9 to named?

Reply via email to