----- Original Message -----
On Mon, Jul 15, 2013 at 02:46:27PM -0600, Eric Smith wrote:
I don't actually care whether there's a binary journal or not, but far more of us have real usecases for /var/log/messages, so we shouldn't give up that being available by default.
If you use bash or ksh you could just replace /var/log/messages with <(journalctl) in your command line and stuff should just work (when reading). Other shells can probably do the same. It obviously depends on journalctl being able to run.
And you want to do the system wide search and replace all the 3rd party programs, scripts, and documents that mentioned /var/log/messages?
Even if you do, you cannot change the exist tutorial, blog, and forums that refer /var/log/messages.
Image the following scenario: Suppose a Fedora newbie (or linux newbie) encounters a problem, most of the search results state: Check /var/log/messages
He/She will be very frustrated if he/she cannot find it.
I am not saying that journalctl itself is not a good tool, in fact, I've played with it, so far it is working.
However, I strongly recommend that we keep the default syslog until journalctl is well aware and adopted.