<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 10/09/2012 02:12 PM, Lennart
Poettering wrote:<br>
</div>
<blockquote cite="mid:20121009141254.GI19792@tango.0pointer.de"
type="cite">
<pre wrap="">On Tue, 09.10.12 09:56, Simo Sorce (<a class="moz-txt-link-abbreviated" href="mailto:simo@redhat.com">simo@redhat.com</a>) wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Tue, 2012-10-09 at 15:23 +0200, Lennart Poettering wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Tue, 09.10.12 07:10, "Jóhann B. Guðmundsson" (<a class="moz-txt-link-abbreviated" href="mailto:johannbg@gmail.com">johannbg@gmail.com</a>) wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 10/09/2012 04:34 AM, Bill Nottingham wrote:
</pre>
<blockquote type="cite">
<pre wrap="">rsyslog.service
</pre>
</blockquote>
<pre wrap="">
Remind me again of the reason why we are still shipping rsyslog by
default now that we have the journal?
</pre>
</blockquote>
<pre wrap="">
For F19 I plan to submit a feature asking for not installing syslog by
default anymore. I wonder how far I'll get with this before this is
shut down by the conservatives... ;-)
</pre>
</blockquote>
<pre wrap="">
Does systemd journal populate /var/log/messages ?
</pre>
</blockquote>
<pre wrap="">
No. It doesnt.
</pre>
<blockquote type="cite">
<pre wrap="">I already found myself stranded in F18 a couple of times.
Stuff changed and there is no way to discover how to fix things.
</pre>
</blockquote>
<pre wrap="">
Well, making changes means, well, making changes. Sure it is a bit of a
learning involved if we make changes, but it should always be our goal
to make the learning easy rather than just sticking to the old ways,
because we are afraid of making these changes. More specifically a good
approach here could be to include an almost empty /var/log/messages that
just tells you to invoke "journalctl" instead. Alternatively we could
just add a /var/log/README with the same info.
(Actually, it has been on my TODO list for a while to add
/etc/rc.d/init.d/README with similar info, I just never came around to
actually do it.)
</pre>
</blockquote>
<br>
Simon has a point and simply having well documented man pages is not
enough and I myself have not been doing my due diligence wikifying
stuff <br>
<br>
Given <br>
<br>
"<code>CHANGES WITH 194: * If /etc/vconsole.conf is non-existent or
empty we will no longer load any console font or key map at boot
by default. Instead the kernel defaults will be left intact. This
is definitely the right thing to do, as no configuration should
mean no configuration, and hard-coding font names that are
different on all archs is probably a bad idea. Also, the kernel
default key map and font should be good enough for most cases
anyway, and mostly identical to the userspace fonts/key maps we
previously overloaded them with. If distributions want to continue
to default to a non-kernel font or key map they should ship a
default /etc/vconsole.conf with the appropriate contents."<br>
<br>
<br>
</code>You probably want to do the same for /etc/sysconfig/i18n
since it's now considered legacy and administrators and users in
general should use <br>
( using my use-case as an example ) <br>
"vconsole.keymap=is-latin1 vconsole.font=latarcyrheb-sun16" on the
kernel command line<br>
<br>
Instead of the old SYSFONT and FONT which probably are being
ignored/deprecated now.<br>
<br>
or make the necessary changes to /etc/vconsole.conf as in <br>
<br>
KEYMAP=is-latin1
<br>
FONT=latarcyrheb-sun16<br>
<br>
For those interested in details see [1]<br>
<br>
JBG<br>
<br>
*cough* in perfect pony world we would be updating the
installer,firstboot and bunch of other stuff that needs to be
updated and tested at the same time *cough*<br>
<br>
<pre class="bz_comment_text" id="comment_text_0">1.<a href="http://www.freedesktop.org/software/systemd/man/vconsole.conf.html">http://www.freedesktop.org/software/systemd/man/vconsole.conf.html</a></pre>
</body>
</html>