Mailinglist Archive: opensuse (3996 mails)
| < Previous | Next > |
Re: [SLE] SuSE or KDE?
- From: Sid Boyce <sboyce@xxxxxxxxxxxxxxxx>
- Date: Sat, 18 Sep 2004 00:33:09 +0100
- Message-id: <414B7435.2000900@xxxxxxxxxxxxxxxx>
Carlos E. R. wrote:
export PATH=$PATH:/usr/local/bin:/usr/local/sbin:</whatever_path>
The new paths will be picked up on boot up, but can be activated immediately by ". ~/.bashrc" or "source ~/.bashrc" as root.
Each distro does its own thing, whether right or wrong, the differences once learned are minor and easy to handle. There are certain things I do with Mandrake to make it pretty much the same to work with as SuSE, mainly with aliases in ~/.bashrc.
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
=====LINUX ONLY USED HERE=====
The 2004-09-16 at 09:55 -0700, Bahram Alinezhad wrote:<STUFF DELETED>
If "echo $PATH" is done as root, /usr/local/bin is not in the path for root, that's SuSE's way of doing Linux. In order to have any other paths available, edit /root/.bashrc and add a line5- When I login to a user other than root, and use "su
root" or open a root shell in order to run some
commands located in /usr/local/bin, I get the error of
"command not found"! I have to type the full path! A
problem that there is somehow in redhat but not so bad
as this.
export PATH=$PATH:/usr/local/bin:/usr/local/sbin:</whatever_path>
The new paths will be picked up on boot up, but can be activated immediately by ". ~/.bashrc" or "source ~/.bashrc" as root.
Each distro does its own thing, whether right or wrong, the differences once learned are minor and easy to handle. There are certain things I do with Mandrake to make it pretty much the same to work with as SuSE, mainly with aliases in ~/.bashrc.
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
=====LINUX ONLY USED HERE=====
| < Previous | Next > |