VehiclesFashionRecipesBlogsHuntTravelsSportFunHandmadeITEducation
Mini-Games
x

x
zakruti.com » IT - Software » IT, programs, coding
So Many Linux Terminal Commands Do The Same Thing DistroTube

So Many Linux Terminal Commands Do The Same Thing DistroTube

FBTwitterReddit

video description

Rating: 4.0; Vote: 1
So Many Linux Terminal Commands Do The Same Thing DistroTube So many terminal commands can do the same thing. For example, I often use the 'wc' program to get a line count of terminal output. You see me do this on distro reviews to get the number of installed packages for that distro. Well, many people like to point out that I don't have to use 'wc' to get a line count. I could actually use at least half a dozen other standard core utilities to get a line count
Date: 2022-03-30

Comments and reviews: 10


There is another reason sticking to a certain set of commands. In the real world of UNIX admins, that is, if one aspires to be one, many of the Linux alternative don't exist on UNIX. For example, wc is standard part of UNIX, nl is not.Lets say you do a site visit to do some admin work, and the company runs HP UX, if you learn the standard commands they'll transfer. You may not even have emacs installed, though vi will be guaranteed., therefore vi is a must learn for real admins, emacs is optional.
Learn the standard BSD/System V set, and you'll be set on any UNIX platform.
Also, what's the point learning something 10 different ways when one will suffice, unless there is a specific reason one method is superior in any given situation. or it's for fun.

reply

yeah but from different angles...
lsblk then I can get the same info using findmnt but from a different direction using the disk mount directory instead of the device directory
don't things present the information differently and if I don't like it I can pipe it through an awk/sed script and get it the way I want
Linux gives you options unlike Windows which is their way or no way
----

reply

Hey all of you useless-use-of-cat haters. Nothing wrong with using cat to pipe output to another command that can read from either standard input or the file. I actually find it easier to start out with cat. You can always optimize it out in a shell script later. Put that in your pipe and smoke it! -
reply

Linux is impressing.
I used Windows for almost 30 years and I loved it. But since about two years I switched to Linux, because my harddisk crashed during an unstoppable Windows update and I will never switch back to Windows again. I really love the freedom Linux is giving me.

reply

WC uses the kernel to read the file, and hence pretty fast. You can use the same code to read your files into memory. Big files. It takes you just to type a couple of letters ... This is a big difference when you are crafting piped/nested commands.
reply

Hey DT, you can use the 'count' command in the fish shell for the same result.
For example, 'pacman -Qq - count' is the same as 'pacman -Qq - wc -l', just with an easier to read syntax.
This also works with count $VAR or count < FILE

reply

Why use cat(1) and pipe into wc(1) and nl(1), when you can add that to the commands directly? tee(1) are actually a reason to pipe like that.
Create an empty file with touch(1) command.
Except that, good introduction, as usually.

reply

NOOO! Just as there MUST BE just ONE Linux Distro, there MUST BE just ONE way to do this, and ONLY ONE!!!!
Just kidding, another great video on the flexibility of Linux and the CLI. Thank you so very much!

reply

-04:28 actually an aspirant for the useless use of cat award (according to Randal Schwartz) here ;-)
instead of
cat -/.bashrc-wc -l
this will do the same
wc -l -/.bashrc

reply

It's good we have so many different ways of doing the same thing. The more we reinvent the wheel, the more wheels we have to choose from to better fit the situation we're in.
reply
Add a review, comment






Other channel videos