[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: systemd, getty and brltty

Samuel Thibault <sthibault@debian.org> writes:

> The current version of brltty in Jessie suffers from an issue with
> systemd: systemd does not dare running getty on virtual consoles 2-6
> because brltty is reading them. This is worked around in the latest
> brltty 5.3 release, but we still have the issue in Jessie and brltty 5.3
> is not to be uploaded there.

I have seen this issue in the wild, however, I at least was easily
able to work around it by temporarily switching back to tt1 and back to
the target tty again.  This apparently gave systemd enough of time to
initialize the getty in the meantime.

> One work around could be to make the brltty package run this at
> postinst:
> ln -s /lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty2.service
> ln -s /lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty3.service
> ln -s /lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty4.service
> ln -s /lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty5.service
> ln -s /lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty6.service

> to force the start of getty even when brltty is reading the virtual
> console.  I'm not sure the release team would accept this as a stable
> update, what do people think?

I think this looks like quite a crud hack.


Reply to: