Xdm and startx

J.A. Neitzel jan.listbox at belvento.org
Wed Oct 24 07:32:05 PDT 2001


Craig Colton wrote:
<snip />
>> From the reference above... This has nothing to do with xdm. xdm does
>> not give error, but startx does. To diagnose, from a VT /dev/tty[1-6]
>> do a `echo $PATH' and see if it contains /usr/X11R6/bin .
>>
>> If your PATH does not contain the path to startx and friends then you
>> will get this error. Add /usr/X11R6/bin to your PATH; refer to the
>> actual /usr/X11R6/bin/startx script for more info about how startx is
>> doing its thing...
>>
>> HTH
> 
> I was under the impression (possibly incorrect) that xdm authorizes all
> requests for a display. How might xdm be in one's path and not startx?

Have you set your PATH to include /usr/X11R6/bin ? xdm BTW does not
read any of your shell startup files unless you explicitly tell it to
do so somewhere in /etc/X11/xdm/Xsession or by some other method.

Also, xdm-config has the following possibility:

DisplayManager.DISPLAY.userPath
       Xdm sets the PATH environment variable for the ses-
       sion to this value.

==== Abbreviated Explanation =) ====
Well, one difference between the two is that xdm is started by someone
(i.e., superuser) and left running for the purpose of managing
displays. xdm doesn't really know anything about the user...

startx OTOH, *is* started directly by the user. The user's environment
in effect when startx is run gets ?_adopted_? by all of the child
processes.
-- 
Jeff

-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe blfs-support' in the subject header of the message



More information about the blfs-support mailing list