^p and ^n for previous and next line, ^w to kill last word, ^y to yank last word (yes, cut and paste work in the terminal, without the mouse, but don't share the mouse kill buffer).
ctrl u to delete the whole line, ctrl t to switch places of the 2 last letters behind the cursor, ctrl shift c/v to copy and paste in the terminal; obv there are more shortcuts. also you can write to a file without opening it using "echo banana > file.txt" the > symbol will delete all in the file and write what you want, you can append with >>. you can use the output of a command as a command itself by entering the command in "$(command)" and you can redirect standard output in standard input with the | symbol (e.g find banana | grep something). these are just some useful tricks to do stuff in a faster way
Its work in every command 5he !! Is just print whatever you print before Lets say you want to change to a directory but you forget to put cd in the start You can just type cd ! ! And it will work
Using the up arrow and typing sudo at the beginning of the line is quick too, if you go to the beginning of the line using Ctrl+a. In some shells the Home key works as well. Ctrl+e takes you to the end of the line, by the way.
I don't know what's hot about sudo !!. I just do Up Home then type "sudo", or alternatively Up Ctrl-A also works as well. That works just fine and uses just as many keypresses. Additionally, it previews the command you're about to run, so much less risky than !! It also fits better with Ctrl-R (reverse-i-search), which !! can't really do.
Good tips for beginners! Maybe add: - locate / find to search for files - rsync for nice backups / more comfortable way to copy files - du -m | sort -n or baobab to see what takes up how much space on the disk (when you need to clean up) - grep to search inside of files - ip r to find out IP of the router - ping to see if machine on the network / internet is reachable - traceroute maybe? - xprop to find out more about an opened window - lsof maybe in order to see which processes access a file? - chown / chmod maybe? - history - apropos / man - diff maybe - loginctl in case the session seems frozen? - watch .... I'm sure there are a lot more and a lot better examples but they don't come to my mind right now :)
@@AnujRaool you have to install bash-completion but i think is already installed in most distros packages.ubuntu.com/search?keywords=bash-completion But that completion is different than ctrl+R
>dd and binwalk - for working with unknown binary file formats >ffmpeg - anything about video/audio encoding/decoding >imagemagick - image editing >mathomatic - calculator >tmux - multitasking >strace and ltrace - debugging >watch - monitoring things (like output of sensors or nvidia-smi) >lsusb, lspci, lsmod and dmesg - figuring out hardware/driver issues
Gosh, I loved this video. I sure wish you'd make more videos like this. Now, this one really helps me. I see how to do the aliases which I would love to do. Then, I had never seen the CNTRL + ALT + F1 and then F7. In the Linux class that I took at a community college, useful stuff like this wasn't covered. Also, how you showed the Automounting helped. I watched your video, but it was quite a while ago. I hope there is an app to help you quickly handle the automounting syntax, but (yes) I should learn it too. However, thanks for this video. It was really, really, really helpful.
Random useful tip that I like: When I compile stuff from github that is not available in my repos, then I use "sudo checkinstall --install=no" first instead of "sudo make install" to be able to easily remove the github stuff through my favourite package manager. (Usefull for when sudo make uninstall does not work properly)
Why even install software globally if you do not have to? If I can run something in place I do. I'll just make a script to launch it and put that on my personal path. Learn to live in your home directory. Then crap won't get shotgun scattered all throughout your OS.
Learned a few thing there, thanks, including some surprisingly basic things, like shortcut for system monitor instead of htop, sudo !!, and even combination of lsblk and then blkid! In particular the ctrl-alt F7 to get back to normal window after mucking in tty.
FYI htop also shows processes in tree form Its "htop -t" You can make alias htop to run htop -t And htop tree shows full path of process instead of just name so its pretty useful when I'm using python virtial environments. I knw exactly which python process is to quit.
I love these top videos. I switched to Linux fully around 6-7 months ago and I challenge myself to learn something new at least a few times a week. Alias’ for directories is an awesome idea. Idk why I never thought of that lol
A fun little thing about that TTY bit: It's just a "virtual" console. Linux can manage dozens of these things, and if you're sitting at a Linux install in your DE right now, you're already logged into a TTY. You can do anything here you could do anywhere else, including typing startx to get into your UI. Even when you already have your DE up and running in a different TTY! Meaning you can have multiple users logged in different TTYs, or even the same user for that matter. Back in Ye Olde Days people would connect to different TTYs over serial to interact with the system. This is how deep in the roots of Linux the whole multi-user thing is. On my server, I actually run the UI session in one TTY while server terminal apps are running in others. It means I can log in and out of any user I want in the UI, open a bazillion console instances there to do whatever I need to, all while my server software is just quietly humming away in the background, probably tucked away in a tmux instance, completely unconcerned. ...And I'm just a novice, I can't imagine what people who have a better grasp of linux can do with this kind of flexibility.
A few more: $ ps afx shows the full tree of your processes in the terminal $ df -h shows sizes and available space on all mounted devices $ free -h shows memory status (but the same information is available in top too) and couple pushd/popd allow jumping from directory to directory and return back
An empty SPACE in front of a command makes it skip the BASH history. Perfect to do some housekeeping of your bash history 'as you type'. Because my absolute favourite is CTRL + R to turn the BASH history into an autocomplete interactive session.
I did not know about !! thats gonna save me time from all the sily spelling mistakes. Also I use bashtop rather than htop as its a slightly more user friendly terminal monitoring tool. Thanks again for the great tips
sudo !! was probably made in pure sheer anger lol. _"GOD DAMMIT DO I HAVE TO SUDO EVERYTHING YOU SONOFABI-"_
4 года назад
The most important Linux tip in my opinion: use timeshift or something like that. Tinkering is a great way to learn, but when you inevitably mess things up, it's nice to be able to restore a snapshot.
I don't mess computers up. In the 30+ years I've been running them it's only happened like once. OK there was that time when I was setting up a parallel libc but I knew that was going to go bad. I did get that to work eventually too. I wanted to run KDE on Slackware and at the time Slack did not support glibc2. I was not going to run Red Hat either! You're pink to Bob.
For auto-mounting drives instead of editing fstab directly I just use gnome-disks utility and edit the mount options. Makes auto unencrypting drives easy as well so I only need to remember my bootup drive password and I can keep the rest in Bitwarden in case I forget them
Gee your knoledge of Linux is amazing many commands you show here are over my present comprehension level but very interresting to learn about. thanks for sharing
Hi Chris, Thanks a lot! For me as a beginner, this is very helpful. I've learned a lot from your videos. Thanks for sharing your knowledge and improve others people life!
Thanks for making these videos fun. Your awesome. I have first time moved over from win 8 to Linux mint and all your videos really help. There are other content creators but honestly they are a bore to watch. You rock amigo. Keep it up. 👍
I'd like to see someone do a video on how to display a remote machine's GUI locally. Maybe, an entire video showing the setting up of ssh and the firewall and executing a remote machine's browser that display's locally. Thank you:)
Nyc tips.. Thanks for the tip about sudo !! I often pipe to more for reading longer instructions or large list of files like " ls /etc/ | more " or " ffmpeg -help | more "
My NYC tip is don't stare at the tall buildings but rather the sidewalk. You never know what's on it. Plus everyone knows you're a yokel if you're staring at the tall buildings.
Another good video! Some things I use quite frequently: scp to copy files to/from remote systems wget to download files via http tar, gzip, bzip2 for working with archives ln for making links vim the AUR bashtop wireshark Shell scripts - more of an advanced topic Less often: tcpdump - only for servers without a GUI, otherwise I use wireshark lsmod sendmail
Chris, now that I'm actually paying attention, I now seen how to make the fancy prompt. Too bad I missed that older video. Guess I need to go back and watch all your videos. Thanks for your great tips. (Plus I enjoy your occasional sarcasms) ;-)
ok, this sudo !! thing blew my mind. I knew this exact command had to exist, but could never find the syntax for it and always just retyped the command
A cool tip on the command line is if you want to clear the line you hit ctrl-k from the beginning of the prompt. #> I just typed a bunch of junk and want to start over. Home Key, Ctrl-k
I'd suggest using a separate .bash_alias file and sourcing it within .bashrc (source ~/.bash_alias) Also I always install sox, nano, imagemagick, tmux, w3m/lynx and your preferred mailutils package (snail, mail, mailx etc) or even alpine/cone/mutt so you have a usable environment should X fail (or if not using X) Oh and use bash functions
I'd like to see you do some videos on the following: Bash Doing bash scripts with IF statements, which can make them have selections and help modes. like typing the name of the script with the typical ---h after it. I use bash for many things, but mostly to ssh into two different local computers all of the time, and notes on samba and terminal use. These bash scripts are in the path, so they can be called up just like a command, like "linux terminal" calls up my notes on commands used in the terminal. I used "linux terminaledit" to edit that file to put in the tip you gave on the Matrix screen. The ssh command is "s lucid" for may machine lucid and "s dragon" for my machine called dragon. Both are the same bash script, but the $1 string to call up different computers. This is the same with my "linux terminal" or "linux samba" call up is the same bash script that can call up 5 different sets of notes with one script or edit any one of them in nano. Before doing a script, make sure it isn't a command already on the computer. CRON Use of the cron directories to run scripts to back things up. I know you did the command line cron, but these can run whole scripts, which wouldn't fit on a command line. Also these scripts can write the run status to a file, like did it work and how. LOCAL Also I see people advice others to "ssh 192.168.0.41", when they could do "ssh lucid.local" (where lucid is the computer name and local makes ssh look it up in your router) to do the same thing on the local network. That is much easier to remember. Also doing ssh -X lucid.local will make it so you can pull up things like the file or web browsers as a GUI. Dragon has my folding on it for the Cronavirus, and it is in the other room. I can see what the status without leaving my man cave by typing s dragon, which does the ssh -X dragon.local command. Then I pull up Firefox. Aliases are easier than doing scripts. if it is a one line command. I got tiered of typing in "echo $PATH" so now it's just path, an alias, which is easier to remember than "echo $PATH." I have no idea where they got the idea to make it more complicated than just typing in path. Also launchers and places in the task bar.
Excellent video, switched to Linux about a year ago. I have watched a lot of videos and gotten a lot of tips. I have to say there were 3 or 4 I did not know. Thank you. One question: What is the CLI command for the system monitor in debian?
Did you know about jump? Perhaps you don't need a big CD alias but just a magic CD command that jumps to previously cd'd directories based on a fuzzy search. Install jump, set it up and type in j pi to jump to for example your pictures folder from anywhere if you've previously cd'd into it. It will basically keep a history of directory structures. And uses fuzzy search for those directories. For example I type j dev to go to my Development folder that I have in my home folder
High Chris, really nice videos ! If you are looking for a subject for one of your next video. I'm still struggling (and I sure I'm not the only one) to securely "automount" my NAS device (Synology as well) with fstab. Maybe it will worth a 10min explanation video.
In Terminal xkill lets you kill a process without needing to know its official name. Type xkill & enter, then click the window of the process (e.g. vlc) you want to stop.
Great tips; I add my aliases at this location. ~/.bash_aliases so I don't have to clutter my .bashrc and just have one place for all my aliases. Only tip I can think of is the virtual keyboard. Where your actual keyboard is on a blink or some keys just don't work, where you have to replace your keyboard. But if you don't have a spare around or just have to get what every you have to do to finish up a project. For the time being you can bring up your virtual keyboard to continue typing without a real keyboard. Lot of people don't know about this. Which my is call onboard to bring up my virtual keyboard. hopefully those keys work for you or at least your hotkeys can bring it up for the time being. My hotkeys are set as Ctrl + T(continue typing). As long your mouse works, you can continue to type with your virtual keyboard. Even go to the menu with your mouse to bring up the onboard application to continue to type, if your real keyboard is on the blink.
Since you mention cmatrix, I would like to recommend sl. It's a funny little thing for when you mistype ls. That way there's no mistakes, just happy accidents.
Nice to see most of these now looking familiar, Liked aliases, would like more on sym links with there use, How can we automate different open windows when we want more than one in one workspace, say two vertically or horizontally arranged or two horizontal and half screen with third. I need them in google classroom where the website itself is so annoying and not user friendly. One feature I am looking at is the ability two first have two windows vertically arranged and then I can use a hotkey with left and right arrow to move the centre line separating the windows left or right without having to move each of them to divide say 1:3 of the full screen.
Systemd.automount www.freedesktop.org/software/systemd/man/systemd.automount.html If you put systemd.automount in fstab the mounting is posponed to the first usage of the filesystem. For example if you do automount in your net fs, It won't block the boot and It will be mounted after you do a ls folder. We can call it "on demand mounting" if you wish.
@@rotflol6666 Nah. That's how things develop and grow. Everything can always work better than it currently does, even if the current state is to some people perfect. For example, Liquorix Kernel + governor set to performance + KDE Plasma with both the shell and compositor killed = A pretty damn good Steam machine
'cd -' allows you to flip between directory locations on the FS. e.g. If you 'cd /etc/' from the '$HOME', then 'cd -', will bring you back to $HOME; Do 'cd -' again, and end up at '/etc/'
try pkill instead of killall! Always pivot to root from another user on another machine, don't permit root login on ssh also gets you an audit trail on the other machine.
Knew pretty mutch every tip xD Just doing my network mounts differently... I'm mounting my NAS folders via a shell script and not via fstab (in my case I'm only doing additional local mounts in fstab). I'm starting the script via the autostart of the desktop environment.. If the mount is not available (server offline, network down,...) the system is not hanging itself or taking more time to boot up in any way.. It might be a better solution to automount network devices that way..
An extra interesting tool that replaces noMachine for Linux. Its x2go. Its a fork by the times NoMachine was open source. It is very easy to set up and use.
Rather than aliases, I've used bash scripts in ~/Custom Scripts, with symbolic links in the proper root directory. Aliases with a sed script(for any time I may want to change out my OS or upgrade my storage drive) might be a nice alternative.
You youngin's be lazy. In the olden days we had to do a ps -aux | grep to find the process number and then do the kill -9 to take care of those hung processes.
Sometimes finding what you want doesn't come quickly or you don't know the complete name of the process you want to kill. a ps -aux | grep name of process can help. It was something I had to use for years. Can get you the pid etc..... cause... sometimes killall doesn't help. Sometimes you don't know why a process isn't dying, or it will say it won't pop up. Can get you the name of the process quickly too. For instance if you were running chrome (not chromium) you would find out from a ps -aux | grep chrome that you have a google-chrome program running in that situation. If for instance it was still showing some of the processes running towards the bottom that were more or less Zombies without actually being zombies (not sure how that one works but I've seen it happen with a couple programs) you can then either try the killall google-chrome for instance (or whatever program is frying) or a a kill -9 pid etc.....
Hi Chris, thanks a lot for your tips as always! Some times my Linux Mint just freezes with no responses to any keys or mouse movement. Do you have any keys combinations to restart Linux at once? Cheers.
My tips. Hope someone finds something useful. KDE users easily see and kill processes hit Ctrl and Esc. Instead of neofetch you can also use screenfetch. In fstab if you want to have a mount entry that doesn't automount use noauto option. In terminal just use the up arrow to scroll through your previously typed commands. To easily look back into your entire terminal command history you can enter the command history > history.txt and it will drop a text file of your entire command history in your current directory. After a while of uptime system ram usage high? Try sync; echo 2 > /proc/sys/vm/drop_caches. For KDE users plasmashell and if used latte-dock will consume more and more ram the longer the system is up. Use killall plasmashell && plasmashell &, and same for latte-dock to quickly restart them to free that system ram. You can create a script and put an icon on your dock or desktop to do it all in one click. Have a drive or partition used only for backups or rarely used data? Use btrfs filesystem and enable on-the-fly compression. In fstab use the compress-force=zstd option. Can also use zlib or lzo. You can also add a compression level option to use a higher than default compression level at the cost of performance like this, compress-force=zlib:9 for example. I've got to thank Chris for his videos introducing me to btrfs. I never would have learned about btrfs compression if he had not turned me on to btrfs in the first place. I use it with my external USB3 backup drive and my automated backups and other archive data are automatically compressed which is an awesome feature and space saver. The file manager still reports the uncompressed file sizes and I don't yet know what that means for when the file manager thinks the disk is full and it's not but you can use the btrfs utility compsize to see the compressed size and also timeshift can see the true space remaining on disk even though KDE can not.
Ah huh... control+Opt+F1..... i wish I knew. I once update my NVidia graphic card driver, and got a black screen after reboot. Not knowing what to do, and not able to find solution from the internet, I was forced to reinstall the Linux. Now I know. Thanks for the info.
I think new users should know more about ttys and runlevels. I would like to be reminded how to add and subtract virtual consoles- ttys. At least text ones.
@@justsomerandompersononthei2595 No, I mean if there is only 6, create more or if there is 12, and I want 6, remove them. Also change which are GUIs, which are system logs, etc.
I define my aliases in a separate file called .bash-aliases. The .bashrc runs it for me using the source command. I like to keep things in order and not mix everything together in an uncontrollable mess. 😁👍🏼
ncdu for finding humongous files. Had a web spreadsheet that wrote logs to a file that didn't have a .log extension and an android emulator kept its logs in a weird place where they grew to gigs.
Here's how you add a "simple" calculator to the terminal: Use sudo apt install bc xclip to set up your system, then add the following lines to your .bashrc: # clipboard alias setclip="xclip -selection c" alias getclip="xclip -selection c -o" # Calculator calc() { echo $*=$(echo "scale=4;$*" | bc -l) | setclip getclip }
I hate UUID. I am not even keen on naming disks s without a real SCSI interface. I like the old h naming scheme the best. I miss hda. But UUID really disgusts me. It is so butt farging ugly! Whoever came up with it must run around wearing mismatched socks and two left shoes. They have not one shred of elegance about them.
Depends on what computer I'm on, ZSH is cool, but I really don't care if it is bash or zsh. ZSH is a bit faster with the plugins like auto complete and other shortcuts, but Bash is already there and I just didn't feel like reinstalling it hehe.
@@igorordecha Brings back old memories. CD-disk, DAT-tape and so on. At least in my language (CD-skiva, DAT-band, and no, don't try to pronounce it, you'll most likely fail miserably, at least if you are a native English speaker… 😁).
