rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (08/29/90)
I've haven't followed the thread of this, but ... No matter what you call it, xdm handles a person logging in yet makes it impossible to use the .login file. 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. Any situation which allows the reading of .login doesn't allow for checking envar's or using stty and such. Please explain each of these individually in more detail (and elaborate "and such"). Using stty outside the context of a terminal emulator with a pty seems pretty uninteresting to me. If xdm wants to act like a login shell make it act like a login shell instead of only doing half the job. 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.
rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (08/31/90)
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...
I have sent you private mail about ways of doing this. I believe it can be
done without changing xdm.
If xdm is not a login interface,
Reread what I wrote. I said it does not act like a login *shell* (in the
sense of how I understand you to interpret the word "shell"). If you want
to enforce a particular policy on sessions at your site, I believe xdm will
let you do so.
I changed these so that the users would quit asking
this question. Is xdm distributed with these defaults?
Making the default prompt something besides login? No, I wouldn't distribute
xdm that way. I wouldn't want to confuse people. :-)harkcom@potato.pa.Yokogawa.CO.JP (Alton Harkcom) (09/01/90)
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$@<R(J PA$@#15;#22](J TEL 0422-52-5748 FAX 0422-55-1728 E-mail harkcom@pa.yokogawa.co.jp