I get it !!! The shell operators section took me a few times of watching it over and over, but it gets easier the more I watch it, mainly the section about chaining commands using the double ampersand "&&". Thanks for being so detail oriented. It helps me understand the 'WHY'. It's slowly coming together...
Hi Hank, found it very useful. Some more commands learned and others refreshed. For me, when you go off script and on side missions its like 'Gold' It is similar to dotting the i's and crossing the t's. Very useful and increases my understanding. Thank you and keep up the great work :)
I'm glad you find it useful David! I literally have to remember to reel it back in when I go off script, because I have to remember that it's meant for beginners and to go too deep will overwhelm some people. But I think I maintained fairly well this time around lol
I'm very happy to hear that it's helping you! And you're very welcome. There are two more episodes coming this week, and then next week, and so on. Stay tuned!
30:52 - I’m a N00b, so I could be wrong lol, but I wonder if when you used the “find” command with “*.txt” if it only searched for the first file that came up? Like, since your “file.txt” wasn’t in any folders and it found that one first, it stopped looking for anything else. Is there a plural version of this command? Or would it have typically located and displayed all files ending in .txt on another linux system? P.S. Thank you for these videos. I just found you on my FY page and I subbed. ❤😊
35:57 Now I’m at this point in the vid and I agree with you that it may be simply due to this being a demonstrative teaching environment, and going off script made it not really know what to do. 😄
@@jah-q6f you’ve made a great observation and yes there is a “plural” version. It’s called the “recursive” search and essentially you tell “find” that you want it to search inside any location and all of the folders inside of it. So if we do something like “find / -name *.txt” we’re telling it to search inside of the root “/“ and all of the folders inside of the root. And that command usually works. I just did some more research about it and I wonder if I placed the *.txt inside quotes or not. This is the article that explains it: www.binarytides.com/linux-find-command-examples/#google_vignette
@@jah-q6f lol that’s why I was so confused. Because I have actually used it in other environments and it worked Ike a charm. I did a Linux tutorial video a while back and the “find” command worked very well in it. P.s. thanks for the sub!
@@HankHacksHackers Ahh okay, that makes sense. Thank you for elaborating on that and for providing your research link. Much appreciated. I’m definitely gonna check it out. Peace. 😊
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
I get it !!!
The shell operators section took me a few times of watching it over and over, but it gets easier the more I watch it, mainly the section about chaining commands using the double ampersand "&&". Thanks for being so detail oriented. It helps me understand the 'WHY'. It's slowly coming together...
@@darnellknights3147 let’s goooooo… I love it. Very happy that it’s clicking for you Darnell
Hi Hank, found it very useful. Some more commands learned and others refreshed. For me, when you go off script and on side missions its like 'Gold' It is similar to dotting the i's and crossing the t's. Very useful and increases my understanding. Thank you and keep up the great work :)
I'm glad you find it useful David! I literally have to remember to reel it back in when I go off script, because I have to remember that it's meant for beginners and to go too deep will overwhelm some people. But I think I maintained fairly well this time around lol
You’ve been so helpful…Thanks so much…cant wait for the next episodes 🙏🏼
I'm very happy to hear that it's helping you! And you're very welcome. There are two more episodes coming this week, and then next week, and so on. Stay tuned!
Big fan here😊
@@feyishow3589 thanks! And welcome!!
LETS GOOOOOOOOOOO!
LFG!
30:52 - I’m a N00b, so I could be wrong lol, but I wonder if when you used the “find” command with “*.txt” if it only searched for the first file that came up? Like, since your “file.txt” wasn’t in any folders and it found that one first, it stopped looking for anything else. Is there a plural version of this command? Or would it have typically located and displayed all files ending in .txt on another linux system?
P.S. Thank you for these videos. I just found you on my FY page and I subbed. ❤😊
35:57 Now I’m at this point in the vid and I agree with you that it may be simply due to this being a demonstrative teaching environment, and going off script made it not really know what to do. 😄
@@jah-q6f you’ve made a great observation and yes there is a “plural” version. It’s called the “recursive” search and essentially you tell “find” that you want it to search inside any location and all of the folders inside of it. So if we do something like “find / -name *.txt” we’re telling it to search inside of the root “/“ and all of the folders inside of the root. And that command usually works. I just did some more research about it and I wonder if I placed the *.txt inside quotes or not.
This is the article that explains it:
www.binarytides.com/linux-find-command-examples/#google_vignette
@@jah-q6f lol that’s why I was so confused. Because I have actually used it in other environments and it worked Ike a charm. I did a Linux tutorial video a while back and the “find” command worked very well in it.
P.s. thanks for the sub!
@@HankHacksHackers Ahh okay, that makes sense. Thank you for elaborating on that and for providing your research link. Much appreciated. I’m definitely gonna check it out. Peace. 😊
@ you’re welcome ☺️ have fun!