On Wed, Sep 07, 2005 at 06:30:58AM -0700, Dan Nicholson wrote:
/ Archaic wrote:
// xdm isn't messing with the path in the way that you think. xdm is it's
// own login prompt.
//
// Thanks, that's a really good explanation. Same to Simon from the other
// reply. I still don't understand why
--- Dan McGhee [EMAIL PROTECTED] wrote:
On Wed, Sep 07, 2005 at 06:30:58AM -0700, Dan Nicholson wrote:
The config files are in /etc/X11/xdm. Xsession even has scripting to
source profile and ~./bash_profile.
Should I play it really safe and put a test in?
if [ -f /etc/profile ]; then
On Wed, 2005-09-07 at 06:30 -0700, Dan Nicholson wrote:
OK, so now I'm convinced that xdm and gdm aren't as evil as I thought,
how can I configure them to mock my /bin/login procedure? Where are the
config files?
Well, one of the key files for gdm is /etc/gdm/Xsession (assuming built
with
Archaic wrote:
xdm isn't messing with the path in the way that you think. xdm is it's
own login prompt.
Thanks, that's a really good explanation. Same to Simon from the other
reply. I still don't understand why they wouldn't use the standard
login procedure and build the environment from
Hi everyone,
I've seen some remarks on this issue, but I'm hoping that someone can
help me put them all together here. It seems that using a display
manager like xdm or gdm, or even just running X, overwrites important
variables set for a login shell. I don't like this behavior at all, and
Randy McMurchy wrote:
[EMAIL PROTECTED]: ~ cat .profile
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
==
[EMAIL PROTECTED]: ~ cat .bashrc
. /etc/profile
[snip everything else that I want for me]
I agree that that works, and that's probably what I'm going to
