Category: Tips

How To: Show Your Hard Drive Specifications In The Terminal

In today’s article, we’re going to explore one way that you can show your hard drive hard drive specifications in the terminal. There’s nothing too challenging in this article, so even new people can follow along.

To be clear, I’m using the phrase ‘hard drive’. In this instance, I’m speaking both of mechanical hard drives (HDD) and solid state drives (SSD). I could probably come up with something better, but we’ll just stick with ‘hard drive’.

You may want to know your hard drive specifications to ensure you got what you paid for. You might also want to know what features it supports – and how long at least one of those features is expected to take. For instance, there’s a secure erase feature on many drives and this takes time. The command we’ll be using may tell you how much time it will take to securely erase the disk.

We’ll be showing the hard drive specifications in the terminal and the biggest tool we’ll be using is ‘hdparm’. It does what it says on the tin and describes itself like:

hdparm – get/set SATA/IDE device parameters

You should find hdparm installed and shouldn’t need to install anything. If you want confirmation that hdparm is installed, run:

You’ll find that there’s a lot to learn about hdparm, but don’t worry about that. You can check the manual if you want:

See also:

Check Disk Speed In The Terminal

So then, let’s just jump into the article…

Show Your Hard Drive Specifications:

As the title suggests, we’ll be using the terminal for this exercise. Open you terminal now. If you don’t know how to open the terminal, you can do so with your keyboard – just press CTRL + ALT + T and your default terminal should open.

With your terminal now open, let’s find your disk drives with the following command.

Your drive should look something like this:

lsblk output
You’re looking on the left, at the base directory – such as ‘sda’ or ‘sdb’.

At this point, you want to note the base – the parent disk drive. In the above image, you see two of them. You see both ‘sda’ and ‘sdb’. Your results can be wildly different, but that’s the information you need.

Now it’s time to show the hard drive specifications. To do that, you’ll want to use a command that looks a lot like this:

An example of that command would look like:

The output is pretty verbose and you can learn a great deal about your hard drive specifications by using the hdparm command. As suggested above, don’t be afraid to run man hdparm to learn more because hdparm is a rather robust application..

Closure:

There you have it, you have another article! This time, you’ll have learned a bit about one way to show your hard drive specifications in the Linux terminal. Pretty sweet! So far we’ve been able to maintain that ‘every other day’ schedule.

Anyhow, please don’t frivolously click ads on the site. Google’s just taking the clicks away and is probably taking away some legitimate clicks while doing so. That’s not helpful! I appreciate it, I appreciate that you’ve whitelisted the site, but Google’s convinced I have invalid traffic and there’s not much I can do about it.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

How To: Test Your Drive Speed In The Linux Terminal

Today’s article is going to just be a nice and easy article, one that shows you how to test your drive speed in the Linux terminal. It’s easier than you might think and even easy enough that a new Linux user can figure this one out.

Why would you want to do this? Why would you want to test your drive speed in the Linux terminal?

Well, while there are surely GUI ways to accomplish this, you might want to verify that you’re getting the disk speed you paid for. You might also just want to know your drive’s speeds or perhaps you want to post your drive speed on a forum for bragging rights? These terminal commands will also be pretty much universal, across all distros.

It doesn’t matter why you want to test your drive speed, it just matters that you can test it – and that you’ll now know how. And, you know what they say? Knowledge is power!

So, what will we be doing?

Well, we’ll be using the Linux terminal to check how fast we can read and write data to your drives, no matter if they’re spinning platter hard disk drives or solid state drives. The commands will be the same for all drive types and are fairly easy to learn.

So, with all that said and done, let’s get into the article…

Test Your Drive Speed In The Linux Terminal:

Of course, this article will require an open terminal. On Linux-Tips we do a lot in the terminal. It’s fun and fairly universal. If you don’t know how to open the terminal, you can do so with your keyboard – just press CTRL + ALT + T and your default terminal should open.

With your terminal open, you’ll want to run the following command to identify the drive you want want to test. That’s nice and easy, just run:

You’re looking for something like /dev/sda1 or something like /dev/nvme0n1p1 and the lsblk command might help you narrow down which drive it is you want to test.

Once you have identified the drive you want to speed test, you can begin testing. You can first try testing the write speed, that is how fast you can write data to the drive. To do that, you’re command would look like:

For example, if you had ‘sda1‘, your command would look like:

That will tell you how quickly you can write data to your drive, a pretty handy number to know. However, that’s only half of the equation…

You might also want to know how fast you can read data to the drive, the other half of the equation. The command to find the read speed is pretty similar to the command to read the write speed – and that command would look a little something like this:

Or, again, if you want an example of how to test the speed at which you can read data from your drive, an example command would look a little like this:

Note the difference between the commands. In the latter command, we’re writing data from the disk (reading it) and sending it to the bit bucket. With the write command, we’re going the opposite direction. In one case you’re writing from /dev/null and in another case you’re writing to /dev/null. Pretty easy, huh?

Closure:

There it is! This is actually the 301st article written for Linux-Tips.US! This time around we learned how to test your drive speed in the Linux terminal. I told you that it wasn’t too complicated and I stand by it. If you just follow the directions, you’ll learn how to test your drive speed and have another tool in your toolbox.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Let’s Learn A Little About The ‘dir’ Command

In today’s article, we’re going to learn about the ‘dir’ command. The ‘dir’ and ‘ls’ command are quite similar, but ‘ls’ seems to get all the press. So, today we’ll be looking at the ‘dir’ command. It will be a relatively short article (I suppose) and easy enough for new people to follow.

You’re possibly already familiar with the ‘ls’ command. I’ve written a variety of articles about ‘ls’. We’ve used ‘ls’ in numerous articles along the way. Here are a couple of ‘ls’ articles:

Some Fun With Sorting The Output Of ‘ls’
Let’s Use ‘ls’ To Sort Files By Time

Those are just a couple. WordPress, the backbone of this site, isn’t very good at searching for just two characters like ‘ls’. That’s for good reason and I’m not sure if that behavior can be changed.

Ah well… Root around and I’m sure you’ll find more. I’ve written about 300 articles and can’t possibly remember them all!

Anyhow, we’ll be using the ‘dir’ command in this article. It describes itself pretty well in the man pages, and is similar to the ‘ls’ command. It describes itself as:

dir – list directory contents

So, if you’re familiar with the ‘ls’ command, you’ll find ‘dir’ to be quite similar. I’m sure there’s a reason that both exist – I’m just not sure what that reason is, nor am I sure why both are included by default. Feel free to let me know your thoughts or theories!

Edit: See this link to see why Linux contains both.

Well then, let’s get on with it…

The ‘dir’ Command:

Well, you shouldn’t need to install anything for this article, but you will need to have an open terminal. By now, you know how to open the terminal if you’re a regular reader, but others need only press CTRL + ALT + T and their default terminal should open.

With your terminal now open, let’s just start with the basics. If you just enter the ‘dir’ command it will output a list of all the visible files in that directory. It looks like:

You can also specify a directory, like:

If you want to show hidden files, you can try this:

If you want to list things in a single column, in a list format, you can just add the -l flag. This also shows the file’s permissions and modification time. So, you could try:

If you want to list files with the ‘dir’ command and to do so recursively (digging into the folders within folders), you can do that too. All you need is the -R flag. So, for example:

That’s just scratching the surface of the ‘dir’ command. There’s a whole lot more that you can do, so just try the man page for more nifty tricks  you can do with ‘dir’.

If you have any questions or nifty ‘dir’ information, please feel free to leave a comment. It’s a pretty handy command to have on hand, much like ‘ls’.

Closure:

And there you have it. You have yet another new article, this one about the ‘dir’ command. It’s not terribly complicated and it’s another tool to toss into your toolbox. You never know when you might want to use it instead of the ‘ls’ command, though they’re awfully similar.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

How To: Extract Files From An .iso

In today’s article, we’re going to learn how to extract files from an .iso. This is a good tool to add to your toolbox. You never know when you may need it. This really shouldn’t be a very long article, and even a new user should be able to follow along. Read on!

First, an .iso is really an optical disk image – even though some of the current .iso examples far exceed what you can write on a CD or even a DVD. You still use an .iso when  you’re writing a Linux live/boot USB. It’s still an optical image, you’re just not writing it to optical media. It’s a standard.

Commonly, you’ll find that Linux distros come in .iso format. You’ll also find some backup software that creates an .iso image. Traditionally, you don’t extract an .iso, you write it as a single image to your media, be it USB, CD, or DVD. But, sometimes you might want to extract files from the image file, and it’s not terribly hard to do so.

Further Reading:

How Do I Install Linux (A General Guide)
How do I ‘Boot to USB’? (Or CD/DVD, if Such is Available)
balenaEtcher: A Tool To Turn Linux .ISO Files Into Bootable USB Drives

Alas, you might have flubbed a configuration file and want to extract a known good one from the .iso you used to install Linux. You may have a backup in .iso format and not want to recover the entire image just for a few files, so you’ll want to extract the files from the .iso. There are a variety of reasons why you might want to do this, which is what we’ll learn in this article.

Extract Files From An .iso:

Just like so many previous articles, we’re going to do this in the terminal. So, crack open your terminal and we’ll get started. If you don’t know how to open your default terminal emulator, just press CTRL + ALT + T and your default terminal should open.

With your terminal now open, the first thing you have to do is make the correct directory in your /mnt (mount) directory. It looks like:

Next, you want to mount the .iso, which is done like this:

Now, at this point, you can do one of two things. If you want to remain in the terminal, you just ‘cd /mnt/iso‘ and start with ‘ls -la‘ to navigate and find the file(s) you want to extract from .iso. Pretty easy, really!

Alternatively, at this time, your system will now see the .iso as being a mounted image file. You can open your default file explorer (Nemo, PCManFM-Qt, Thunar, Dolphin, and the list goes on and on and on…) where you should see the .iso mounted, especially if you navigate to /mnt/iso. You can then navigate to that mounted image graphically, treating it like its own file system, and extract files as you see fit.

The choice is up to you. You can use a GUI file manager or just use the terminal. Both will be equally effective and allow you to extract files from an .iso. See? Not all that hard at all. Find an .iso on your system and test it.

Closure:

And there you have it, you have yet another article! This time, we’ve gone over how to extract files from an .iso. This isn’t something you’re likely to need often, but it’ll be handy when you do need it. It’s just one of those tools you stuff into the back of your mind for when you do need it – or at least enough to be able to get a reminder by way of a search engine.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

How To: Open FeatherPad At A Specific Line

Today’s article is going to show you how to open FeatherPad at a specific line. It won’t be a very long article. It won’t be a difficult article. But, ideally, it’ll be a handy article. Read on!

FeatherPad is a pretty decent, lightweight text editor. It reminds me of LeafPad quite a bit, but it’s its own separate project. You will find that FeatherPad is the default GUI plain text editor with Lubuntu, which is how I first learned of it.

FeatherPad supports things like tabs, tab drag and dropping, and can even do things like automatically close brackets when you open them. There are plenty of options, but it’s a basic text editor. You can even use CTR: + + to zoom in, and you can use CTRL + – to zoom out. That’s pretty neat.

Me? I love the ability to save a session and have the previous session open automatically when the application is started. FeatherPad lets me have a couple dozen text files that I want to keep open at all times, and this is how I do that. I just use the session manager and open the previous session when FeatherPad starts.

If you’re looking to try a new graphical text editor, I would suggest taking a look at FeatherPad. It’s certainly in your default repositories, assuming you’re using a major distro. As I mentioned above, it’s still a pretty basic editor, that could also be used as a code editor – so don’t expect too much from it, as it’s not intended to do all that much.

So then, let’s learn how to…

Open FeatherPad At A Specific Line:

You can open FeatherPad via the GUI and just navigate to the intended line. It supports line numbering, so that’s not a problem. You can also start FeatherPad from the terminal, which is what we’ll be doing here. Press CTRL + ALT + T and your default terminal should open.

With your terminal now open, you should probably start by installing FeatherPad. It is installed by default in Lubuntu, but to install it in something like Ubuntu you’d run this command:

Now, if you try to run ‘man featherpad‘ you’ll find out that there’s no man page associated with FeatherPad. So, to access the help documents, you’d just run:

Of course, that right there’s enough for the article. What you need to know is mostly right there in the help pages. They’re not even complicated, but that’d make for a very short article. So then…

If you want to open LeafPad at a specific line, it’s this:

A real world example of that would be something like:

You can even open LeafPad at a specific line AND at a specific column. That command isn’t much more difficult, it looks like this:

Again, for a real world example, if you want to open ~/.bashrc on line 12 and at column 5, the command would look like:

Bonus:

In all those instances above, FeatherPad will be attached to the terminal. If you close the terminal FeatherPad will also close. So, if you start the application from the terminal, you have to leave that terminal window open until you’re done with it.

If you close the terminal, FeatherPad would also close. On top of that, there’s no new line for you to continue typing further commands into the terminal. So, you can’t keep using that terminal while FeatherPad is open.

We got this figured out!

Which is also why you might want to read this previous article:

Don’t Let Applications Close When The Terminal Is Closed

Or, to save you some reading time, you can just add a ‘&‘ at the end of the terminal command to open FeatherPad at a specific line number. Like so:

If you use that command, with the ‘&‘ at the end of it, it will detach FeatherPad from the terminal, meaning you can keep FeatherPad open while still using the terminal or that you can even close the terminal while that instance of FeatherPad remains open.

Closure:

And there you have it. You have another article! This time it turned out a bit longer than I expected. I wasn’t going to include the bonus content but that seemed like a good idea. Either way, it’s not very complicated and should be a quick read.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Linux Tips
Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.