[From nobody Tue Mar 31 13:51:09 2026
Received: (at submit) by bugs.debian.org; 17 Mar 2026 23:48:45 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-20.0 required=4.0 tests=BAYES_00,
 BODY_INCLUDES_PACKAGE,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,
 DKIM_VALID_EF,FOURLA,HAS_PACKAGE,MD5_SHA1_SUM,RCVD_IN_DNSWL_MED,
 SPF_HELO_PASS,SPF_PASS,XMAILER_REPORTBUG autolearn=ham
 autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 36; hammy, 150; neutral, 182; spammy,
 0. spammytokens: hammytokens:0.000-+--forky,
 0.000-+--HTo:N*Debian, 
 0.000-+--H*Ad:N*Bug, 0.000-+--H*Ad:N*Tracking, 0.000-+--HTo:N*System
Return-path: &lt;andrew@bower.uk&gt;
Received: from mx1.mythic-beasts.com ([2a00:1098:0:86:1000:0:2:1]:56477)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from &lt;andrew@bower.uk&gt;) id 1w2e9T-00Evlp-0M
 for submit@bugs.debian.org; Tue, 17 Mar 2026 23:48:45 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bower.uk;
 s=mythic-beasts-k1; h=Date:Subject:To:From;
 bh=dOLBzn5fz9Z7WAQmMiNhVmPiImKhaIMejNFhtbYtBOI=; b=MxxP7vFl+aPVOImRZBSqk6Slf6
 KyOC62sP3cQ0dzojeEcZ5xOiKBHPSasqtWhpm3Tsy/mB+cOB1QdUVIxIuJnnjCxC6xtXPbzTqFC5v
 xM0VKx9sZjkuiGWoplT1lPUdsysSlpZmmjSfwKji6GnsvstJfrszjb0dz/06Djt6pmcWKnFjRNxLm
 ydLa8EjVCqZIcMf7uc61uwP4xExKVaMSe6PHCQcMoA877R+Ubpj7KueXI+NQFKG/prHPHZKhvJGeF
 0rhS9cZbglMBC3Odl/m/bcc4zC6k98SKchNiZOECH5G/BVIUhkO5gVJ2U+x9/R9GA52GgAPMPqFYt
 5nIUo7Tw==;
Received: by mailhub-cam-d.mythic-beasts.com with esmtpsa (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96)
 (envelope-from &lt;andrew@bower.uk&gt;) id 1w2e9M-006q5B-0N;
 Tue, 17 Mar 2026 23:48:36 +0000
Received: from andy by shenstone.ab8.net with local (Exim 4.99.1)
 (envelope-from &lt;andrew@bower.uk&gt;) id 1w2e9A-000000005LO-2eA9;
 Tue, 17 Mar 2026 23:48:24 +0000
Content-Type: text/plain; charset=&quot;us-ascii&quot;
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Andrew Bower &lt;andrew@bower.uk&gt;
To: Debian Bug Tracking System &lt;submit@bugs.debian.org&gt;
Subject: sysvinit-core: inittab.d support unreasonably verbose
Message-ID: &lt;177379130462.20418.5555498450530359042.reportbug@shenstone.ab8.net&gt;
X-Mailer: reportbug 13.2.0
Date: Tue, 17 Mar 2026 23:48:24 +0000
X-BlackCat-Spam-Score: 0
Delivered-To: submit@bugs.debian.org

Package: sysvinit-core
Version: 3.15-6
Severity: minor
Tags: patch

Dear Maintainer,

When booting with sysvinit, the following message is invariably displayed:

  INIT: No inittab.d directory found

This is a little excessive for a default installation as the visual footprint
from init should be minimal. It does not seem to be valid as an error or a
warning.

This can be worked around by adding a directory in debian.sysvinit-core.dirs.
However, this then leads us to a documentation issue: you have to read the
source code to realise that only files ending &quot;.tab&quot; will be read. Therefore I
suggest the patch below [4] would be a better resolution in the debian package,
including a README to explain this point.

But we are not out of the woods. The change [1] that introduced this feature
did not document it. So I suggest that the upstream documents the directory and
its constraints in the man pages.

Then if you do use the feature, you get excessively verbose output due to [2]:

  printf(&quot;Got line: %s\n&quot;, buf); 

I think upstream should remove that.

This directory has some potential to reduce the fragility of maintscripts when
packages include inittab drop-ins, such as runit-run [3].

Do you think any of my suggestions is worth actioning?

Andrew


[1] https://codeberg.org/thejessesmith/sysvinit/commit/d4cc79bcb907b39722f1431d4881bcfcf8740c49

[2] https://codeberg.org/thejessesmith/sysvinit/commit/a24e0232e5298a0cdde102d72ccb255f57ab4e09

[3] https://sources.debian.org/src/runit/2.3.0-1/debian/runit-run.postinst#L30-L41

[4]

diff --git a/debian/inittab.d/README b/debian/inittab.d/README
new file mode 100644
index 00000000..5230440b
--- /dev/null
+++ b/debian/inittab.d/README
@@ -0,0 +1 @@
+This directory accepts drop-in inittab(5) fragments with names ending in &quot;.tab&quot;
diff --git a/debian/sysvinit-core.install b/debian/sysvinit-core.install
index 1d973126..884622c7 100644
--- a/debian/sysvinit-core.install
+++ b/debian/sysvinit-core.install
@@ -3,3 +3,4 @@ sbin/init usr/sbin
 sbin/runlevel usr/sbin
 sbin/shutdown usr/sbin
 usr/include/initreq.h
+debian/inittab.d etc


-- System Information:
Debian Release: forky/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.19.6+deb14-amd64 (SMP w/24 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages sysvinit-core depends on:
ii  initscripts     3.15-6
ii  libc6           2.42-13
ii  libselinux1     3.9-2
ii  login           1:4.16.0-2+really2.41.3-4
ii  mount           2.41.3-4
ii  sysv-rc         3.15-6
ii  sysvinit-utils  3.15-6

Versions of packages sysvinit-core recommends:
ii  orphan-sysvinit-scripts  0.23

Versions of packages sysvinit-core suggests:
ii  bootlogd  3.15-6

-- no debconf information
]