Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!novavax!twwells!bill
From: bill@twwells.com (T. William Wells)
Newsgroups: comp.unix.i386
Subject: Re: getty replacement
Message-ID: <1990Jan1.150934.7517@twwells.com>
Date: 1 Jan 90 15:09:34 GMT
References: <259cff98:549comp.unix.i386@tronsbox.UUCP> <1989Dec31.015909.23878@ <259ea868:549.2comp.unix.i386;1@tronsbox.UUCP>
Organization: None, Ft. Lauderdale, FL
Lines: 32

In article <259ea868:549.2comp.unix.i386;1@tronsbox.UUCP> tron1@tronsbox.UUCP (HIM) writes:
: >If the latter, you can, with my soon to be released getty,
: >specify an alternate /etc/issue file. If the former, you are
: >probably out of luck.
:
: That will do nicely.
:
: Actually no , it wont. This would happen AFTEr the getty ran , but before CD
: went high since this has to happen BEFORE the connect.

As I recall, you have two (or more?) devices for talking to a
given modem line. One waits for CD; the other doesn't. Assuming
that that is what you have, try this: create a getty script,
something like:

{                                       # send commands to the modem
	echo "whatever"
	echo "more"
	....
} >/dev/tty-ignore-CD
exec /etc/getty /dev/tty-wait-for-CD    # run the real getty

and run that from your inittab instead of the regular getty.

There is one way this might fail. If, after the echos, DTR is
dropped, that might make the modem reinitialize itself. If that
is the case, you can move the exec into the braces. That will
work with my getty; it may work with the standard one.

---
Bill                    { uunet | novavax | ankh | sunvice } !twwells!bill
bill@twwells.com