<div dir="ltr">Hi<br><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Dec 31, 2013 at 4:36 PM, Joe Zeff <span dir="ltr"><<a href="mailto:joe@zeff.us" target="_blank">joe@zeff.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 12/31/2013 01:20 PM, Rahul Sundaram wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Your proposal is irrelevant when we are talking about current reality.<br>
journalctl is not a requirement to read logs. It is just far more easier<br>
than grepping through /var/log/messages for the common use cases.<br>
</blockquote>
<br></div>
Not always. As an example, I'm getting error messages at boot time on my laptop about [sdb] even though there isn't one. Locating them with journalctl would require me to know exactly what field to look for,<br>
</blockquote><div><br></div><div>No. That's just blatantly wrong. journalctl's output is a pixel perfect match of /var/log/messages. <br><br></div><div>Rahul<br></div></div></div></div></div>