I have a significant installed base (more than 1000) of CRT’s and printers attached to Digi XEM 16’s that were attached to NCR UNIX SVR4 or IBM AIX systems. All of these devices are running 7-bits, 1-stop bit, Even parity, and either 19200 or 9600 baud. The new servers we want to deploy are running RedHat ES4.
Using agetty, it displays the /etc/issue file and the Login: prompt using 7-bits, 1-stop, and SPACE parity - looks like garbage. If you type stuff in at that point, it figures out the 7/1/E part, but that only stays set until you log out. Therefore you never get to see /etc/issue legibly.
Linux agetty allows command line specs for baud, but not word/parity/stop settings. I tried setting them with stty, but agetty always overrides it, then tries to figure it out during login.
Everything looks good if the CRT is set to 8/1/N, but this means changing all of the devices and having settings sheets that are specific to the system (right now we use the same setups for AIX & NCR UNIX systems). My helpdesk wouldn’t be very happy with me if we go that way.
Is there a way to use agetty or is there another getty that would allow control of the word/parity/stop settings? I’ve been messing around with mgetty, but I’m not having much luck with these directly connected devices.
Thanks,
Rick.