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)
Input Form:Deal with this potential dealer,buyer,seller,supplier,manufacturer,exporter,importer
(Any information to deal,buy, sell, quote for products or service)
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
bash - What is the difference between . profile and . bash_profile and . . . The profile dates back to the original Bourne shell known as sh Since the GNU shell bash is (depending on its options) a superset of the Bourne shell, both shells can use the same startup file That is, provided that only sh commands are put in profile For example, alias is a valid built-in command of bash but unknown to sh Therefore, if you had only a profile in your home directory and
When exactly do the scripts in etc profile. d get executed? In etc profile d I got a script called logchk sh which is meant to send an email to the admin email address via bin mail If someone logs in via ssh user@serveradress this script is properly executed and the email is sent
What do the scripts in etc profile. d do? - Unix Linux Stack Exchange It says that the etc profile file sets the environment variables at startup of the Bash shell The etc profile d directory contains other scripts that contain application-specific startup files, which are also executed at startup time by the shell
When should I use . bashrc and when . profile? [duplicate] profile is read by every login shell, xxxrc is read by every interactive shell after reading profile You need to decide yourself depending on what you like to add A good idea is to put everything that sets exported environment variables and thus propagates to sub shells into profile Things that are not propagated should be in bashrc or whatever your shell looks into This is e g alias
How to permanently set environmental variables You can add it to the file profile or your login shell profile file (located in your home directory) To change the environmental variable "permanently" you'll need to consider at least these situations:
Where should I source usr local etc profile from? . bash_profile or . . . Many distributions have a directory etc profile d, and put code in etc profile to source the files in etc profile d If your distribution does that, the best place for your machine-specific content would be a machine-specific file in etc profile d
Setting PATH vs. exporting PATH in ~ . bash_profile What's the difference and which is better to use when customizing my bash profile? Documentation on the export command is scarce, as it's a builtin cmd Excerpt from version 1 of my ~ bash_profil