<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - systemd-205: output from starting services messing up tty1 console"
href="https://bugs.freedesktop.org/show_bug.cgi?id=67114#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - systemd-205: output from starting services messing up tty1 console"
href="https://bugs.freedesktop.org/show_bug.cgi?id=67114">bug 67114</a>
from <span class="vcard"><a class="email" href="mailto:kay@vrfy.org" title="Kay Sievers <kay@vrfy.org>"> <span class="fn">Kay Sievers</span></a>
</span></b>
<pre>The kernel's use of the console is entirely unrelated to what it stored
in the kernel log buffer (the stuff you see with dmesg) or what is imported
into the journal (the kernel stuff journalctl shows).
The messages will always end up in the kernel buffer and the journal, even
when the output is suppressed from the console. There is no re-direct, or
anything needed, systemd does not need to read the console, it's all in the
kernel log buffer anyway.
Note: The way the kernel puts stuff to the console and the default level of
showing almost everything comes from a time where it was exciting that the
kernel booted at all on a box, and Linux was used by people who ran their
self-compiled kernels and were happy that they could watch it doing its job. :)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>