11 More Linux Commands Every Linux User Needs - Learning Terminal Part 2 - Chris Titus Tech
video description
Date: 2022-03-20
Related videos
Comments and reviews: 10
Cuttlefish
Computers in it's most basic use, I find is best at note taking/editing. It's also a bare/basic philosophy that everything in Linux is a file/list, so editing them would be fairly important, I imagine for most people. Aside from nano and vim, I'm surprised you haven't gone over cut, paste, nl, head & tail, and a few other useful file-displaying and editing tools.
awk and sed may or may not be more advanced, but idk, I barely use them just because the syntax for them is kinda ridiculous and weird. However, much like a lot of stuff in Linux, I hear these tools are amazingly powerful once you get used to them, which I have no incentive for because there's other more basic tools to do the same thing. And worst comes to it, I can just open these up in a leafpad or vim for editing.
Come to think of it, these commands are probably more sensibly used sticking them in a script rather than using them directly from the terminal. It probably depends on workflow and comfort in using them. However... I remember in my early days preferring to write wrapper scripts for complicated commands and sticking them in -/bin rather than writing aliases for them... this stuff is weird.
reply
Computers in it's most basic use, I find is best at note taking/editing. It's also a bare/basic philosophy that everything in Linux is a file/list, so editing them would be fairly important, I imagine for most people. Aside from nano and vim, I'm surprised you haven't gone over cut, paste, nl, head & tail, and a few other useful file-displaying and editing tools.
awk and sed may or may not be more advanced, but idk, I barely use them just because the syntax for them is kinda ridiculous and weird. However, much like a lot of stuff in Linux, I hear these tools are amazingly powerful once you get used to them, which I have no incentive for because there's other more basic tools to do the same thing. And worst comes to it, I can just open these up in a leafpad or vim for editing.
Come to think of it, these commands are probably more sensibly used sticking them in a script rather than using them directly from the terminal. It probably depends on workflow and comfort in using them. However... I remember in my early days preferring to write wrapper scripts for complicated commands and sticking them in -/bin rather than writing aliases for them... this stuff is weird.
reply
Engie
when using the ssh command, do not just dismiss the fingerprint warning. linux is only as safe and secure as it's users know what they are doing. if someone with an ill intent tries to impersonate your site to grab your username and password when you connect to their fake site -- this is exactly the type of a situation that ssh devs want you to avoid by warning you about the fingerprint mismatches. telling your viewers to just type yes is an ill advice here.
reply
when using the ssh command, do not just dismiss the fingerprint warning. linux is only as safe and secure as it's users know what they are doing. if someone with an ill intent tries to impersonate your site to grab your username and password when you connect to their fake site -- this is exactly the type of a situation that ssh devs want you to avoid by warning you about the fingerprint mismatches. telling your viewers to just type yes is an ill advice here.
reply
Cuttlefish
PROTIP: download xclip and add the alias clip='xclip -selection clipboard' to your .bashrc file! So useful! Another thing that helped me get away from Windows (powershell; halfway through my Linux transition, I tried to use Windows the way I've been using Linux).
Idk about others, but I find it faster/smoother to type out another command than to highlight text with my mouse and hit Ctrl+Shift+C.
reply
PROTIP: download xclip and add the alias clip='xclip -selection clipboard' to your .bashrc file! So useful! Another thing that helped me get away from Windows (powershell; halfway through my Linux transition, I tried to use Windows the way I've been using Linux).
Idk about others, but I find it faster/smoother to type out another command than to highlight text with my mouse and hit Ctrl+Shift+C.
reply
Cuttlefish
PROTIP: download xclip and add the alias clip='xclip -selection clipboard' to your .bashrc file! So useful! Another thing that helped me get away from Windows (powershell; halfway through my Linux transition, I tried to use Windows the way I've been using Linux).
Idk about others, but I find it faster/smoother to type out another command than to highlight text with my mouse and hit Ctrl+Shift+C.
reply
PROTIP: download xclip and add the alias clip='xclip -selection clipboard' to your .bashrc file! So useful! Another thing that helped me get away from Windows (powershell; halfway through my Linux transition, I tried to use Windows the way I've been using Linux).
Idk about others, but I find it faster/smoother to type out another command than to highlight text with my mouse and hit Ctrl+Shift+C.
reply
Paul
env dumps your whole environment. In case you don't even know what you're looking for. Which it looks like you don't. SSH is in its own package. You do have to install it if you want to use it. Though perhaps your kitchen sink distribution just throws a copy at everyone? $ dlocate -S -which ssh- openssh-client: /usr/bin/ssh It is grep not grip. grep is short for global regular expression print.
reply
env dumps your whole environment. In case you don't even know what you're looking for. Which it looks like you don't. SSH is in its own package. You do have to install it if you want to use it. Though perhaps your kitchen sink distribution just throws a copy at everyone? $ dlocate -S -which ssh- openssh-client: /usr/bin/ssh It is grep not grip. grep is short for global regular expression print.
reply
xnonsuchx
My first experience w/ grep was doing scripts in PS3 'OtherOS' Linux (YDL 6.1) for emulation stuff...had to use it and sed to parse MAME XML info, among other things. It made me wonder why Windows didn't have such helpful tools built-in. Also, the touch command to easily update/create files (used it as a quick and dirty way to 'flag' settings options for emulator scripts).
reply
My first experience w/ grep was doing scripts in PS3 'OtherOS' Linux (YDL 6.1) for emulation stuff...had to use it and sed to parse MAME XML info, among other things. It made me wonder why Windows didn't have such helpful tools built-in. Also, the touch command to easily update/create files (used it as a quick and dirty way to 'flag' settings options for emulator scripts).
reply
Jeroen
-10:24 you can make some impressive dashboards by running a process that automatically runs SSH and execute 1 or more command(s) on 1 or more servers (like df -h or maybe cat /proc/loadavg) and snipping the value's you want out of the output. works nicely if you have multiple servers and a way to draw graphs on a local webserver for example :)
reply
-10:24 you can make some impressive dashboards by running a process that automatically runs SSH and execute 1 or more command(s) on 1 or more servers (like df -h or maybe cat /proc/loadavg) and snipping the value's you want out of the output. works nicely if you have multiple servers and a way to draw graphs on a local webserver for example :)
reply
TheLotw
Chris, check out eDEX-UI for a command line type program. Its not something you will use everyday, but nice to show off what could be done if devs but work into the command line. I use it sometimes when I remote to another machine, because it makes noise when the screen gets updated, so I know its doing something if I am not looking.
reply
Chris, check out eDEX-UI for a command line type program. Its not something you will use everyday, but nice to show off what could be done if devs but work into the command line. I use it sometimes when I remote to another machine, because it makes noise when the screen gets updated, so I know its doing something if I am not looking.
reply
teamvigod
Good video. I forgot about htop! damn! You could add piping to -more- or -less- for those long lists. so after you systemctl - grep enable - more. this way you can page thru the list in terminal. I use MORE and LESS alot in terminal. Thanks for the video. Enjoying your work.
reply
Good video. I forgot about htop! damn! You could add piping to -more- or -less- for those long lists. so after you systemctl - grep enable - more. this way you can page thru the list in terminal. I use MORE and LESS alot in terminal. Thanks for the video. Enjoying your work.
reply
fourdotsYT
Search/browse history commands:
Press -Ctrl+r- and type command fragment (incl. arguments) to search. Keep pressing -Ctrl+r- to flip through all matches. Press enter to execute selected command, or right arrow to put it on the command-line without executing (to edit).
reply
Search/browse history commands:
Press -Ctrl+r- and type command fragment (incl. arguments) to search. Keep pressing -Ctrl+r- to flip through all matches. Press enter to execute selected command, or right arrow to put it on the command-line without executing (to edit).
reply
Add a review, comment
Other channel videos
