David Lockwood wrote:
> If I "login" inside an xterm using
> $ su - username
> (Password)
> I can no longer start another xterm from that xterm, getting
> xterm Xt error: Can't open display:
man xhost
--
Lennon Victor Cook
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://ww
On 11/11/05, Simon Geard <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-11-11 at 13:26 +1000, David Lockwood wrote:
> > But /bin/sh is just a symlink to /bin/bash, the same binary runs. I
> > didn't think of this straight away because I knew bash was the only
> > shell I had installed, and I thought fro
On Fri, 2005-11-11 at 13:26 +1000, David Lockwood wrote:
> But /bin/sh is just a symlink to /bin/bash, the same binary runs. I
> didn't think of this straight away because I knew bash was the only
> shell I had installed, and I thought from my reading that "bash +
> login = ~/.bash_profile gets rea
Solved. I'm not sure if anybody felt the answer was too obvious - if so I
apologise. But it's not an answer I came across anywhere else and shells don't
work the way I thought they did.
The problem was a simple error in /etc/passwd - my userid didn't have the
default shell specified (/bin/bash
David Lockwood wrote:
> If I "login" inside an xterm using
> $ su - username
> (Password)
> I can no longer start another xterm from that xterm, getting
> xterm Xt error: Can't open display:
Same with my System, I think this is good system behavior, why should
another user be allowed to open a Win
Hi. I have read some previous threads about startup scripts but can't work
out the answer to this problem. I beg some patience from those who have been
through all this before.
My ~/.bash_profile is not run under circumstances where I think it's supposed to
be.
~/.bash_profile _does_ run when I
