Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!sun-barr!ccut!wnoc-tyo-news!dclsic!sjc!spider!leia!harkcom From: harkcom@potato.pa.Yokogawa.CO.JP (Alton Harkcom) Newsgroups: comp.windows.x Subject: Re: using .login under xdm Message-ID: Date: 31 Aug 90 17:49:03 GMT References: <9008291413.AA09697@expire.lcs.mit.edu> Sender: news@leia.pa.yokogawa.co.jp Organization: Yokogawa Electric Corporation, Tokyo, Japan. Lines: 23 In-reply-to: rws@EXPO.LCS.MIT.EDU's message of 29 Aug 90 14:13:02 GMT In article <9008291413.AA09697@expire.lcs.mit.edu> rws@EXPO.LCS.MIT.EDU (Bob Scheifler) writes: =}My .xsession sources my .login. I'm happy. Perhaps you have a different =}definition of"use".Perhaps you could explain this definition in more detail. by sourcing a .login file, I mean being able to use something besides 'setenv' in that file. Checking the values of envars and using stty to set up default control sequences are very important to those of us who use 2byte characters in our non-English-only terminal emulators... =}xdm does not act like a login shell. xdm provides login authentication =}and means for running a session. One of the things you can start up =}in your session is a shell. If xdm is not a login interface, then why does the default prompt say "login" and "passwd"? I changed these so that the users would quit asking this question. Is xdm distributed with these defaults? -- -- $@2#2OEE5!3t<02q(J$@