Andrew Bower <andrew@???> writes:
> On Thu, Jul 17, 2025 at 01:02:44AM -0400, Steve Litt wrote:
>> Rainer Weikusat via Dng said on Wed, 16 Jul 2025 12:05:15 +0100
>> >Steve Litt <slitt@???> writes:
>> >> Rainer Weikusat via Dng said on Tue, 08 Jul 2025 16:30:16 +0100
>> >>
>> >>>init.d scripts are config file and as such, supposed to be under user
>> >>>control. This includes that a user may remove them.
>> >>
>> >> Or put exit 0 at the very top.
>> >
>> >I used to do that in the past but some woman working for the Mainz
>> >university computing center convince me of the other method. Her
>> >arguments where:
>> >
>> > - this render starting the serice manually via init.d script
>> > impossible
>> >
>> > - such changes are easily forgotten and possibly, cause a lot
>> > of
>> > headscratching because of this while the renamed script is
>> > visible in the filesystem without having to look at its
>> > content
>
> All problems which are solved by using update-rc.d as Debian intends,
> even though the end user does "own" the conffiles.
update-rc.d is a Debian legacy (due to the switch to systemd) tool which
was/ is meant to be used by maintainer scripts to isolate them from the
details of boot configuration of any particular system for manageing a
boot configuration (same as invoke-rc.d, by the way).