Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!think!ames!ucsd!ucsdhub!hp-sdd!ncr-sd!rancho!rock
From: rock@rancho.uucp (Rock Kent)
Newsgroups: comp.unix.i386
Subject: Re: /etc/issue choking uucp logins
Message-ID: <1989Dec26.062006.13829@rancho.uucp>
Date: 26 Dec 89 06:20:06 GMT
References: <4927@gaboon.UUCP>
Organization: Del Rayo Ranch, San Diego, CA
Lines: 27
In-Reply-To: asv@gaboon.UUCP's message of 25 Dec 89 05:13:56 GMT

>>>>> On 25 Dec 89 05:13:56 GMT, asv@gaboon.UUCP (Stan Voket) said:
Stan>      I have a full screen /etc/issue that I'd like to display on
Stan>      unused terminals to clear a previous user's work for
Stan>      security and neatness.  However, a full screen of anything
Stan>      is not what another machine likes or needs when trying to
Stan>      login for a uucp transfer.  It has caused remote logins to
Stan>      fail.  How can I display my large /etc/issue for local
Stan>      terminals but not on dialup lines?

I can think of two possible approaches:

SIMPLE:  Assuming that all of your local terminals are known and have
similar screen control sequences, embed the *clear screen and home
cursor* control sequence into either the login prompt or the
/etc/issue and blow off the screen full of ascii graphics or whatever.

HARDER:  Get yourself a copy of a getty source (e.g. T William Wells'
getty.c copywrite 1989) and hack into it the intelligence to tell the
difference between different local and remote terminal lines.

NOTE that, although I am running Wells' getty under Microport V/386, I
haven't tried either of the above stunts and wouldn't bet my system on
the feasability of either one.  Let us know how it turns out.

***************************************************************************
*Rock Kent    rock@rancho.uucp        POB 8964, Rancho Sante Fe, CA. 92067*
***************************************************************************