Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!cbmvax!vu-vlsi!devon!paul
From: paul@devon.UUCP
Newsgroups: comp.unix.questions
Subject: Re: Suppressing SCO Xenix motd
Message-ID: <270@devon.UUCP>
Date: Tue, 26-May-87 20:56:34 EDT
Article-I.D.: devon.270
Posted: Tue May 26 20:56:34 1987
Date-Received: Thu, 28-May-87 06:38:31 EDT
References: <7526@brl-adm.ARPA>
Reply-To: paul@devon.UUCP (Paul Sutcliffe Jr.)
Followup-To: comp.unix.xenix
Distribution: world
Organization: Devon Computer Services, Allentown, PA
Lines: 32
Keywords: SCO Xenix motd
Summary: One possible solution

In article <7526@brl-adm.ARPA> jl42#@andrew.cmu.EDU (Jay Mathew Libove) writes:
> Well, we have all sorts of neat ways posted now for suppressing a
> standard BSD m.o.t.d., but I have a slightly different problem - my
> Xenix (by the Santa Cruz Operation, SysV/286 v2.1.3 kernal running on
> a PCs Limited AT) IGNORES .hushlogin ... and I do wish to keep the
> motd file.
> 
> Anyone know a way around this?

    Trouble is, Xenix's /etc/login is AT&T based, not BSD.  So it  doesn't
    know anything about a .hushlogin (strictly a Berkeleyism).

    But  you  could  try  this:   First,  rename  the  /etc/motd  file  to
    /etc/Motd.   The /etc/login program won't be looking for that name, so
    it won't display anything.  Then place some statements in /etc/profile
    (which  is  processed  by  every  /bin/sh  login  shell)  and  similar
    statements in /etc/cshrc (XENIX  only:  processed  by  every  /bin/csh
    login  shell)  to  type  the  contents  of  /etc/Motd  under  whatever
    circumstances you wish.

    It is left as an exercise to the reader to determine just exactly what
    statements should be added to /etc/profile or /etc/cshrc.

    I have directed followups to comp.unix.xenix.

-paul

-- 
Paul Sutcliffe, Jr.		UUCP: paul@devon.UUCP
				      ...!seismo!bpa!vu-vlsi!devon!paul

"No problem is so big that it can't be run away from." -- Charlie Brown