|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
home directory in search path
Post 6718 by LivinFree on Monday 10th of September 2001 11:42:11 PM
09-11-2001
A very common thing to do is create your own bin directory in your $HOME, so you can keep files seperate. I do this on nearly all of my account, both regular and root.
mkdir $HOME/bin
chmod 700 $HOME/bin
PATH=${PATH}:/$HOME/bin
Then add that PATH addition to your .profile (or .bash_profile if needed) to make it work every time you log in. The reason I suggest the added bin directory is to keep your scripts / programs you want to use regularly seperate from test scripts, and other file that may interfere.
Besides, it's just plain cool to have your own bin directory
mkdir $HOME/bin
chmod 700 $HOME/bin
PATH=${PATH}:/$HOME/bin
Then add that PATH addition to your .profile (or .bash_profile if needed) to make it work every time you log in. The reason I suggest the added bin directory is to keep your scripts / programs you want to use regularly seperate from test scripts, and other file that may interfere.
Besides, it's just plain cool to have your own bin directory
|
|
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
By default FIND command searches for matching files in all the subdirectories within the specified path.
Is there a way to restrict FIND command's search path to only the specified directory and NOT TO scan its subdirectories.
Any help would be more than appreciated.
Thanks and Regards (2 Replies)
Discussion started by: super_duper_guy
2 Replies
2. Solaris
Hi,
I've created solaris user which has both FTP and SFTP Access. Using the "ftpaccess" configuration file options "guest-root" and "restricted-uid", i can restrict the user to a specific directory. But I'm unable to restrict the user when the user is logged in using SFTP.
The aim is to... (1 Reply)
Discussion started by: sftpuser
1 Replies
3. Shell Programming and Scripting
Hi all,
This is probably a basic question. I had installed a stand-alone library called szip in my home directory, as I don't have the necessary root permission.
I tried to set an environment for both include and lib files in my .cshrc script as
setenv /home/szip/lib
setenv... (3 Replies)
Discussion started by: alamcheril
3 Replies
4. Shell Programming and Scripting
Hi,
I have a file abcd.txt which has contents in the form of full path file names i.e.
$home> vi abcd.txt
/a/b/c/r1.txt
/q/w/e/r2.txt
/z/x/c/r3.txt
Now I want to retrieve only the directory path name for each row
i.e
/a/b/c/
/q/w/e/
How to get the same through shell script?... (7 Replies)
Discussion started by: royzlife
7 Replies
5. Shell Programming and Scripting
Hello All,
Here is what I am trying to do and maybe you guys can point me in the right direction. I have a file that contains the following string(s):
WARNING: </d1/test/program1> did not find item1
WARNING: </d1/test/program1> item1 does not exist
WARNING: </d1/test/program2> item1 failed... (1 Reply)
Discussion started by: maxshop
1 Replies
6. Shell Programming and Scripting
I have many views in my Linux home dir under different folders mentioned below.
Home
1. CCVIEWS
2. views
3. Development
4. testproject
:
:
etc.
Now i want to list all the clearcase views in my linux dir in below format to work on other script.
1) user_test_Work1.vws
... (4 Replies)
Discussion started by: saku
4 Replies
7. Solaris
Hello,
I've just started using a Solaris machine with SunOS 5.10.
After the machine is turned on, I open a Console window and at the prompt, if I execute a pwd command, it tells me I'm at my home directory (someone configured "myuser" as default user after init).
... (2 Replies)
Discussion started by: egyassun
2 Replies
8. UNIX for Beginners Questions & Answers
Hello,
I am creating a file with all the source folders included in my git branch, when i grep for the used source, i found source included as relative path instead of absolute path, how can convert relative path to absolute path without changing directory to that folder and using readlink -f ? ... (4 Replies)
Discussion started by: Sekhar419
4 Replies
9. UNIX for Beginners Questions & Answers
What is the difference ../directory path and ./directory path in ksh? (1 Reply)
Discussion started by: TestKing
1 Replies
LEARN ABOUT OPENDARWIN
su
SU(1) BSD General Commands Manual SU(1) NAME
su -- substitute user identity SYNOPSIS
su [-flm] [login] [-c shell arguments] DESCRIPTION
su requests the password for login and switches to that user and group ID after obtaining proper authentication. A shell is then executed, and any additional shell arguments after the login name are passed to the shell. If su is executed by root, no password is requested and a shell with the appropriate user ID is executed. The options are as follows: -c Invoke the following command in a subshell as the specified user. -f If the invoked shell is csh(1), this option prevents it from reading the ``.cshrc'' file. -l Simulate a full login. The environment is discarded except for HOME, SHELL, PATH, TERM, and USER. HOME and SHELL are modified as above. USER is set to the target login. PATH is set to ``/bin:/usr/bin''. TERM is imported from your current environment. The invoked shell is the target login's, and su will change directory to the target login's home directory. This option is identical to just passing "-", as in "su -". -m Leave the environment unmodified. The invoked shell is your login shell, and no directory changes are made. As a security precau- tion, if the target user's shell is a non-standard shell (as defined by getusershell(3)) and the caller's real uid is non-zero, su will fail. The -l and -m options are mutually exclusive; the last one specified overrides any previous ones. Only users in group ``wheel'' (normally gid 0) or group ``admin'' (normally gid 20) can su to ``root''. By default (unless the prompt is reset by a startup file) the super-user prompt is set to ``#'' to remind one of its awesome power. SEE ALSO
csh(1), login(1), sh(1), skey(1), kinit(1), kerberos(1), passwd(5), group(5), environ(7) ENVIRONMENT
Environment variables used by su : HOME Default home directory of real user ID unless modified as specified above. PATH Default search path of real user ID unless modified as specified above. TERM Provides terminal type which may be retained for the substituted user ID. USER The user ID is always the effective ID (the target user ID) after an su unless the user ID is 0 (root). HISTORY
A su command appeared in Version 7 AT&T UNIX. BSD
April 18, 1994 BSD