I’ve watched a lot of technical training videos with 20 years in the industry. You do a great job explaining things included with real live demos! Thank you for sharing what you do! Helping others learn too. 🙌🏼
I shortened that alias and implemented it into all my servers immediately (in my home) because it is simple and brilliant. I know them anyway because they are static, but I love the simplicity of it.
Nice bash intro. Half the battle when writing bash is knowing which command and arguments (flags) to pass to it; # hostname -I Returns the system primary IP address. Type hostname --help for details. Of course, I understand the exercise was to demonstrate pipping capabilities of bash. But the less pipping the faster your script will run. Also, this is much better than without the curly brackets. # echo "${STRING}" Excellent job.
You didn’t need the `echo $(`…`)` at the end, you just needed to escape the `$` so it doesn’t get expanded in the string: `alias ipaddress="ifconfig | grep broadcast | awk '{print \$2}'"`.
Fortunately for the civilized jq users among us, there is now “ip -json addr show | jq …” No more ifconfig (I guess? Honestly I never got the ip tools memo, so this has been very confusing for me)
Thanks for sharing. A minor correction, re 2:17 - the .sh extension is not actually necessary. And just a note re 12:55, while some folks do call those "curly brackets", a less-confusing name for them would be "braces" -- { and } -- whereas "brackets" (or "square brackets") would be [ and ].
Great video. Exactly what a bash nab (me) needs to start up, see how to make a basic one then build on it, then add more and more and bit of polish ... brilliant.
@@charlesmagno28I got the same situation. For example - it really helps handle server apps, particularly deploy updates (or configs, patches), do system tasks
Cool video- There is a lot of content like this on youtube but your style makes this easy to ingest for beginners. Couple if things though- You don't have to have .sh at the end of it and it you're going to run it with `bash ` you don't need the shebang either. Also, why did you have to fuzz the ifconfig command? I hope you continue this series- bash offers some much more advanced capabilities.
@@dawidsadzak8137 True. I've seen a few. But it was a nice coincidence to watch this video today. I know how the world works, still, i think it's a great short video about things you can do with bash scripting.
I love your videos, can't thank you enough for what you do out here, and thanks for taking the time to "give us" this knowledge. Keep. Up the good work!
In the case of shebang, it's better to use `/usr/bin/env bash` instead of the exact shell location so it can be ram on different machines without changing a single line.
thats neat and smart tip, if i was to write malware on my linux machine and wanted to transfer to a remote machine somewhere else that might be using different shell. It could in cases like that then
It's fascinating that Mr. Kinzie explains that you need a "Ubuntu or Kali Linux system, really any Linux system" and then proceeds to create and run bash scripts on a macOS machine without mentioning that macOS does bash as well.
@@Wegottohustlehard VSCode is a better editor IMHO but may be more complicated and sometimes simpler is better. Not sure why you're having trouble getting VSCode to work with his examples. I did just try the first script he typed in using VSCode instead of nano, and it works just fine.
Thanks a lot, this is very well explained. It is the best explanation I have come across unlike many scripting/programming videos where the narrator often spends a lot of time even hours talking to themselves in vain because they are so badly explained.
Intermediate Tip: Use "man bash" to learn the semantic differences of: "&" (ampersand), "&&" (double ampersand), "|" (bar), and ";" (semi-colon). Most of my aliased commands use these punctuations, with one being "firefox & discord &" and another being "git fetch ; git status ;". GL, HF
Bash was my entry point into coding! I just wanted to save time on repetitive tasks and chill more while at work; upside was that I learned I could annoy my supervisor by being such a TryHard.
@@justinc4782 it depends where you want to go, to have a cushiony job with few working hours, then just quietly do your part. If you want to be more successful and have a job that recognizes this effort, then ask for more work.
Good habits put in a "header" with the date, your name and purpose of the script. Also keep upper case vars for env vars. ^^^ being kind to your future self
From man bash: For almost every purpose, aliases are superseded by shell functions. So no, aliases are not cool (apart maybe for just one command, but it gets crazy when you want to put more than one command with quotes; and also they can't handle arguments). Functions are cool!
I was going to comment to bash you for using nano but then I realized that I started doing anything on the *nix command line using nano instead of vi so I can't really say stuff; but vi is the best thing to learn.
Remember: **Syntax is your wand**, and every bug is a riddle waiting to be solved. May your journey be filled with wonder and your code compile without tantrums.
@Learn Linux im starting to get the idea actually , my issue is the way i learn , unlike most people i need the bigger picture first , then the break down , not the other way around , sooo ya lol
Actually to find out the shell you are currently using you need to execute which $SHELL since most of the time you want your current shell to interpret your script
hello . 0:40 It's get my attention that black blanket on the wall. The blanket surface is like the equipment on the voice lab to eliminate external sound effect. Am I right？
I wouldn’t recommend using aliases like that. Make them little scripts. Aliases are part of bash expansion. Using grep with your alias… womp womp. Gotta single tick it. Aliases for obscure references. Scripts for other stuff, not piped commands.
a bit confused @8:53 with "read name". If name isn't defined as a variable yet, how is it reading it as the only reference to "name" previously is in the string?
alright, this is more like it. let's be real, a lot of n00bs need to be learning stuff like this and not be so concerned about being the next best h4x0r. Good job Null Byte. /usr/share/thumbs.up
Here’s what I’d like, Press the on button, boots to the login in screen. Computer says: who’s there? I answer with my name, Booting finishes, logged in.
boot it into a tty by configuring grub. make your terminal run your little program when it loads use espeak to say "whos there" use the read command to ask for your name and get input, if, else, string contains to check for proper input, then boot into your graphical interface
I've been searching for a tutorial to make my terminal look like this, old green monitor, for a long time. Do you have any tutorial for that? I'm a complete newbie here in Brazil, learning Linux and Terminal prior to learn coding itself. Thanks for the video.
If you use the alias command in a live terminal, the alias is stored for that session only. Once you exit the terminal, the alias is lost. To save and store your own aliases, you need to edit your bashrc file, which is a configuration file that stores the settings for your shell. There are two copies of this file, one in /etc/bashrc that holds system-wide configuration (any user on the system will inherit these configurations), and one in /home/$USER/.bashrc that affects your user profile only. In most cases, you will want to edit the version of the file in /home/$USER/bashrc. Open the file with nano or vim and add your alias command to the file. You could add your command pretty much anywhere, but it's probably easiest to just add it to the end of the file. Once you save the file, the alias command you added will execute every time you open a shell. You can also edit the .bashrc file to change environment variables such as your $PATH.
This is my kind of guy. His eyes tell me he's wasted no more than 3 hours sleeping since birth.
Pissed my pants lol
he's an EXPERT at what he does, and i like it.
@Badger anti R? Which programming language is that?
@@rikkertkuklinski4410 R is the language
@@aminechei8509 just be carefull. Dont piss the guy off. He might hack you while you're taking a dump and staring into your phone ...
Dude where have you been? I was about to call 911 and report you as missing. Glad you are back.
Oh wow false alarm for 911
Good luck at trials bro
@@KangJangkrik It was a joke.
@@kingseekerbackup3085 I know
The grim reaper pulled him into a dimension between space and time, to see who would blink first in exchange for his soul. Cody clearly won 👏👏👏
@@sprBEAST211 lmao
I’ve watched a lot of technical training videos with 20 years in the industry.
You do a great job explaining things included with real live demos! Thank you for sharing what you do! Helping others learn too. 🙌🏼
I shortened that alias and implemented it into all my servers immediately (in my home) because it is simple and brilliant. I know them anyway because they are static, but I love the simplicity of it.
Nice bash intro.
Half the battle when writing bash is knowing which command and arguments (flags) to pass to it;
# hostname -I
Returns the system primary IP address. Type hostname --help for details.
Of course, I understand the exercise was to demonstrate pipping capabilities of bash. But the less pipping the faster your script will run.
Also, this is much better than without the curly brackets.
# echo "${STRING}"
Excellent job.
You didn’t need the `echo $(`…`)` at the end, you just needed to escape the `$` so it doesn’t get expanded in the string: `alias ipaddress="ifconfig | grep broadcast | awk '{print \$2}'"`.
Thanks for this tip. It is more short and useful.
Phew I’m glad I’m not the only one that caught this. 😅😅
Fortunately for the civilized jq users among us, there is now “ip -json addr show | jq …”
No more ifconfig (I guess? Honestly I never got the ip tools memo, so this has been very confusing for me)
I don't understand the concept of 'escaping'.. why did it work without escaping before aliasing?
Thanks for sharing.
A minor correction, re 2:17 - the .sh extension is not actually necessary.
And just a note re 12:55, while some folks do call those "curly brackets", a less-confusing name for them would be "braces" -- { and } -- whereas "brackets" (or "square brackets") would be [ and ].
Great video. Exactly what a bash nab (me) needs to start up, see how to make a basic one then build on it, then add more and more and bit of polish ... brilliant.
Writing bash scripts has saved me thousands of hours over the years. Thank you for the video, this is incredibly useful.
any real world sample you can share? thanks
@@charlesmagno28I got the same situation. For example - it really helps handle server apps, particularly deploy updates (or configs, patches), do system tasks
“Oops this isn’t python” hahah
Studying for my Linux+, this is gold
Just what I needed. I was literally just thinking about this! Thumbs up
Same bro, thought the algorithms recent update was to read my mind xD
This guy explains it better than my professor did last week
Are you taking computer science? Or IT
Lmaoo thx I will never go to university
I feel thee!!
Mine tooooo😅
@@cyberrock9018 which are you in?
Cool video- There is a lot of content like this on youtube but your style makes this easy to ingest for beginners. Couple if things though- You don't have to have .sh at the end of it and it you're going to run it with `bash ` you don't need the shebang either. Also, why did you have to fuzz the ifconfig command?
I hope you continue this series- bash offers some much more advanced capabilities.
just getting started with Linux Mint on a VM. This video just taught me so much. thank you :)
You guys are reading my mind! This is EXACTLY the video I was looking for. This video is gold. More like this.
this is what i was gonna type in comment .....lol
@@sachinmaurya3259 I was going to type this too haha
@@dawidsadzak8137 sad u.u but great they made this video
@@dawidsadzak8137Way to devalue for the video for others my guy. If you don't get excited about this, you're in the wrong place.
@@dawidsadzak8137 True. I've seen a few. But it was a nice coincidence to watch this video today. I know how the world works, still, i think it's a great short video about things you can do with bash scripting.
I love your videos, can't thank you enough for what you do out here, and thanks for taking the time to "give us" this knowledge. Keep. Up the good work!
Thank you for showing the error you ran into and the work arounds in the video.
In the case of shebang, it's better to use `/usr/bin/env bash` instead of the exact shell location so it can be ram on different machines without changing a single line.
thank you :D
thats neat and smart tip, if i was to write malware on my linux machine and wanted to transfer to a remote machine somewhere else that might be using different shell. It could in cases like that then
My dad had me watch this video for a class I'm going to take. This looks interesting. I like coding.
It's fascinating that Mr. Kinzie explains that you need a "Ubuntu or Kali Linux system, really any Linux system" and then proceeds to create and run bash scripts on a macOS machine without mentioning that macOS does bash as well.
hey,,can you plz tell what is he using to type that script..cause if iuse vscode i amd not the sam eoutput.thank you!
@@Wegottohustlehard VSCode is a better editor IMHO but may be more complicated and sometimes simpler is better. Not sure why you're having trouble getting VSCode to work with his examples. I did just try the first script he typed in using VSCode instead of nano, and it works just fine.
thanks from France!! I can't wait for the next video about bash scripting ! :)
Me thinking about something*
One day later this dude who never blinks says: “hmm maybe i should make a video about that”
Thanks a lot, this is very well explained. It is the best explanation I have come across unlike many scripting/programming videos where the narrator often spends a lot of time even hours talking to themselves in vain because they are so badly explained.
Holy crap, I'm shocked I actually know almost all of this. I was genuinely nervous thinking I forgot a lot of this stuff.
Been trying to execute a bash file forever! First resource that actually helped!
Intermediate Tip: Use "man bash" to learn the semantic differences of: "&" (ampersand), "&&" (double ampersand), "|" (bar), and ";" (semi-colon).
Most of my aliased commands use these punctuations, with one being "firefox & discord &" and another being "git fetch ; git status ;".
GL, HF
I ENJOY your helpful interventions and your professional knowlege. TANK'S TOO MUCH.
I taught my self this exact thing for batch scripting, time to learn bash!
woooow, Vibrasphere - Sweet september music on the beging.... I am delighted... :)
1:16 "You can always pick up a Raspberry Pi" lol
The no-blink guy is back!
Lol
Amazing. Actually the advance commands was awesome
Bash was my entry point into coding!
I just wanted to save time on repetitive tasks and chill more while at work; upside was that I learned I could annoy my supervisor by being such a TryHard.
See but now they'll just give you more work if you prove yourself to be so efficient.
@@pianochannel100 yes if you ever make these kind of tweaks keep it to yourself and dont brag about it! :)
@@justinc4782 it depends where you want to go, to have a cushiony job with few working hours, then just quietly do your part.
If you want to be more successful and have a job that recognizes this effort, then ask for more work.
Any book recommendations to learn it more advanced?
Hey Kody, Thank you for your time and for your video
Amaizing ,i did this tutorial on termux(android) , works like magic! Thanx alot!
Nice trick using a subprocess in an alias! Thanks
He stares the information into my soul.
A lot of power to the user. Very useful.
Last task was awesome..thnx man
Nice~♡ dig the first ifconfig 🤣
I was looking exactly for this. Very nice content.
Good habits put in a "header" with the date, your name and purpose of the script.
Also keep upper case vars for env vars.
^^^ being kind to your future self
Bash scripting in the new Windows Terminal is very useful.
Great work man 😀 love your videos 👍
This is good stuff mate 🧠👍
This guy teach like a master.
sick video , the alias thing is really cool.
From man bash: For almost every purpose, aliases are superseded by shell functions.
So no, aliases are not cool (apart maybe for just one command, but it gets crazy when you want to put more than one command with quotes; and also they can't handle arguments). Functions are cool!
I was going to comment to bash you for using nano but then I realized that I started doing anything on the *nix command line using nano instead of vi so I can't really say stuff; but vi is the best thing to learn.
Awesome presentation! Thanks for the clarification.
Need more parts of it. 😍
"Paranoids...HOW DARE YOU!"
I love that sticker!
Please continue this bash series.
Thanks for the video
Please do make more videos for daily task automation
Thanks man, you helped me a lot. I appreciate your work.
I enjoy your support. your work is very benefit. TANK'S.
Hello , très interessant ce tuto de découverte . J'ai apprécié vos explications et vous dis un grand merci pour ce partage .
Argumentative bash script! hilarious :D
that cracked me up bro
Thanks dude, great description.
Remember: **Syntax is your wand**, and every bug is a riddle waiting to be solved. May your journey be filled with wonder and your code compile without tantrums.
Yay I'm early - I love your videos man ❤
Amazing video. Ty Nullbytes
Excellent video brother
You could also do ifconfig | awk '/broadcast/ {print $2}' which would let awk grep and parse column.
Yeah that's definitely WAAAAY ahead my level atm , i didn't understand a thing , hopefully within a year I would 🤣🤦🏻♂️
# hostname -I (uppercase i)
@Learn Linux im starting to get the idea actually , my issue is the way i learn , unlike most people i need the bigger picture first , then the break down , not the other way around , sooo ya lol
"Kody"? Jackie is the punk. Thanks for shooting and sharing such a great tutorial.
@Null Byte what that "Codes" book behind you?
Thank God you did not use "Hello World". I have created scripts before and I understand them but this was helpful for other variables I have not used.
Actually to find out the shell you are currently using you need to execute which $SHELL since most of the time you want your current shell to interpret your script
hello . 0:40 It's get my attention that black blanket on the wall. The blanket surface is like the equipment on the voice lab to eliminate external sound effect. Am I right？
Even though it's quite a simple quide, it's great!
Thank you!
I wouldn’t recommend using aliases like that. Make them little scripts. Aliases are part of bash expansion. Using grep with your alias… womp womp. Gotta single tick it. Aliases for obscure references. Scripts for other stuff, not piped commands.
Great timing 😁
Industrious intelligent geek. Awesome!
great video wish we could have more of
Thank you man for sharing this stuff
well this was fun and educational thanks!
Great video, but I gotta ask: are you using a hammer to type?
AMazing video sir for beginners.
I swear this is what I wanted
Great work Mate. Keep Staring
a bit confused @8:53 with "read name". If name isn't defined as a variable yet, how is it reading it as the only reference to "name" previously is in the string?
In bash, all variables are string, no need to declare, the default value being empty.
Really helpful video . Do you have any course on Udemy that I can purchase ?
Cool You really help me Well done!
Well made! Thank you 😁
alright, this is more like it. let's be real, a lot of n00bs need to be learning stuff like this and not be so concerned about being the next best h4x0r. Good job Null Byte. /usr/share/thumbs.up
?
?
?
This term, Linux, good timing❤️💋
Great video, thanks for sharing
4:56 How did you change that 2 into a 3?
7:07 Why not just use "whoami" by itself?
"belive"... Great video, as always, though.
To make a script portable say RHEL 6, 7, 8 and 9 you can use #!/usr/bin/env bash instead of #!/bin/bash
Can you make a script for making post on social media as planed per user and on given time
Here’s what I’d like,
Press the on button, boots to the login in screen.
Computer says: who’s there?
I answer with my name,
Booting finishes, logged in.
boot it into a tty by configuring grub.
make your terminal run your little program when it loads
use espeak to say "whos there"
use the read command to ask for your name and get input,
if, else, string contains to check for proper input, then boot into your graphical interface
@@justinc4782 OK cool thanks!
Do the aliases get saved themselves ? If not where to save them so that I can use them after I restart my system ?
Add them to your ~/.bashrc file
@@mattbeta thanks mate ! 😎
@@nikolaimakarov3034 good tip is to make an alias for editing your aliases
so aliases command would open up your .bashrc file :)
Your videos are perfect to learn
Was the $2 in your final script grabbed from a premade bash script? confused where that came from.
The man doesn’t blink😱
Drinking game: drink every time he says "go ahead."
I've been searching for a tutorial to make my terminal look like this, old green monitor, for a long time.
Do you have any tutorial for that?
I'm a complete newbie here in Brazil, learning Linux and Terminal prior to learn coding itself.
Thanks for the video.
Do all the scripts you make using "alias" are stored in bin/bash ? Thank you very much for the video , it fit like a puzzle piece for me .
If you use the alias command in a live terminal, the alias is stored for that session only. Once you exit the terminal, the alias is lost.
To save and store your own aliases, you need to edit your bashrc file, which is a configuration file that stores the settings for your shell. There are two copies of this file, one in /etc/bashrc that holds system-wide configuration (any user on the system will inherit these configurations), and one in /home/$USER/.bashrc that affects your user profile only. In most cases, you will want to edit the version of the file in /home/$USER/bashrc.
Open the file with nano or vim and add your alias command to the file. You could add your command pretty much anywhere, but it's probably easiest to just add it to the end of the file. Once you save the file, the alias command you added will execute every time you open a shell.
You can also edit the .bashrc file to change environment variables such as your $PATH.
@@jonathanverret6872 Thank you very much for taking your time to explain :D Haw an awsome weekend !
A .sh extension is not required for a shell script.