Path: utzoo!attcan!uunet!ogicse!ucsd!ucbvax!ucbarpa.Berkeley.EDU!edward
From: edward@ucbarpa.Berkeley.EDU (Edward Wang)
Newsgroups: comp.windows.x
Subject: Re: Should login xterms show /etc/motd?  (R5 wet dreams?)
Message-ID: <37719@ucbvax.BERKELEY.EDU>
Date: 23 Jul 90 23:45:04 GMT
References: <1990Jul18.200754.13129@cs.umn.edu> <678@venice.SEDD.TRW.COM> <1990Jul20.180959.21846@cs.umn.edu> <5877@crltrx.crl.dec.com> <1990Jul23.201745.11646@cs.umn.edu>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: edward@ucbarpa.Berkeley.EDU.UUCP (Edward Wang)
Organization: University of California, Berkeley
Lines: 13

In article <1990Jul23.201745.11646@cs.umn.edu> brsmith@cs.umn.edu (Brian R. Smith) writes:
>Ok - so the best fix would be to:
>  Have xterm NOT do the utmp/wtmp stuff.  (Quick Imakefile hack.)
>  Have "login" xterms run "/bin/login -h $DISPLAY -fp $USER" as root.

Actually, even with the right version of login,  this isn't a solution,
because there's nobody to do the logout part of utmp and wtmp fixing.
Currently, this is done whatever programs that invoke login: init, rlogind,
and so on.  (Brian: I know I suggested using login -f, but with a caution.)
The correct solution seems to be a server-based pty server.
There seem to be people working on this here at Berkeley.

The original Unix login design is outliving its usefulness.