[systemd-devel] [PATCH] use systemd.debug on the kernel command line, not "debug"

[Tom Gundersen]

On Thu, Apr 3, 2014 at 11:08 AM, Tom Gundersen <teg at jklm.no> wrote:
> Is the rationale for this, simply a matter of preference, i.e., is the
> claim simply that we believe most users would benefit more from the
> 'kernel only' compared to 'all low-level stuff' behavior? If that's
> the case, I don't have an opinion on the patch, so I'll leave it to
> those who do :)

Ok, I may care a bit, so I'll add my two cents:

I suppose the general use-case here (i.e., not seen from the point of
view of either a kernel or a systemd developer, but trying to imagine
an end-user), is when 'boot is broken'. In that case, it makes a lot
of sense to me to have a simple switch to give all the relevant debug
info about the boot process. There are basically two things that may
be broken: the kernel or systemd (or the initrd if that's !=systemd),
and the end-user probably doesn't care much for the distinction. I'd
therefore think it makes the most sense for "debug" to trigger
debugging of all these things. I'm sure there are ways to see this to
justify the opposite view though...

Cheers,

Tom