Subject: Re: xterminal permissions?
From: goo (goo@radek.org)
Date: Wed Sep 06 2000 - 01:26:19 MDT
> Ummm... maybe I am, I'm not sure I know what you mean by the console window,
> but I did try it in xterm with the same results. (see below)
We can forget this line of thought -- I'm not terribly familiar with KDE,
and didn't know you were using it anyway, so I didn't realize that "Konsole"
was just a KDE xterm.
> It appears I'm missing /sbin in all my paths except as root in level 3 --is
> this YD's default or did I mess up when upgrading to XF4? I don't see a
> problem with this if it's some sort of a security feature, but how would I
> go about changing a PATH if I wanted to? Could I just place a symlink of
> certain commands from the sbin directory to say the /usr/local/bin directory
> and have it work?
Yup, the PATH's the thing. Or maybe Shakespeare said something else.
Anyway, am I correct in assuming that you're in X at runlevel 5, but on a
text console at runlevel 3? Yeah, I guess I can see that from your output.
The PATH can get set up differently in an X login from a normal text console
login, primarily through using different shells between an xterm and console
login. However, I notice that you used "su" to check the path as root. The
"su" command doesn't work exactly the same as logging in. You usually end
up with the "sh" shell instead of "bash", for example.
What you suggest with symlinks would work, but it's not the proper solution.
You should spend some time investigating the various scripts that run to set
up your environment when you login, and figure out how to fit them together
to get the proper results.
Here are some files to get you started:
/etc/profile
/etc/conf/profile
~/.profile
Read the man pages for login, bash, sh, xdm, kde, su, and anything else you
can think of. :)
> As root: bash:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin: No
> such file or directory
>
> As karl: bash:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin: No such file or
> directory
"No such file or directory" isn't part of the path. The proper way to
examine your PATH (or any other environment variable, for that matter) is to
use the "echo" command:
bash-2.03$ echo $PATH
Anyway, what you did was try to /execute/ your PATH, so bash was trying to
tell you it wasn't a valid command.
It's entirely proper for root's path to include the sbin directories while a
regular user's path does not. That's no excuse for not setting the execute
permissions correctly on those programs so regular users can't use what
they're not supposed to, but that's beside the point.
This archive was generated by hypermail 2a24 : Wed Sep 06 2000 - 01:31:31 MDT