[systemd-devel] [PATCH] Add support for initial state of NumLock
Kay Sievers
kay at vrfy.org
Fri Apr 12 17:11:08 PDT 2013
On Sat, Apr 13, 2013 at 12:36 AM, Cristian Rodríguez
<crrodriguez at opensuse.org> wrote:
> El 12/04/13 13:53, Stanislav Brabec escribió:
>>
>> Add support for setting of initial state of NumLock. Supported values
>>
>> are "yes", "no" and "bios" (on x86 platforms).
>>
>> It sets NumLock in virtual consoles. If NumLock should be turned on, it
>> also creates empty /run/numlock-on, which can be used e. g. for setting
>> of X session default.
>>
>> This ports a feature that exists for a long time in SUSE to systemd.
>
> Please apply the attached patch on top of this one.
Upstream systemd should not add more features to the utterly broken
kernel console font/keymap/... handling, it should stay as minimal as
possible and not get any fancy things.
What we have today does not even work, it's full of bugs, issues we
can't solve, and full of promises we can't hold today. Kernel VTs are
just a forgotten and not-really-working kernel facility, nobody will
fix it for us, hence we should not make it more complicated as it
already is, but work on leaving it behind.
If things work out as planned, we will switch all the kernel VTs over
to sane and proper font/keymap handling in userspace (kmscon or
whatever it will be called then) and leave the original kernel VTs as
a plain debug console which is no longer in use by default.
If distributions needs and supports such a console features they
better ship it downstream, upstream should not fiddle with even more
weird kernel switches here. We do not consider these things as
features everybody should have.
Kernel VTs not the future, not the direction we are heading; every
feature we add here now, we kind-of need to carry over to the new
world where people are working on, and the fewer things we need to
support the better.
Thanks for understanding,
Kay
More information about the systemd-devel
mailing list