<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - Do not parse "debug" command line parameter" href="https://bugs.freedesktop.org/show_bug.cgi?id=76935#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - Do not parse "debug" command line parameter" href="https://bugs.freedesktop.org/show_bug.cgi?id=76935">bug 76935</a> from <a class="email" href="mailto:mgorman@suse.de" title="Mel Gorman <mgorman@suse.de>"> Mel Gorman</a> <pre>(In reply to <a href="show_bug.cgi?id=76935#c4">comment #4</a>) > (In reply to <a href="show_bug.cgi?id=76935#c3">comment #3</a>) > > > The generic term "debug" is read by Base OS tools too. > > > > ... which was wrong to begin with, without a namespace prefix. > > Which we do not agree. Generic terms are generic, not the first user > owns them. > Come on Kai. The kernel is the primary user of its own command line and has a reasonable expectation that it's the default namespace for parameters. In cases where that is not true (such as modules), the parameter get prefixed by the name of the module affected like i915.foo. There may be base utils that parse the command line (they really shouldn't) but even if they do, their reaction should not be to scribble all over the kernel log. systemds default debug behaviour should not be to hijack the kernel log. I can see cases where you want to do that if you need the output from a serial console but that should be explicitly stated with a systemd.log_target.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>