Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!sun-barr!ccut!kogwy!wnoc-tyo-news!dclsic!sjc!spider!leia!harkcom From: harkcom@potato.pa.Yokogawa.CO.JP (Alton Harkcom) Newsgroups: fj.windows.x,fj.sys.news,comp.windows.x Subject: xdm => bug (or should I call it an insect) Message-ID: Date: 15 Aug 90 19:33:20 GMT Sender: news@leia.pa.yokogawa.co.jp Followup-To: fj.windows.x Organization: Yokogawa Electric Corporation, Tokyo, Japan. Lines: 21 It may just be something that was overlooked or was thought to be unneccesary ( => insect). Or it may just be a mistake ( => bug). I recently started using xdm. At first I thought "no problem, I can put up with the changes". Now I see that it is more than a minor change. xdm doesn't read the 'login' file when it logs in a user. This makes for some nasty complaints from the users. I have put most of the stuff from my login file into the xsession file and the rest into cshrc file. But then there arises a problem of using bourne shells or kourne shells or whatever-you-call-them shells. There is also the problem of users who want things to be left the way they are "because thats the way they are". Anybody got a solution or should I just trash xdm and take the flak. -- -- $@2#2OEE5!3t<02q