On Thu, Sep 13, 2012 at 9:29 AM, Lennart Poettering <lenn...@poettering.net> wrote: > On Tue, 28.08.12 19:29, Tom Gundersen (t...@jklm.no) wrote: > >> We do this for several reasons: >> >> * it is counter-intuitive that an empty vconsole.conf file is different >> from adding FONT=""; >> * the version of the default font shipped with Arch (the upstream one) >> behaves very badly during early boot[0]; > > Hmm, that sounds like a bug to fix in the font or the console tools?
My guess is that the problem is in the font (as I have only experienced this with that particular font), but I don't know anything about how it is supposed to work so can't say that with any confidence. > Hmm, so I am tempted to make this change for everybody instead of just > Arch. That would be great. > But before I do that, I have one question: the default kernel font, does > that do the usual UTF-8 subset that LatArCyrHeb-16 does? If so, then > there is indeed no point in loading a font from userspace, indeed, > especially given that setfont is so awfully slow... > > By "usual UTF-8 subset" I mean box chars (i want QR codes on the > console! ;-)) and the range that iso8859-15 covers I guess. I don't know. However, if no one beats me to it I'll look into this sometime in the coming week and let you know. -t _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
