Your SHEBANG made me LOL, I remember learning about bang (!), splat (*) in UNIX ages ago. They said they came about from people telling code to each other in a noisy room or with distance between coders--was easier than saying "Exclamation point." Huh? "BANG!"
THANK YOUUUUU. This was exactly I was looking for. I was trying to deploy resources in azure using Azure CLI and I used a bash script to automate these tasks. Commands with spaces, such as az group create --name and yadayada I was struggling on it. I can't thank you enough for this!!!!
Hi Shawn, I am so glad that there is a series on bash scripting on your channel! It is a corner-stone skill for would-be Linux sys-admins and is a very cool skill to have under your belt. I will watch the remaining episodes in this playlist
Sweet, thank you! As I think of more interesting things to do with BASH, I will add videos. But it contains most of what I do with BASH on a daily basis. :)
Super late to the game on this but working through the playlist for Bash to do assignment 2 - so far I think I've started to see some snags (an obvious typo) but these videos are amazing. Love the content and the way you help instruct and just communicate with the audience is a pleasant change. Looking forward to the rest of the videos.
Thanks! And there's a bit of irony that I'm responding to a comment about communication NINE DAYS LATER. I know it's a "good problem" to have lots of communication, but I worry about when I can't keep up. Thanks for being awesome. :)
@8:30 formatting is different because output of "date" command is pre processed by bash before echo is executed. White spaces are removed and each string is passed as a separate parameter to a main function in echo program. If you want to preserve spaces use double quotes (call echo "`date`" or echo "$(date)"). There is a useful lint tool "shellcheck" that can show you basic issues inside you shell script.
For several years now, most of my programming has been in bash. I don't love it, but as Bjarne (C++) Stroustrup noted, "there are only two kinds of languages". :-) One bit of advice to those getting started: smart programmers overcome language limitations, wise programmers avoid them. Bash scripts are either very short, or very bad. If your code keeps growing, split it into single-purpose reusable tools, reconsider your larger goals, or switch to another language.
This is really good advice. But I have to admit, I have done some SHAMEFUL things using multiple languages... For example: Writing a BASH interface that calls a CLI PHP script to pull values out of an API which I then (using BASH) send that value to a Python script to do complex calculations, and return the value back to the BASH script. I have a bad habit of learning JUST enough of a language to make it do what I need, and not one command more. LOL (I have gotten better at just using Python for most of the heavy lifting I can't effectively do with BASH -- but PHP was my first non-BASH language, so it's hard to not fall back to things I'm familiar with)
@@shawnp0wers I have used Nano since before it was Nano, when it was Pico (PIne COmposer ). I am no expert on it but it does what I need to do. Nano is what I use in my videos.
Ok, so you're one of the few people who could actually have this conversation, lol. Michigan Tech had both Pine and Elm email clients available, but when I was there, Pine wasn't installed on all clients, whereas Elm was. And since Elm used vi as the editor, that's where I first started using it. One of my close friends still uses Mutt as his only email client. He's much cooler than me. :)
![Eminem - Somebody Save Me (feat. Jelly Roll) [Official Music Video]](http://i.ytimg.com/vi/Vwa0HenQMi4/mqdefault.jpg)
Go Shawn, Go Shawn - I'm in - let's do this.
w00t!! 😃
Your SHEBANG made me LOL, I remember learning about bang (!), splat (*) in UNIX ages ago. They said they came about from people telling code to each other in a noisy room or with distance between coders--was easier than saying "Exclamation point." Huh? "BANG!"
Ha! I didn’t know that, how cool. :D
Over a decade that I'm enjoying your tuts! You're awesome! 👊🏻❤️
Thanks!!! I’m really enjoying making videos again. :)
THANK YOUUUUU.
This was exactly I was looking for. I was trying to deploy resources in azure using Azure CLI and I used a bash script to automate these tasks. Commands with spaces, such as az group create --name and yadayada I was struggling on it.
I can't thank you enough for this!!!!
I'm so glad it was helpful!!
Hi Shawn, I am so glad that there is a series on bash scripting on your channel! It is a corner-stone skill for would-be Linux sys-admins and is a very cool skill to have under your belt. I will watch the remaining episodes in this playlist
Sweet, thank you! As I think of more interesting things to do with BASH, I will add videos. But it contains most of what I do with BASH on a daily basis. :)
@@shawnp0wers it would be awesome Shawn
This was a great video! Glad I found this channel. Linux has been a bit overwhelming to me coming from CCNA studies.
Thank you, and welcome!
Super late to the game on this but working through the playlist for Bash to do assignment 2 - so far I think I've started to see some snags (an obvious typo) but these videos are amazing. Love the content and the way you help instruct and just communicate with the audience is a pleasant change. Looking forward to the rest of the videos.
Thanks! And there's a bit of irony that I'm responding to a comment about communication NINE DAYS LATER.
I know it's a "good problem" to have lots of communication, but I worry about when I can't keep up. Thanks for being awesome. :)
@8:30 formatting is different because output of "date" command is pre processed by bash before echo is executed. White spaces are removed and each string is passed as a separate parameter to a main function in echo program. If you want to preserve spaces use double quotes (call echo "`date`" or echo "$(date)").
There is a useful lint tool "shellcheck" that can show you basic issues inside you shell script.
Great info, thanks!
For several years now, most of my programming has been in bash. I don't love it, but as Bjarne (C++) Stroustrup noted, "there are only two kinds of languages". :-)
One bit of advice to those getting started: smart programmers overcome language limitations, wise programmers avoid them. Bash scripts are either very short, or very bad. If your code keeps growing, split it into single-purpose reusable tools, reconsider your larger goals, or switch to another language.
This is really good advice. But I have to admit, I have done some SHAMEFUL things using multiple languages... For example:
Writing a BASH interface that calls a CLI PHP script to pull values out of an API which I then (using BASH) send that value to a Python script to do complex calculations, and return the value back to the BASH script. I have a bad habit of learning JUST enough of a language to make it do what I need, and not one command more. LOL
(I have gotten better at just using Python for most of the heavy lifting I can't effectively do with BASH -- but PHP was my first non-BASH language, so it's hard to not fall back to things I'm familiar with)
This series is gonna be GREAT can't wait. 😊 i love this. thanka alot.
Thank YOU!
Thanks for your video! I just found your channel from Chuck's podcast.
Thank you, and welcome! :)
awesome 👍🏻, thank you for the video 🙏🏻
Thank YOU for watching!
Dammmm...vi for 20 years??? I'm only learning it now! 🙂
Awesome video, thank you
Waiting....shawn please also make a tutorial how to pass expect output as parameters directly to bash script for further processing
I have an outline of about a dozen videos - one is on I/O, I’ll be sure to include expect. Thank you. :)
Good Series. Just the colour of your terminal script is hard to see.
Nice bracelet! Thank you for useful content. Slava Ukraini! 🇺🇦
I was starting to feel like I was the only one that used nano.
lol -- it's so silly that I DON'T use nano, it's just decades of muscle memory. Nano is awesome. :)
@@shawnp0wers I have used Nano since before it was Nano, when it was Pico (PIne COmposer ). I am no expert on it but it does what I need to do. Nano is what I use in my videos.
Ok, so you're one of the few people who could actually have this conversation, lol.
Michigan Tech had both Pine and Elm email clients available, but when I was there, Pine wasn't installed on all clients, whereas Elm was. And since Elm used vi as the editor, that's where I first started using it.
One of my close friends still uses Mutt as his only email client. He's much cooler than me. :)