Bug#761880: [Pkg-sysvinit-devel] Bug#761880: sysv-rc: support init scripts in /lib/init.d (or similar)

Ansgar Burchardt ansgar at debian.org
Thu Dec 20 08:15:10 GMT 2018

Control: reopen -1

Dmitry Bogatov <KAction at debian.org> writes:

> control: tags -1 wontfix
> [2014-09-16 18:00] Ansgar Burchardt <ansgar at debian.org>
>> The symlinks in /etc/rc?.d/* and /etc/default/* are configuration files,
>> but init script themselves are not (and if admins are supposed to modify
>> them, I would call them buggy).
> Your proposal contradicts Debian Policy (9.3.2):

No, all scripts in /etc/init.d would still be treated as configuration
files.  Just packages could choose to *not* do that (as is the sane
way) by shipping init scripts in a different location.

Policy also seems to lag a decade behind reality:

>  The /etc/init.d scripts must be treated as configuration files, either
>  (if they are present in the package, that is, in the .deb file) by
>  marking them as conffiles, or, (if they do not exist in the .deb) by
>  managing them correctly in the maintainer scripts (see Configuration
>  files). This is important since we want to give the local system
>  administrator the chance to adapt the scripts to the local system,
>  e.g., to disable a service without de-installing the package, or to

It's possible to disable services without editing /etc/init.d/*.

>  specify some special command line options when starting a service,

It's possible to do that without editing /etc/init.d/*. (/etc/default/*)

Allowing packages to not have init scripts as configuration files would
help dealing with outdated init scripts (from removed, but not purged
packages) which cause problems (for example when they lack LSB headers,
have outdated dependencies which cause cirular dependencies, ...).


More information about the Debian-init-diversity mailing list