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 in shells? source is there for readability and self-documentation, exists because it is quick to type The commands are identical The commands are identical Perl has long and short versions of many of its control variables for the same reason
Source vs . why different behaviour? - Unix Linux Stack Exchange source is a shell keyword that is supposed to be used like this: sourcefile where file contains valid shell commands These shell commands will be executed in the current shell as if typed from the command line
How to export variables from a file? - Unix Linux Stack Exchange is the standard and Bourne name for the source command so I prefer it for portability (source comes from csh and is now available in most modern Bourne-like shells including bash though (sometimes with a slightly different behaviour)) In POSIX shells, you can also use set -o allexport tmp txt set +o allexport
If bash lt;file gt; works, why is source lt;file gt; throwing an error? It works when you execute it but fails when you source it because aliases are not available in non-interactive shells (the type of shell that runs shell scripts) As explained in the bash manual : Aliases are not expanded when the shell is not interactive, unless the expand_aliases shell option is set using shopt (see The Shopt Builtin )
shell - What is the difference between sourcing (. or source) and . . . $ file # that exact same file as above, now it is sourced $ source file # an equivalent (but longer) command Of course, if the directory is not set in the path (not starting dot), some searching will be involved to find the specific file to be sourced In bash:
Disable fib_validate_source - Unix Linux Stack Exchange Is there a way to disable source validation? The solution suggested in the question I linked is to change the source IP of these packets; that's not something I control I tried doing sudo sysctl -w net ipv4 <interface> all rp_filter=0 for each of: the incoming tun0 interface; the expect outgoing bm interface; all; default