I think it would be fair to be able to configure s6-linux-init so that
it does not rely on specific details about what hardware is available.
Then I have some good news for you: s6-linux-init already does not
rely on specific details about what hardware is available.
Because if it did,
"Laurent Bercot" writes:
>>While that might make sense when the system is expected to have a
>>/dev/tty0 device, it is kind of messy to see that on systems that is not
>>supposed to have /dev/tty0.
>
> Kernels and various parts of init systems print warning messages all
> the time for similar
I checked the shadow utils site. It's provide a lastlog CLI. while it's a lack
of lastlogd similar to utmpd/wtmpd.
The lastlog file isn't managed by utmp, but by the login program, with
or without assistance from PAM. It's an entirely different operation,
and I don't understand why you'd want
Hi
Currently, there is an unconditional attempt to open /dev/tty0 in
src/init/s6-linux-init.c:kbspecials(), and when running on systems
without CONFIG_VT_CONSOLE enabled, that causes a warning message to be
printed out.
s6-linux-init: warning: unable to open /dev/tty0 (kbrequest will not be
While that might make sense when the system is expected to have a
/dev/tty0 device, it is kind of messy to see that on systems that is not
supposed to have /dev/tty0.
Kernels and various parts of init systems print warning messages all
the time for similar reasons (some operation failed
