|
- What is the difference between . . and source?
The source command is not required by POSIX and therefore is less portable than the shorter Share
- 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
- 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
- What is the difference between ~ . profile and ~ . bash_profile?
bash will try to source bash_profile first, but if that doesn't exist, it will source profile 1 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:
- firewalld ignoring source - Unix Linux Stack Exchange
I have a CentOS8 box, and a default config of firewalld: firewall-cmd --list-all public (active) target: default icmp-block-inversion: no interfaces: ens192 sources: services: dhcpv6-cli
- Source shell script automatically in terminal
I'm not entirely sure how this works with your file manager but, presumably, "open in terminal" is something you use on directories and it just opens a terminal window at that location If so, it should be enough to source your script from the initialization file for interactive, non-login shells
|
|
|