From owner-freebsd-questions Thu May 30 12:20:59 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA12953 for questions-outgoing; Thu, 30 May 1996 12:20:59 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA12946 for ; Thu, 30 May 1996 12:20:55 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id MAA25518; Thu, 30 May 1996 12:20:50 -0700 Date: Thu, 30 May 1996 12:20:49 -0700 (PDT) From: Veggy Vinny To: Sean Kelly cc: terry@lambert.org, terry@lambert.org, questions@FreeBSD.ORG Subject: Re: long motd files - screen pause? In-Reply-To: <199605301528.PAA16583@gatekeeper.fsl.noaa.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 30 May 1996, Sean Kelly wrote: > >>>>> "Veggy" == Veggy Vinny 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