Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-23 Thread Matwey V. Kornilov
Dear all, I've just read the discussion with a great interest. What I would like to add is that there a people (like me) who use real world serial consoles (not emulated as in qemu) for working with ARM single board computers. I usually use 'screen' terminal emulator to connect to /dev/ttyUSB0

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-21 Thread Lennart Poettering
On Mo, 20.07.20 10:13, Bruce A. Johnson (bjohn...@blueridgenetworks.com) wrote: > Reading this discussion about VT220, I'm wondering why that was the > choice and not VT100 (which was also monochrome). And I'm straining my > memory to recall what it was that we had back then that made the VT100 >

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-21 Thread Lennart Poettering
On Mo, 20.07.20 15:03, s...@collabora.com (s...@collabora.com) wrote: > On Sat, 11 Jul 2020 at 21:04:18 +0200, Lennart Poettering wrote: > > widely-supported TERM value > > For a value of TERM to work (at all), it must be something that is reliably > present in the terminfo/termcap data visible

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-20 Thread Bruce A. Johnson
Reading this discussion about VT220, I'm wondering why that was the choice and not VT100 (which was also monochrome). And I'm straining my memory to recall what it was that we had back then that made the VT100 seem so slick and futuristic. Bruce A. Johnson | Firmware Engineer Blue Ridge Networks,

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-20 Thread smcv
On Sat, 11 Jul 2020 at 21:04:18 +0200, Lennart Poettering wrote: > widely-supported TERM value For a value of TERM to work (at all), it must be something that is reliably present in the terminfo/termcap data visible to TUI programs. Debian divides terminfo into two categories. It wouldn't

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-15 Thread Daan De Meyer
> Well, --color means you request color no matter what, so this is not surprising. I actually only got color because TERM was set to xterm-256color. ls won't output color if TERM is set to vt220. It checks against a hardcoded list of terminals to determine whether it'll output colors or not. See

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-15 Thread Lennart Poettering
On Di, 14.07.20 22:15, Daan De Meyer (daan.j.deme...@gmail.com) 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

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-15 Thread Lennart Poettering
On Di, 14.07.20 19:48, Daan De Meyer (daan.j.deme...@gmail.com) wrote: > I just tried vt241 and didn't get colorized output in konsole. I looked > around a bit and it doesn't really seem supported at all by terminal > emulators (or at least none that I found). I also tried TERM=xterm-256color >

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-15 Thread Michał Zegan
Note there is an easy way to override term type. The default serial-getty@.service at least here has no TERM set by default, but uses it to set term type when launching getty. You can use kernel command line and add TERM=screen for example, or things like that, and it should be picked up,

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-14 Thread Christopher Cox
On 7/14/20 4:27 PM, Mantas Mikulėnas wrote: On Tue, Jul 14, 2020 at 9:48 PM Daan De Meyer > wrote: I just tried vt241 and didn't get colorized output in konsole. I looked around a bit and it doesn't really seem supported at all by terminal emulators

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-14 Thread Mantas Mikulėnas
On Tue, Jul 14, 2020 at 9:48 PM Daan De Meyer wrote: > I just tried vt241 and didn't get colorized output in konsole. I looked > around a bit and it doesn't really seem supported at all by terminal > emulators (or at least none that I found). I also tried TERM=xterm-256color > with 8 different

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-14 Thread Daan De Meyer
> 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

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-14 Thread Christopher Cox
On 7/14/20 1:48 PM, Daan De Meyer wrote: I just tried vt241 and didn't get colorized output in konsole. I looked around a bit and it doesn't really seem supported at all by terminal emulators (or at least none that I found). I also tried TERM=xterm-256color with 8 different terminal emulators

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-14 Thread Daan De Meyer
I just tried vt241 and didn't get colorized output in konsole. I looked around a bit and it doesn't really seem supported at all by terminal emulators (or at least none that I found). I also tried TERM=xterm-256color with 8 different terminal emulators and got colors with all of them. My workflow

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-14 Thread Christopher Cox
On 7/14/20 3:19 AM, Lennart Poettering wrote: On Mo, 13.07.20 18:16, Christopher Cox (c...@endlessnow.com) wrote: No vt220 does not support colour. I used to work on one and it is monochrome hardware. Xterm and konsole support extensions beyond vt220 that add in the colour support. Not sure

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-14 Thread Lennart Poettering
On Mo, 13.07.20 18:16, Christopher Cox (c...@endlessnow.com) wrote: > > No vt220 does not support colour. I used to work on one and it is > > monochrome hardware. > > Xterm and konsole support extensions beyond vt220 that add in the colour > > support. > > Not sure how much (offtopic) history we

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-13 Thread Christopher Cox
On 7/13/20 4:08 PM, Barry wrote: On 11 Jul 2020, at 20:31, Daan De Meyer wrote:  > TERM=linux means Linux console, but that's just too much, as it not > only implies a multitude of ESC sequences specific to the Linux > console, but also indicates that certain ioctls might work. In our own

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-13 Thread Barry
> On 11 Jul 2020, at 20:31, Daan De Meyer wrote: > >  > > TERM=linux means Linux console, but that's just too much, as it not > > only implies a multitude of ESC sequences specific to the Linux > > console, but also indicates that certain ioctls might work. In our own > > code we also bind

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-11 Thread Daan De Meyer
Nevermind that, I just forgot to remove my override file that set TERM=linux for serial-getty@ttyS0. Daan On Sat, 11 Jul 2020 at 20:31, Daan De Meyer wrote: > > TERM=linux means Linux console, but that's just too much, as it not > > only implies a multitude of ESC sequences specific to the

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-11 Thread Daan De Meyer
> TERM=linux means Linux console, but that's just too much, as it not > only implies a multitude of ESC sequences specific to the Linux > console, but also indicates that certain ioctls might work. In our own > code we also bind certain behaviour to TERM=linux, as indicator if we > are on the

Re: [systemd-devel] vt220 default for serial console still relevant?

2020-07-11 Thread Lennart Poettering
On Sa, 11.07.20 17:51, Daan De Meyer (daan.j.deme...@gmail.com) wrote: > Hi, > > I was playing around with mkosi's qemu support, more specifically adding > the -nographic option to have the virtual machine output in my terminal > instead of a separate window. After figuring out that I had to add