Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1270459
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#944779: initramfs-tools-core: debug setting does not turn on tracing for scripts called by init |
| Date | 2025-11-17 00:30 +0100 |
| Message-ID | <LRUlX-dvbI-17@gated-at.bofh.it> (permalink) |
| References | <z2F9n-2EK-7@gated-at.bofh.it> <z2F9n-2EK-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[Multipart message — attachments visible in raw view] - view raw
Control: tag -1 wontfix
On Fri, 15 Nov 2019 02:21:14 -0600 Glenn Washburn
<development@efficientek.com> wrote:
> Package: initramfs-tools-core
> Version: 0.130ubuntu3.9
> Severity: normal
> Tags: newcomer
>
> Dear Maintainer,
>
> When adding "debug" to the kernel commandline debug output is turned on and is
> very useful for debugging. However, none of the scripts (eg. local-premount/resume)
> recognize the debug variable to turn on tracing as in init. I simply added the
> line "[ -n "${debug}" ] && set -x" as the first line in local-premount/resume
> and now I get debug logging when the debug kernel parameter is added. This line
> should be added to all scripts, or at least the scripts run by "run_parts".
I think this would be a surprising interpretation of the "debug" kernel
parameter, and it could leak sensitive information to the screen. So I
won't be making this change.
Ben.
--
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein
Back to linux.debian.bugs.dist | Previous | Next | Find similar | Unroll thread
Bug#944779: initramfs-tools-core: debug setting does not turn on tracing for scripts called by init Ben Hutchings <ben@decadent.org.uk> - 2025-11-17 00:30 +0100
csiph-web