Difference between revisions of "Talk:Ubuntu Customization"
(Created page with "== vncserver == Warning: foo:1 is taken because of /tmp/.X1-lock Remove this file if there is no X server foo:1 xauth: file /root/.Xauthority does not exist New 'X' de...") |
(→Ways to set $PATH: new section) |
||
| (One intermediate revision by one user not shown) | |||
| Line 10: | Line 10: | ||
Starting applications specified in /root/.vnc/xstartup | Starting applications specified in /root/.vnc/xstartup | ||
Log file is /root/.vnc/foo:2.log | Log file is /root/.vnc/foo:2.log | ||
| + | |||
| + | == Thunar == | ||
| + | |||
| + | Run Thunar file explorer as root | ||
| + | |||
| + | sudo Thunar | ||
| + | |||
| + | == Ways to set $PATH == | ||
| + | |||
| + | The PATH can be set in any of | ||
| + | |||
| + | ~/.bashrc | ||
| + | ~/.profile | ||
| + | ~/.bash_profile | ||
| + | ~/.bash_login | ||
| + | /etc/profile | ||
| + | /etc/environment | ||
| + | /etc/bash.bashrc | ||
| + | |||
| + | Which ones are read depends on the kind of bash session you are running. What you want to do is grep for PATH in all these files. | ||
| + | |||
| + | $ grep PATH ~/.bashrc ~/.profile ~/.bash_profile ~/.bash_login \ | ||
| + | /etc/profile /etc/environment /etc/bash.bashrc | ||
| + | |||
| + | I have a nifty little bash function for just this sort of issue: | ||
| + | |||
| + | grep_bash(){ | ||
| + | for f in ~/.bashrc ~/.profile ~/.bash_profile ~/.bash_login \ | ||
| + | /etc/profile /etc/environment /etc/bash.bashrc; | ||
| + | do | ||
| + | [ -e $f ] && grep -H "$@" $f; | ||
| + | done | ||
| + | } | ||
| + | |||
| + | I have that in my .bashrc so whenever something strange is going on, I use it to look for the relevant string in all possible config files. For example: | ||
| + | |||
| + | $ grep_bash PATH | ||
| + | |||
| + | As a side note, not having /sbin and /usr/sbin in a normal user's PATH is standard practice for most distributions. There is no reason for a normal user to have these directories in their path. I just checked on a Debian, and Ubuntu Server and a SuSe machine and only the Ubuntu seems to add /sbin to a normal user's path and it does so in /etc/environment. The other two only add it if the user is root. | ||
Latest revision as of 17:45, 18 February 2015
vncserver
Warning: foo:1 is taken because of /tmp/.X1-lock Remove this file if there is no X server foo:1 xauth: file /root/.Xauthority does not exist New 'X' desktop is c3po:2 Creating default startup script /root/.vnc/xstartup Starting applications specified in /root/.vnc/xstartup Log file is /root/.vnc/foo:2.log
Thunar
Run Thunar file explorer as root
sudo Thunar
Ways to set $PATH
The PATH can be set in any of
~/.bashrc ~/.profile ~/.bash_profile ~/.bash_login /etc/profile /etc/environment /etc/bash.bashrc
Which ones are read depends on the kind of bash session you are running. What you want to do is grep for PATH in all these files.
$ grep PATH ~/.bashrc ~/.profile ~/.bash_profile ~/.bash_login \
/etc/profile /etc/environment /etc/bash.bashrc
I have a nifty little bash function for just this sort of issue:
grep_bash(){
for f in ~/.bashrc ~/.profile ~/.bash_profile ~/.bash_login \
/etc/profile /etc/environment /etc/bash.bashrc;
do
[ -e $f ] && grep -H "$@" $f;
done
}
I have that in my .bashrc so whenever something strange is going on, I use it to look for the relevant string in all possible config files. For example:
$ grep_bash PATH
As a side note, not having /sbin and /usr/sbin in a normal user's PATH is standard practice for most distributions. There is no reason for a normal user to have these directories in their path. I just checked on a Debian, and Ubuntu Server and a SuSe machine and only the Ubuntu seems to add /sbin to a normal user's path and it does so in /etc/environment. The other two only add it if the user is root.
