Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=663900
--- Comment #13 from Miloslav Trmač <mitr(a)redhat.com> 2011-01-07 09:45:55 EST ---
(In reply to comment #12)
There are two separate locales.
* Locale used in the login process. This uses the system locale. I don't
really have an opinion about whether this should be set in systemd or in
*getty.
Actually... To the extent systemd can write status or error messages to the
Linux console, systemd itself should, eventually, also set the system locale
and do the filtering (because, eventually, the messages should support
translation).
I still can't see a clear reason to "logically" place the responsibility
for
filtering the locale should be to systemd or to the various programs that use
the console (i.e. should getty set the locale and filter it, and should gdm set
the locale and not filter it, or should both be handled by systemd?) - but if
the code needs to exist inside systemd anyway, placing the responsibility with
systemd would probably result in the simplest design.
I.e. systemd would be responsible for setting locales for services it starts,
and could be configured to filter it for services that use the Linux console.
None of the system-wide daemons would care about /etc/sysconfig/i18n, parsing
it, or worry about filtering the data.
Ideally it should be possible to share the locale filtering code between
systemd and profile.d/lang.sh (e.g. a script that gets the L* environment
variables on stdin and outputs filtered settings on stdout), but that's
probably just too much bike shedding from me.
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.