10 Advanced Linux Commands You’ve Probably Never Used (Part 3)
10 Advanced Linux Commands You’ve Probably Never Used (Part 3)
www.tecmint.com
10 Underrated Linux Commands to Try Today – Part 3
19 comments
-
"Advanced Linux Commands You've Probably Never Used"
ping
-
Just thinking of commands I need to learn, and I think
chrootis up there. Iirc, you can recover from some extremely bad system states with an ISO andchroot.I understand the basics of what it does from it's description, I just haven't really dived deep enough to feel comfortable with it.
-
foobar Command – Quick Text Substitution
doesn't work for me (using fish) and is apparantly only available in bash; would you call that then a command?
at Command – Schedule One-Time Tasks
at is also not a built-in but an external tool you have to install first; but its an interesting one.
-
doesn’t work for me (using fish) and is apparantly only available in bash; would you call that then a command?
Right, the
^search^replaceis a Bash feature. It is a builtin command, likeechoorcdin example. Just because a command is not available to any other shell or if its not an independent program, does not make it not a command (in my opinion).However I agree its a little bit out of place here. A note that its a builtin and not universally available to every shell would have been nice in such a listing.
-
-
These lists are always nice. But how does following even fit into the topic of this post at all? These are not underrated hidden gems and most who use the terminal used it already:
- file.txt Command – Overwrite a File
Routing the stdout to a file is one of the most common used "commands" in Linux. And one to learn at the very beginning.
- ping -i 60 -a IP_address Command – Ping with a Custom Interval
Probably not that useful in day to day usage, but I assume this is one of the most basic commands lot of people used it in the past to test if they have internet access.
ping google.comis common, or so I thought.Otherwise there are some nice listings, such as
at(I really should use that one too),du(actually not that hidden, but its probably underrated and people install lot of tools doing same instead) oryes(useful for certain automation, where you know the answer is to proceed). A solid list, but a little bit short and with a few questionable entries.-
There's someone out there to whom the existence of
ping -i 30is news.The idea of using
>fileinstead oftouch file— orcp /dev/null fileif it already exists — is new to me, though it doesn't seem all that useful.-
I've been doing echo "" > file
Useless Use of Echo I guess.
-
-
Mine you, this page is clearly targeted at an audience who've never opened a shell before; they're all quite common, and it's almost impossible to have spent any time in bash, zsh, or any bash-ish shell without encountering or using these. Also, a couple are not going to work at all in non-standard shells like fish, nushell, or even more common shells like ash, BusyBox, or the venerable csh, because they're bash built-ins. There's dependency on the GNU toolset, too; some of these commands won't work on FreeBSD, even when running bash, because the SysV tools have different argument lists.
19 comments