4 ms·
You would never need to know the difference - because you can always read the man page.
by nodata 14y ago
You would never need to know the difference - because you can always read the man page.
- azylman 14y agoJust because I "can" do something doesn't mean I "want" to do something or that it's the best way to use my time. That's like saying that we don't need expressive function names in code because we can just refer to the documentation.
- slyall 14y ago$ man bash | wc 5375 41026 312785 "From the Earth to the Moon" by Jules Verne has 39,985 words
- reidrac 14y agoYou don't need to read the whole manual. It's hard when you're looking for something very specific, but in this case it's just the FILES section, so I'll try man bash and then /^FILES. It's like saying /etc/services has 11033 lines in it. Well, use grep or search in the document.
- moe 14y agoWhich man-page exactly? The fun part about .bashrc, .bash_profile, .profile, /etc/bash*, /etc/profile etc. is that their semantics vary wildly between linux-distros. Not even Ubuntu and Debian agree here. You never quite know where, when and if .bashrc is sourced by the distro-templates. A .bash_profile that unconditionally sources .bashrc will work fine on one distro, on the next you will see it run multiple times, on yet another you run into an infinite recursion. His approach is the correct one and you'll find a similar script in just about any sizable, heterogenous deployment.
- nodata 14y agoman bash The INVOCATION part. You find this part by searching for the word "profile".