Results 1 to 3 of 3
I am puzzling over some terminolgy I hear:
"dot in [some shell script name]"
or
"source in [something]"
or what I suspect is similar (from a kshsrc file)
"# Source ...
- 11-10-2010 #1Just Joined!
- Join Date
- Nov 2010
- Posts
- 2
[SOLVED] Linux Jargon/Terminology
I am puzzling over some terminolgy I hear:
"dot in [some shell script name]"
or
"source in [something]"
or what I suspect is similar (from a kshsrc file)
"# Source the standard Developers profile
. /opt/local/etc/profile "
I have a suspicion what they mean, but not sure of the subtleties of the terms.
Can someone please elucidate?
- 11-11-2010 #2forum.guy
- Join Date
- May 2004
- Location
- arch linux
- Posts
- 18,095
Hello and welcome to the forums!
You can find lots of Linux terms with definitions here:
Linux Dictionary
...or download the pdf file for the same Linux Dictionary here:
http://tldp.org/LDP/Linux-Dictionary...Dictionary.pdfoz
→ new members/users: read this first | new member faq
→ no private messages requesting computer support - post them on the forums!
→ please use the "report post" button to alert our forum admins to problematic posts rather than responding to them yourself.
- 11-11-2010 #3Just Joined!
- Join Date
- Nov 2010
- Posts
- 2
Found answer
I did not find an answer in in that document, but just stumbled upon a good explanation:
"If, within the script, you export the environment variable it is effective within any programs called by the script. Note that it is not effective within the program that called the script.
If the program that calls the script does so by inclusion instead of calling, any environment changes in the script are effective within the calling program. Such inclusion can be done with the dot command or the source command. Examples:
. $HOME/myscript.sh
source $HOME/myscript.sh "
(find the source web page by Googling this (in quotes) "Such inclusion can be done with the dot command or the source command" )
That helped alot


