"You know, it is at times like these, when having to deal with systemd instead of /etc/inittab, that I really wish I had listened to my mother when I was young!"
"Why? What did she tell you?" "I don't know! I didn't _listen_!" (laughs maniacally having inserted an HHGTTG meme into this stream) All right, I tend to be leery of "hidden" (non-flat-text) configurations; It reminds me a lot of the M$ "registry" which requires special tools to manage. In the "good old days" (v7 and even System III) /etc/termcap, /etc/printcap and /etc/inittab were places you went to to configure various thingies. With SysV, howsomever, the transition to terminfo happened ... which threw me for a loop, at first, and eventually adapted to as a developer. While *BSD had gone more-or-less away from /etc/inittab, you had _other_ tools to deal with terminal support. Nowadays I miss the transparency of these kinds of configuration files... Look, there are reasons to progress towards the less transparent forms of these files (yeah, yeah, I remember when the encrypted password was removed from /etc/passwd and relegated to /etc/shadow... along with a bunch of other "cool" settings... and, frankly, I could accept the rationale. (Admittedly, AIX's version of the password file was WEIRD, but, then, AIX is short for "AIn't uniX".) Mind you, the first culture shock, vis a vis linux, was there was no "character" device for disk drives, so you could not avoid OS's block device management. (shrugs) Admittedly, I would have preferred "progress" to NOT have driven a bypass through the management of my computer system's OS, but, hey, adapt, improvise and automate. -soup On Fri, Oct 20, 2017 at 10:32 AM, Hendrik Brueckner < [email protected]> wrote: > On Fri, Oct 20, 2017 at 07:55:41AM -0600, Mark Post wrote: > > >>> On 10/20/2017 at 08:38 AM, Dimitri John Ledkov <[email protected]> > wrote: > > -snip- > > > Why do you want to use TERM=dumb instead of Linux? > > > > Because, as you know, the uninterpreted escape sequences makes it very > difficult to pick out the real information on the screen. > > > > Just an idea to try out: systemd creates console and getty service unit > instances for the terminals. You can try to use systemctl edit and change > the TERM environment variables for s390 terminal devices to dumb. The > service > unit starts agetty and specifies the TERM as part of the command line. > > With systemctl edit you simply create an overwrite of the service unit and > the change (or its full version) is then stored in /etc/systemd. > > Hope that hint helps a bit. > > Thanks and kind regards, > Hendrik > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- John R. Campbell Speaker to Machines souperb at gmail dot com MacOS X proved it was easier to make Unix user-friendly than to fix Windows "It doesn't matter how well-crafted a system is to eliminate errors; Regardless of any and all checks and balances in place, all systems will fail because, somewhere, there is meat in the loop." - me ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
