Date: Thu, 30 May 1996 12:20:49 -0700 (PDT) From: Veggy Vinny <richardc@CSUA.Berkeley.EDU> To: Sean Kelly <kelly@fsl.noaa.gov> Cc: terry@lambert.org, terry@lambert.org, questions@FreeBSD.ORG Subject: Re: long motd files - screen pause? Message-ID: <Pine.PTX.3.91.960530121931.29367O-100000@soda.CSUA.Berkeley.EDU> In-Reply-To: <199605301528.PAA16583@gatekeeper.fsl.noaa.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 30 May 1996, Sean Kelly wrote: > >>>>> "Veggy" == Veggy Vinny <richardc@CSUA.Berkeley.EDU> writes: > > Veggy> Hmmm, okay but how do some machines make the motd > Veggy> pause even before it knows the termcap? > > By ``cheating'' with the default user setup, perhaps. > > When creating new users, just give 'em a .hushlogin file so > /usr/bin/login won't do any of the normal introductory stuff. Then, > give 'em a .login (assuming csh/compatible here) that does the > following: > > 1. Determines the terminal type. > 2. Shows if password is about to expire (two week warning). > 3. Shows if account is about to expire (two week warning). > 4. Show last login. > 5. Warn if no kerberos tickets are issued. > 6. Show the Regents copyright. > 7. Page the motd. > 8. Show if there's mail. > > Step 7 will work as a consequence of step 1. I looked and there was no .hushlogin file, somehow they get the motd to page for some reason. This is the uname -a output for the machine: soda.CSUA.Berkeley.EDU% uname -a DYNIX/ptx soda 4.0 V4.0.1 i386 I still wonder how did they do it though. Vince
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.PTX.3.91.960530121931.29367O-100000>