copy and paste this google map to your website or blog!
Press copy button and paste into your blog or website.
(Please switch to 'HTML' mode when posting into your blog. Examples: WordPress Example, Blogger Example)
What is the difference between . . and source? [duplicate] When the script is done, any changes that it made to the environment are discarded script The above sources the script It is as if the commands had been typed in directly Any environment changes are kept source script This also sources the script The source command is not required by POSIX and therefore is less portable than the shorter
How can I make a script in etc init. d start at boot? I think I read something a while back about this, but I can't remember how it's done Essentially, I have a service in etc init d which I'd like to start automatically at boot time I remember i
Source vs . why different behaviour? - Unix Linux Stack Exchange source is a shell keyword that is supposed to be used like this: source file where file contains valid shell commands These shell commands will be executed in the current shell as if typed from the command line
What is the difference between ~ . profile and ~ . bash_profile? The original sh sourced profile on startup bash will try to source bash_profile first, but if that doesn't exist, it will source profile Note that if bash is started as sh (e g bin sh is a link to bin bash) or is started with the --posix flag, it tries to emulate sh, and only reads profile Footnotes: Actually, the first one of bash_profile, bash_login, profile See also: Bash
Use config file for my shell script - Unix Linux Stack Exchange 36 source is not secure as it will execute arbitrary code This may not be a concern for you, but if file permissions are incorrect, it may be possible for an attacker with filesystem access to execute code as a privileged user by injecting code into a config file loaded by an otherwise-secured script such as an init script
How do I apply the changes to the . zshrc file after editing it? You could source the new file, which would work for some changes, possibly including updating the PATH variable (depending on other lines) However, sourcing it would simply run zshrc again, and you might execute unexpected duplicate commands
How to export variables from a file? - Unix Linux Stack Exchange A dangerous one-liner that doesn't require source: export $(xargs <file) It can't handle comments, frequently used in environment files It can't handle values with whitespace, like in the question example It may unintentionally expand glob patterns into files if they match by any chance It's a bit dangerous because it passes the lines through bash expansion, but it has been useful to me when I