Oh man. Been waiting for this series for a long time and didn't realize it. I feel like I'm about to get super nerdy. It really feels like the difference between a linux user and a linux power user is the ability to write bash scripts to fully take command of the system.
You are a legend. Most guides have been too fast for me to truly take in and digest at the same time, but with you, I feel like I can follow your pace and understand the connections that you are making between individual topics and the knowledge you pile on through a single video never has me flustered and feeling dumb. Thanks a lot! I also dig your verbose, reassuring style.
Damn, I neglected this channel way to long and now that I binge watch this playlist I really regret it! This is maybe one of the most easy to understand Tutorial series of (Bash-) scripting I have ever seen. That's meaning something coming from me, since I'm not natively speaking English (so the man pages are quite hard to understand). Also it is hard for me to wrap my head around scripting and programming in general. So thank you very much for sharing this series for free. I and many other appreciate it very much!
The "command" trick in the end is actually pretty smart because it just tries to instantly tell if the executable exists and passes the result to the IF as a boolean so the IF itself resolves out on its own right on the spot. Pretty cool.
Hello Jay and thanks you for all of your instructional videos. I first started with UNIX in the 80's and had limited exposure to the OS. Around 1993, I grabbed an Idiots guide to Linux and a cd of SUSE Linux which was entirely Bash in xterm ( I don't think there were any of the flavors that had a GUI) and made an SMB server using Samba. I left cold turkey and did not pick up again until post-911 and this time I did get a GUI with Mint and for the next year I prostlized it as being the best distro. Fast fwd to this year and I've picked Linux back up and I will be staying this time as Linux is the best desktop I have ever used. I am not blessed with a good memory and I have to basically start from scratch, watch tutorials, and read. This is all just to say thank you! You are a very gifted instructor my friend. You teach in a way where you don't assume people know something about the subject and it is exactly what I need. And this is a great venue. There isn't some knuckhead who feels the need to compete with the instructor in the classrom, which I find very rude and a distraction. Just pure learning! So thank you for your sacrifice of time, expense, and all that goes with this channel. You certainly didn't have to devote you time to help us but I am glad for this measure of selflessness. I appreciate it and don't take it for granted. I'll be around for more!
Really appreciate this. Wanted to see if replacing 'command -v' with 'which' would work (and it does), and discovered that if you replace 'htop' with 'sl' you get something pretty cool. Thanks so much for this!!! Loving this series.
This is so well explained and such an invaluable resource. I barely understand Linux at all, and your videos are doing a thorough job of explaining everything without too much repetition, there's just the right amount to help key concepts stick. Thank you, definitely subscribing and saving to show others.
I like to refer the beginning line of a bash script as a hashbang because the hash sign comes first which makes it easier for me to remember! Good video!
Thank you for making this bash course! It's exactly what I needed. On the subject of man pages, there is also a tool you can install "tldr" (tealdeer is package name in arch) where it works similar to man pages but it will give you a brief description and a couple of color coded examples. An example would be running "tldr test" similar to "man test"
I've been experimenting along with your lessons. I found that "if which $command" works in place of "command -v $command". It might be a little less confusing for some.
12:46 I have done a few online Linux lessons over the years. One lesson I have adopted was to create a bin folder in your home directory to run scripts from and store scripts you create, to me this just makes sense. If you run a bad script in your ~bin no harm will come to your ~home directory.
This guy is great at explaining concepts. The only issue is, is that unless there is an exercise that is used continuously in everyday life, then the lesson will not stick.
this youtube videos are wonderful, well detailed and the fact that he takes his time to explain some things. I learnt some new commands and really understood what they were used for. I felt smart while watching your videos because I understood them easily. i am definitely subscribing
Great video very educational easy to follow along. i just made this script on arch linux. NOTE on Arch Linux based it's sudo pacman -Sy && pacman -S --noconfirm --needed
I think it's important to note in order to remind people that giving the choice of automated continuation of executions of commands on any script is most always better than just have it run everything with a "dry" -y for a lot of reasons, a flag variable could do the trick with a nested if i assume with the example given from this video at least. This matters most in something really significant so it's not like you will always need to have it (the choice) especially if you want to do something fast (even though having some material saved as templates is great and a good idea to keep around).
Depends what you're building for others to an extent most commands using sudo needs passwords especially fdisk. Though at the same time if you download a package you don't wanna keep sitting there typing your passwd especially when your compiling from source lol
If anybody wants to know, the if statement checks wether what goes after the "if" returns 0 as its exit code or something else. It is also possible to use the brackets by themselves and check their return code some other way. If only there was a convinient video on this channel explaining waht return codes are...
Do you have any tutorials on databases? Would love to see those cos you just drive home key concepts that immediately sticks. An excellent instructor that you are. Kudos!!!!
Plus the "command -v" command integrates all source for commands to be tested if they exist. In the first version of the test, using "/usr/bin/" excluded all commands from other directories like "usr/sbin/" etc
Why use 'command'? It has only two switches: -p and -v. The first just runs the argument as it would run alone by itself and the second equals to 'which'. So in this case here just use the 'which' and be done. Why 'command'?
Is there a practical difference between using 'which htop' and 'command -v htop'? It seems like in at least this case, it should produce the same output.
Hello, Just a note: With update and install on the same line: sudo apt update && sudo apt install -y $command this script would not run the apt install part because of a GPG WARNING in the apt update. Once the GPG WARNING was cleared up the script ran as advertised. It would run fine with commands on separate lines: sudo apt update sudo apt install -y $command Joe
I totally understand the -y after the install command, you don't want to answer [Y/n], but what about the password request? How do you avoid this? I'm missing something
Btw if you need to remember all these weird syntaxes bash has (very unintuitive to me) you can just use the manual page for bash: man bash It's a very long page, so you can search stuff typing "/stuff" and pressing "n" to search forward and "N" to find the word backwards.
9:45 Kind of how I like my conversations ... if you have to repeat yourself I am no longer interested in talking to you, I am not stupid and my ears work.
I guess I don't know why shell command language might not be considered a programming language. Its a Turing complete script interpreter. What condition is not met to be worthy of the title? EDIT: I do fully understand the value of drawing that line in the sand for the purposes of this tutorial, but looking into it I can see there is a larger internet argument going on and that is what confused me.
how can u able to take yes or no input as user and use as a condition in if else like mynum = " " if [ $mynum == yes ] then echo ... else .... [ $mynum == no ] ...
how come you specified a sudo operation in the script but you both didn't enter it in the script and either when you launched the script? how can that work? at 19:12
Anyone else having a problem with -f flag? The script written at 13:30 doesn't work for me, and the -f is not highlighted in the editor, using bash version 4.4.20(1).
trying to install on a Mac ... having issues with htop. I got a java issue but I downloaded it and it still did not work. I've used htop once in a controlled environment for my bioinformatics program. It worked there but. not on my laptop
In the code you have used sudo command for installing htop, but it did not prompted for password in my case it is asking for password why? how to automate this.
Just trying to introduce/teach someone to a SIMPLE use of if/else statements, will BLOWWW any novice brain to pieces with an additional and completely unnecessary complex stuff you introduced sir! No one doubts that you are knowledgeable, just you yourself need to learn how to get under the "skin" of any dumbfounded beginner, giving him/her a real chance to grasp and understand the given info, not make them to hate it for life !
I've only used Linux a bit, so this is probably a newb question. How does the script run the sudo install command without requiring you to enter a password to authenticate? Am I missing something?
The shell doesn't ask for password if you installed a package before in the same session using sudo. Once you close the terminal and reopen, it will ask for password again.
Had a problem on this one. Forgot the last command and so it didn't start. Went back and put it in, then ran it again expecting it to find it installed and run it. Instead it didn't find it, installed it again, and when it tried to run it it came up with an error. I had already run it the first time manually when it didn't run, and I ran it manually after it installed again, and came up with the error when trying to run again. Not sure why. I did verify it actually did install in the correct place, but for some reason the script seems to be looking somewhere else I guess? EDIT: Must remember to spell the directory usr not user... lol
![Linux SHELL SCRIPTING in ONE VIDEO For Beginners [ENGLISH] 2024 | MPrashant](http://i.ytimg.com/vi/FL7K2A2KH7g/mqdefault.jpg)
Thanks for all you do Jay. You are by far one of the best Linux teachers on and off youtube.
Oh man. Been waiting for this series for a long time and didn't realize it. I feel like I'm about to get super nerdy. It really feels like the difference between a linux user and a linux power user is the ability to write bash scripts to fully take command of the system.
You are a legend. Most guides have been too fast for me to truly take in and digest at the same time, but with you, I feel like I can follow your pace and understand the connections that you are making between individual topics and the knowledge you pile on through a single video never has me flustered and feeling dumb. Thanks a lot! I also dig your verbose, reassuring style.
Damn, I neglected this channel way to long and now that I binge watch this playlist I really regret it! This is maybe one of the most easy to understand Tutorial series of (Bash-) scripting I have ever seen. That's meaning something coming from me, since I'm not natively speaking English (so the man pages are quite hard to understand). Also it is hard for me to wrap my head around scripting and programming in general. So thank you very much for sharing this series for free. I and many other appreciate it very much!
Same situation here. Jay is really clear
I must say: I haven't had such a great instructor since the Professors that I had in high school. I'll never forget Learn Linux TV and you, Jay.
The "command" trick in the end is actually pretty smart because it just tries to instantly tell if the executable exists and passes the result to the IF as a boolean so the IF itself resolves out on its own right on the spot.
Pretty cool.
Really enjoying this particular series, and really needed to further brush up on BASH in general...keep up the great work, Jay!
Hello Jay and thanks you for all of your instructional videos. I first started with UNIX in the 80's and had limited exposure to the OS. Around 1993, I grabbed an Idiots guide to Linux and a cd of SUSE Linux which was entirely Bash in xterm ( I don't think there were any of the flavors that had a GUI) and made an SMB server using Samba. I left cold turkey and did not pick up again until post-911 and this time I did get a GUI with Mint and for the next year I prostlized it as being the best distro. Fast fwd to this year and I've picked Linux back up and I will be staying this time as Linux is the best desktop I have ever used. I am not blessed with a good memory and I have to basically start from scratch, watch tutorials, and read. This is all just to say thank you! You are a very gifted instructor my friend. You teach in a way where you don't assume people know something about the subject and it is exactly what I need. And this is a great venue. There isn't some knuckhead who feels the need to compete with the instructor in the classrom, which I find very rude and a distraction. Just pure learning! So thank you for your sacrifice of time, expense, and all that goes with this channel. You certainly didn't have to devote you time to help us but I am glad for this measure of selflessness. I appreciate it and don't take it for granted. I'll be around for more!
thanks i was watching cs50 but got overwhelmed by the bash script and this playlist is helping alot
Really appreciate this. Wanted to see if replacing 'command -v' with 'which' would work (and it does), and discovered that if you replace 'htop' with 'sl' you get something pretty cool. Thanks so much for this!!! Loving this series.
I guess it works also with the type command.
Yea you do get something pretty cool XD
This is so well explained and such an invaluable resource. I barely understand Linux at all, and your videos are doing a thorough job of explaining everything without too much repetition, there's just the right amount to help key concepts stick. Thank you, definitely subscribing and saving to show others.
These lessons help me so much with my automation projects! I'm so glad I found it on YT. Thank you!
I like to refer the beginning line of a bash script as a hashbang because the hash sign comes first which makes it easier for me to remember! Good video!
Such a simple way of explaining complex concepts. Hats off
Really good teaching. You make teaching look easy, and the student understanding every bit of it.
Thank you for making this bash course! It's exactly what I needed. On the subject of man pages, there is also a tool you can install "tldr" (tealdeer is package name in arch) where it works similar to man pages but it will give you a brief description and a couple of color coded examples. An example would be running "tldr test" similar to "man test"
Thanks! I didn't know about tldr.
Just installed it. Thx.
I've been experimenting along with your lessons. I found that "if which $command" works in place of "command -v $command". It might be a little less confusing for some.
came to say the same, I though why not to use which instead of command -v as they give the same output.
12:46 I have done a few online Linux lessons over the years. One lesson I have adopted was to create a bin folder in your home directory to run scripts from and store scripts you create, to me this just makes sense. If you run a bad script in your ~bin no harm will come to your ~home directory.
This guy is great at explaining concepts. The only issue is, is that unless there is an exercise that is used continuously in everyday life, then the lesson will not stick.
thanks bro learned a lot
this youtube videos are wonderful, well detailed and the fact that he takes his time to explain some things. I learnt some new commands and really understood what they were used for. I felt smart while watching your videos because I understood them easily. i am definitely subscribing
Great video very educational easy to follow along. i just made this script on arch linux. NOTE on Arch Linux based it's
sudo pacman -Sy && pacman -S --noconfirm --needed
Thanks!
I think it's important to note in order to remind people that giving the choice of automated continuation of executions of commands on any script is most always better than just have it run everything with a "dry" -y for a lot of reasons, a flag variable could do the trick with a nested if i assume with the example given from this video at least.
This matters most in something really significant so it's not like you will always need to have it (the choice) especially if you want to do something fast (even though having some material saved as templates is great and a good idea to keep around).
Depends what you're building for others to an extent most commands using sudo needs passwords especially fdisk. Though at the same time if you download a package you don't wanna keep sitting there typing your passwd especially when your compiling from source lol
This has been such a great lesson, many thanks!
Thanks, this will help me learn and use more linux commands
Thank you Jay. you are saving my life.
Great contents. Thanks for your great efforts on making these valuable contents.
Great Tutorials
Very useful!
If anybody wants to know, the if statement checks wether what goes after the "if" returns 0 as its exit code or something else.
It is also possible to use the brackets by themselves and check their return code some other way.
If only there was a convinient video on this channel explaining waht return codes are...
[[ -f ./06-episode ]] && printf "yep
"
Did you watch "Class 06 - Exit Codes"? (I didn't.)
I was just asking myself that question. Thanks 👍🏽
Next video explained what is exit code... but not explaining what you told me.
Thanks bro!
You're the best at explaining Linux concepts (e.g. Systemd).
Ps. commenting from a vanilla Arch distro
thanks teacher for this great lesson I really love it. Thank you a lot
Amazing lesson
Do you have any tutorials on databases? Would love to see those cos you just drive home key concepts that immediately sticks. An excellent instructor that you are. Kudos!!!!
Thanks for the class!!!
Plus the "command -v" command integrates all source for commands to be tested if they exist. In the first version of the test, using "/usr/bin/" excluded all commands from other directories like "usr/sbin/" etc
Thanks for clarifying the issue of command and $command, it was very confusing.
Great video and examples.
Why use 'command'? It has only two switches: -p and -v. The first just runs the argument as it would run alone by itself and the second equals to 'which'. So in this case here just use the 'which' and be done. Why 'command'?
Awesome video! Thanks for sharing this content
Is there a practical difference between using 'which htop' and 'command -v htop'? It seems like in at least this case, it should produce the same output.
Amazing class!
11:25 instead of using ge,gt,lt,le etc simply just use conventional comparison operator i.e.,
Wouldn't writing 'sudo' int the script at 24:43 will ask user for a password?
Great video.
Is the indentation important like it is in python? Will it work for example if between "!" and the evaluated statement there isn't space written?
Shouldn't you use another variable name instead of $command? Might be confusing to most people.
Yes, showing 'command' twice is confusing.
It's a coincidence. Let it go! He explained what it is as well.
It doesn't make a difference since variables can be of any name as the user input. There are no set rules to variable names. You can make up any name.
Hello,
Just a note:
With update and install on the same line: sudo apt update && sudo apt install -y $command
this script would not run the apt install part because of a GPG WARNING in the apt update.
Once the GPG WARNING was cleared up the script ran as advertised.
It would run fine with commands on separate lines:
sudo apt update
sudo apt install -y $command
Joe
I totally understand the -y after the install command, you don't want to answer [Y/n], but what about the password request? How do you avoid this? I'm missing something
Btw if you need to remember all these weird syntaxes bash has (very unintuitive to me) you can just use the manual page for bash:
man bash
It's a very long page, so you can search stuff typing "/stuff" and pressing "n" to search forward and "N" to find the word backwards.
hi, what is the symbol following sudo apt update? how do we input that symbol? Thank you.
9:45 Kind of how I like my conversations ... if you have to repeat yourself I am no longer interested in talking to you, I am not stupid and my ears work.
Why do we write command=/usr/bin/htop?
A-ha! I learnt how to get stopped jobs back. Great!
such a nice training but its a hard to undrestanding for non-native lang
I guess I don't know why shell command language might not be considered a programming language. Its a Turing complete script interpreter. What condition is not met to be worthy of the title?
EDIT: I do fully understand the value of drawing that line in the sand for the purposes of this tutorial, but looking into it I can see there is a larger internet argument going on and that is what confused me.
Great series. How would I look for available commands if I'm writing a script?
how can u able to take yes or no input as user and use as a condition in if else like mynum = " " if [ $mynum == yes ] then echo ... else .... [ $mynum == no ] ...
how come you specified a sudo operation in the script but you both didn't enter it in the script and either when you launched the script? how can that work? at 19:12
Anyone else having a problem with -f flag?
The script written at 13:30 doesn't work for me, and the -f is not highlighted in the editor, using bash version 4.4.20(1).
thanks for this lesson, too. why didn't you have to input your password when you ran sudo commands in the script?
trying to install on a Mac ... having issues with htop. I got a java issue but I downloaded it and it still did not work. I've used htop once in a controlled environment for my bioinformatics program. It worked there but. not on my laptop
hmm the "fg" command does not work in my case... i have paused the classes in between... maybe something got lost in between?
I'm using Linux Lite and it does not work for me either.
In the code you have used sudo command for installing htop, but it did not prompted for password
in my case it is asking for password why? how to automate this.
thanks!
Just trying to introduce/teach someone to a SIMPLE use of if/else statements, will BLOWWW any novice brain to pieces with an additional and completely unnecessary complex stuff you introduced sir! No one doubts that you are knowledgeable, just you yourself need to learn how to get under the "skin" of any dumbfounded beginner, giving him/her a real chance to grasp and understand the given info, not make them to hate it for life !
You sound like the Common Scense Skeptics guy.
I've only used Linux a bit, so this is probably a newb question. How does the script run the sudo install command without requiring you to enter a password to authenticate? Am I missing something?
The shell doesn't ask for password if you installed a package before in the same session using sudo. Once you close the terminal and reopen, it will ask for password again.
how do I get rid of entering the password for the sudo command ? Because it ask me to enter it when I run the bash script
how can you run sudo in a bash script to install programs? I see that it works but I do not understand how it is done with no password prompt?
What about multiple files or software?
How did you save and exit ?
Had a problem on this one. Forgot the last command and so it didn't start. Went back and put it in, then ran it again expecting it to find it installed and run it. Instead it didn't find it, installed it again, and when it tried to run it it came up with an error. I had already run it the first time manually when it didn't run, and I ran it manually after it installed again, and came up with the error when trying to run again. Not sure why. I did verify it actually did install in the correct place, but for some reason the script seems to be looking somewhere else I guess?
EDIT: Must remember to spell the directory usr not user... lol
I was yelling at my phone. CHANGE THE VARIABLE TO HTOP!!!
15:27
why did not ask you for password before install it? [htop]
👍
world chaos, he output 4 space instead of 3 when indenting, how rude !
☯🙏
Ok, this language is horrible. Teaching if great but my god, it's like something from the dark ages.
I'll use it to run python scripts. Why suffer?
If you are running a sudo command in a script, does it not ask you to insert your password? Or was this prompt also skipped by adding the -y?
thanks bro learned a lot