Re: vt220 default for serial console still relevant?

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

 



On Di, 14.07.20 22:15, Daan De Meyer (daan.j.demeyer@xxxxxxxxx) wrote:

> > About your other comments, systemd sits in user space and can query
> (depend
> > upon) terminfo.  Then, it should be able to support "whatever" terminfo
> has
> > defined.... which could include custom terminals by the way that an end
> user has
> > added.  And while all of that sounds incredibly ancient/old, I was on a
> project
> > post 2000 that had to do exactly that (of course, even that might sound
> too old).
>
> Interestingly enough, systemd's colors work even when TERM is set to vt220,
> probably because it uses ansi escape codes regardless of the TERM setting.
> I think there's probably lots of applications doing this except for ls in
> coreutils which has an explicit list of terminals with color support
> encoded in the dircolors configuration file.  If TERM isn't one of those,
> you don't get colors. There's probably others that do this as well. I don't
> think changing the default in systemd is a good idea since it might break
> other stuff. I'm going to submit a mkosi PR instead that adds an option
> that overrides serial-getty@ttyS0 with whatever terminal the user wants.
> Colors won't work out of the box but at least it shouldn't be too hard to
> find out how to get them to work when using mkosi.

Again, I'd be happy to switch to a different default for serial
terminals if we can find a reasonable one that is available widely in
termcap, that does color, and is a subset of both TERM=linux and
TERM=xterm.

Lennart

--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel



[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux