numactl is missing there. Information about memory topology is quite important.
It is not available in some distributions and one needs to install it (e.g., on Ubuntu/Debian: # apt install numact).
Linux commands for advanced hardware and system info
21–30 of 49 posts
Re: Linux commands for advanced hardware and system info
#22`lstopo` is cool too for bigger servers
Re: Linux commands for advanced hardware and system info
#23The article picture almost had a Droste effect, almost.
Re: Linux commands for advanced hardware and system info
#24I have to say the title is a bit clickbaity. Since when were uname,dmesg,fdisk,gdisk,parted,blkid,lsblk,mount,df and /proc "advanced" commands ? A newbie will likely need to use all of them within the first week of them ever using Linux.
I have interviewed "senior devops" candidates that didn't know what procfs was. edit: We didn't consider them for the role.
I know what it is, do I qualify for at least a junior position? :D
Re: Linux commands for advanced hardware and system info
#25I have to say the title is a bit clickbaity. Since when were uname,dmesg,fdisk,gdisk,parted,blkid,lsblk,mount,df and /proc "advanced" commands ? A newbie will likely need to use all of them within the first week of them ever using Linux.
If you install Ubuntu or any other user friendly distro you might not ever use any of them.
I know what they are, obviously, but I don't think I've needed any of them other than uname because I don't know where Ubuntu prints the kernel version.
Re: Linux commands for advanced hardware and system info
#26Earlier quoted context omitted.
"A newbie will likely need to use all of them within the first week of them ever using Linux." And then some people wonder, why the year of the linux desktop still has not arrived. But luckily no, unless things went very wrong, a newbie will not have to invoke those commands - and if he indeed has to, he or she will likely just give up anyway. (Btw. I use linux since years and so far only had to use half of the liste…
I concur. I've been using GNU/Linux on the desktop (and server) for 20 years, I don't think I ever used blkid or lsblk. fdisk, on the other hand, was a thing in the DOS/Windows world, too, back in the day, and dealing with partitioning is something you are going to do regardless of the OS you are using.
> I concur. I've been using GNU/Linux on the desktop (and server) for 20 years, I don't think I ever used blkid or lsblk.
How do you write disk images (like, if you're installing a new machine and you need to write the installer to a USB drive)? I always use lsblk to find the right device name, then dd to write it.
Re: Linux commands for advanced hardware and system info
#27Earlier quoted context omitted.
You’re already advanced then. Your claim about “within the first week” is a bit silly. I’ve used Linux on and off for the last 15-20 years. Just occasionally, to get certain things done in my development work. And I couldn’t tell you what any of those commands do (although I’ve probably used them a few times by copying and pasting). Advanced is subjective.
It may be true that people don't need to use these commands in the first week. Still doesn't make them advanced. Perhaps intermediate but I think even that is a stretch. You can drive a car and never open the hood if you want. Opening the hood to change the oil still doesn't make you advanced in any way shape or form. Doing your own breaks is a step further but it's still pretty basic. Swapping your engine, is advanc…
I’d settle for intermediate.
Re: Linux commands for advanced hardware and system info
#28Earlier quoted context omitted.
I concur. I've been using GNU/Linux on the desktop (and server) for 20 years, I don't think I ever used blkid or lsblk. fdisk, on the other hand, was a thing in the DOS/Windows world, too, back in the day, and dealing with partitioning is something you are going to do regardless of the OS you are using.
> I concur. I've been using GNU/Linux on the desktop (and server) for 20 years, I don't think I ever used blkid or lsblk. How do you write disk images (like, if you're installing a new machine and you need to write the installer to a USB drive)? I always use lsblk to find the right device name, then dd to write it.
I use dd, too. But I usually know what device corresponds to the USB drive. If my laptop only has one HDD/SSD, it's /dev/sda, so a USB drive will show up as /dev/sdb. My desktop has two internal SSDs, sda and sdb, so the USB drive is going to be sdc.
Re: Linux commands for advanced hardware and system info
#29Earlier quoted context omitted.
I concur. I've been using GNU/Linux on the desktop (and server) for 20 years, I don't think I ever used blkid or lsblk. fdisk, on the other hand, was a thing in the DOS/Windows world, too, back in the day, and dealing with partitioning is something you are going to do regardless of the OS you are using.
lsblk is super helpful and I've used it many, many times since I found it about 5 years ago. inxi is a new one for me. Command usage / knowledge depends on what you need and why.
> inxi is a new one for me.
For me, too. I was surprised to find it already installed on my system. :)
Re: Linux commands for advanced hardware and system info
#30I have to say the title is a bit clickbaity. Since when were uname,dmesg,fdisk,gdisk,parted,blkid,lsblk,mount,df and /proc "advanced" commands ? A newbie will likely need to use all of them within the first week of them ever using Linux.
I've been using Linux since 1995.
I had never heard of `inxi`. 21k lines of Perl, not Bash....