> 1) Ignore /etc/ttytype 'cause the kernel has already set 'linux'
> OBKernel: IMO the kernel should NOT set the terminal type any more,
> init/getty, telnetd and rlogind are by far better places.
> With the existance of serial and printer consoles having
> the terminal type defined during /etc/rc has become stupidly
> dangerous.
Hmmm... Not sure about this one... I'm not having this problem
at all with my setups. Interestingly enough, my systems don't even HAVE
a /etc/ttytype file and the man page on getty specifies the terminal type
set on the command like. There's also no reference to /etc/ttytype in
the man pages for getty or mgetty. I haven't used /etc/ttytype since
working on old SCO systems.
Have you tried setting the terminal type on the command line in
the inittab file like this:
s0:345:respawn:/sbin/getty ttyS0 38400 wy50
^^^^
> 2) Keep writing records to wtmp if the terminal is turned off, eventually
> restarting so often that init disables the inittab line.
I've actually seen this, some time ago. Some "dumb tubes" end up
dragging down CF and DSR when powered off. I remember seeing a "dongle"
with some pull-up resistors to fix that. You got a hardware problem there.
What'cha got? Some old Wyse 50/60/75's or some old VT100's?
> 3) Ignoring a positive DTR/DSR transition and not transmitting a banner
> until the user types a CR.
> 4) Ignoring a negitive DTR/DSR transition by not setting CLOCAL and
> HUPCL for the /bin/login program.
> 5) Keep timing out the input on the terminal line every 60 seconds while
> DTR/DSR is active again filling up wtmp with useless records and
> possibly causing itself to be disabled by init when the terminal is
> left turned on.
man gettydefs
All three of those sound like the wrong gettydefs configuration.
Since most of the "getty's" I use refer back to gettydefs for their setup
and configuration, I would expect them to act very similarly. Certainly,
assuming your hardware is wired correctly, HUPCL and CLOCAL are gettydefs
options.
> None of the standard ones supposedly designed for seial ports actually seem
> to work correctly. The 'mingetty' program seems to do the right thing but
> it doesn't have speed setting or speed change on BREAK. So I grabbed the
> source and hardwired the speed to 115k2 and it works perfectly now.
I use this and haven't had any problems. I've got hardwired
connections, modem connections and cross-coupled consoles between systems.
Only thing I had to do was fine tune the gettydefs file or chose the right
gettydefs entry initially. This all sounds like configuration problems.
Oh... And I don't think I was able to get 115.2 working for the cross
coupled consoles, because lilo doesn't support that speed (although the
kernel does).
Other problem I DID run into was when the morons who assembled the
Mandrake distribution came up with the bright idea of putting the cutesy
color ascii penguin in /etc/issue. That totally hoses any serial logins
(modem or direct) because the file has term type Linux escape codes in it
and lord only knows what you are connecting with... Grrrr....
> --
> Rob. (Robert de Bath <http://poboxes.com/rdebath>)
> <rdebath @ poboxes.com> <http://www.cix.co.uk/~mayday>
>
> On Mon, 20 Sep 1999, wu_yb wrote:
>
> > I use a linux box as firewall, and manage it from a terminal
> > attatched to its COM1. If I exit hyperterminal without logout from
> > linux, the next time I open the terminal, linux doesn't prompt me
> > for passwd, as if I don't exit since last login.
> > ( linux 2.0.35, agetty )
Hmmm... I don't use agetty. I use getty for hardwired, mingetty
on the consoles, and mgetty for modems. Don't know about agetty. Don't
even have it on any of my RedHat, Mandrake, or TurboLinux systems...
> > Please CC to me.
Mike
-- Michael H. Warfield | (770) 985-6132 | mhw@WittsEnd.com (The Mad Wizard) | (770) 331-2437 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/