I enjoyed the video. The only issue with all this quick tutorial is that maybe pointing out the reason why we write script can help people understand why they are so important. All it needs to be said is automation for instance at boot.
fun fact: adding '.sh' in making a shell script from the terminal is entirely optional. Even though your file doesn't end in '.sh', as long as your file has the shebang in it, give it 'chmod +x' permissions, and you can still run it with './'.
I agree and you are right on point. In Linux extensions don't matter. It's a convention to help Linux admins or power users understand what that file is supposed do to. This is not windows lol but LINUX
fun fact: the shebang is only needed in cases of uncertainty (like a file that should be shared) or when not using the same shell; any file run with './' will attempt to run in the same environment as where it was run (typically a shell).
![[LIVE] : ONE ลุมพินี 86 | คู่เอก "คมเพชร vs ชาติพยัคฆ์"](http://i.ytimg.com/vi/m3q_dRYDuU8/mqdefault.jpg)
I enjoyed the video. The only issue with all this quick tutorial is that maybe pointing out the reason why we write script can help people understand why they are so important. All it needs to be said is automation for instance at boot.
fun fact: adding '.sh' in making a shell script from the terminal is entirely optional. Even though your file doesn't end in '.sh', as long as your file has the shebang in it, give it 'chmod +x' permissions, and you can still run it with './'.
I agree and you are right on point. In Linux extensions don't matter. It's a convention to help Linux admins or power users understand what that file is supposed do to. This is not windows lol but LINUX
fun fact: the shebang is only needed in cases of uncertainty (like a file that should be shared) or when not using the same shell; any file run with './' will attempt to run in the same environment as where it was run (typically a shell).
intro song is awesome
did you hear it somewhere else ???
@@paperclips1306i did not