On Thu, 3 Apr 2014 00:12:13 +0200 Mateusz Guzik <mgu...@redhat.com> wrote:
> Well, parsing kernel cmdline by systemd is a bad idea, and hiding > "debug" is even worse. What will happen when the next keyword clashes? > And how should I check the kernel is booted with "debug"? No, I think you got it backwards. Hiding "debug" is a bad idea, having systemd abuse the hell out of it is even worse. > > If there is a real need to pass arguments to systemd, how about a > dedicated option (initargs= or whatever, where it has to be last in > cmdline), then systemd would be spawned with these arguments and would > just go over its argv. > No, the correct solution was to have systemd use its own flag. Say "systemd.debug", which I believe from froward reading my emails, Greg has already sent a patch to do so. That solution was even suggested in the BZ and was turned down with the quote I had in my change log. That we don't own the generic terms, even though it's our f*cking command line, not theirs! -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
