Re: Bug#811345: setupcon not run
Samuel Thibault, on Sun 24 Jan 2016 15:07:18 +0100, wrote:
> Samuel Thibault, on Sun 24 Jan 2016 14:47:59 +0100, wrote:
> > Marco d'Itri, on Sat 23 Jan 2016 23:03:51 +0100, wrote:
> > > On Jan 23, Samuel Thibault <firstname.lastname@example.org> wrote:
> > > > Should udev or systemd perhaps provide some hook to configure a
> > > > just-created VT?
> > > Maybe a rule like this one?
> > >
> > > ACTION=="add", KERNEL=="tty[1-9]|tty[1-9][0-9]", RUN+="..."
> > That gets triggered a few hundreds of times during boot, but apparently
> > not on VT dealloc/realloc done by systemctl restart email@example.com
> I however tried vcs[0-9]|vcs[1-9][0-9], and it does get called on getty
> service restart. I'm having a look at calling setupcon there.
ACTION=="add", SUBSYSTEM=="vc", KERNEL=="vcs[1-9]|vcs[1-9][0-9]", RUN+="/bin/setupcon"
I do get the proper size on getty restart (and only a few calls, not
hundreds of them like with KERNEL==tty*).
I don't know how to pass parameters in the RUN+= statement, but I guess
setupcon can be made to take a parameter to tell the tty or vcs name to
be configured (instead of all of them).