Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Remote X problem (Linux to SCO Unix)



At some point hitherto, Paul Lussier hath spake thusly:
> To my knowledge neither XDM nor Exceed can do this.  Upon login, 
> either will invoke your .xsession (or is it .xinitrc?) file.  If that 
> is configured to start up apps, then that's where it's happening.

The traditional order is: .xsession is sourced by xdm if it exists.
.xinitrc is sourced by startx, if it exists.  If neither exist, both
programs will look for a .Xclients file.

However, both xdm and startx start their sessions by running shell
scripts (startx IS a shell script), and if you can find those scripts
(they can be in /etc/X11, /usr/X11R6/blah, somewhere down /var, or
just about anywhere), then you can edit them to change what gets
sourced when and by whom.

Of course, only eeeevil sysadmins would do this...

-- 
Derek Martin               ddm at pizzashack.org    
---------------------------------------------
I prefer mail encrypted with PGP/GPG!
GnuPG Key ID: 0x81CFE75D
Retrieve my public key at http://pgp.mit.edu
Learn more about it at http://www.gnupg.org




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org