Meta: 200th Post

Today’s article is just a quick note, nothing long or important, that marks our 200th post. It has been a long time coming, but it’s finally here. I’ve had some help along the way, but I’ve written all but a few of the articles. Yeah, we’re at 200 articles on Linux-Tips.

I initially said I’d do this for a year. That year passed a while ago and I’m still going. I’m still not out of ideas for articles, so I keep writing them. Of course, getting to do a non-article type of thing (like this) provides a bit of a break from writing the regular types of articles.

I’ve done these meta types of posts before. In those posts, I pointed out ways you could help. None of you seemed all that interested in helping, so I’ll just skip that section this time around. If you want to help,  you know how to do so. If not, well… I’ll just keep doing it by myself. After all, I got us to the 200th post!

At The 200th Post Mark:

So, the site’s search engine traffic is growing slowly but steadily. In the past 28 days, I’ve had 3100+ visits from just Google. Overall, site traffic increases a little and we’re hovering at about 7500 unique visitors per month. They visit about 13,000 times each month. This excludes bot/scraper traffic, of course. I get quite a bit of non-human traffic but it makes no sense to include them in my records.

The search engine traffic is nifty. They’re most interested in:

screenfetch vs. neofetch
changing the default terminal
Ubuntu’s restricted errors

Those three pages and search terms (combined) make up most of the search engine traffic we get. We rank in the top 10 for a whole mess of keywords. I’m not quite sure how that happened, but I’m glad it did.

That traffic is mostly from the United States, with 80% of the traffic being Linux users – most of whom using Chrome as their browser. However, a large chunk (35%) are unknown browsers. 

The average user also spends about 3m 12s on the site. Excluding those visitors from search engine results, the most frequent referrer is Linux.org. Imagine that? I think that’d be expected. Also to be expected, Linux.org visitors tend to be repeat visitors more than any other visitors – and are so by a very wide margin.

Closure:

I’m not sure what other stats you’d be interested in. Long gone are the days where I visited more than anyone else (meaning the admin control panel was the most opened page). It hasn’t been like that since about a month after I got the site finished. If you’re interested in any other stats, I’ll see what I can dig out – just ask.

The search engine traffic amazes me. I’m always a bit surprised to see so many people using my site – with so few questions, meaning I must be doing something right. Once in a while I get a correction, and I always appreciate that. Google refers to my site as ‘high traffic’ but I’m not sure what they compare us with. Sure, most sites get no traffic, but we really don’t get that much traffic.

Anyhow, we’ve hit 200 articles as of this one – which isn’t really much of an article. Still, I’m gonna count it and let’s hope we get to 400! I suppose we just might get there, but it’s gonna be a long road with a whole lot more articles than I ever dreamed I’d write. So, we shall see!

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.

Running Away From Windows

There are many new Linux users, people interested in Linux, that are running away from Windows. Instead, what they should be doing, is running towards Linux. When asked ‘who should use Linux’, my answer would be ‘anyone that wants to’. But, in all the years I’ve been involved in the community, I’ve learned a few things about who is most likely to have more success. 

Today’s article won’t be tech or jargon, or even a how-to… It’s just a bit of a short essay about some observations made over the years. As I said above, I’ve learned a few things. Let me try to explain them as best as I can. (Besides, it’s a nice day to not do a how-to article. A change of pace is always a good idea.)

Important: I don’t want to seem elitist. This is not about elitism – it’s about your point of view and your reasons for the actions you take.

In fact, I figure pretty much anyone can learn to use Linux if they want to and they’re sufficiently motivated to do so. But, I find those that ask the most questions and need the most help are those who are running away from Windows instead of running towards Linux. The folks that are running towards Linux are the ones that read the documentation, search before asking questions, study the books, troubleshoot effectively, etc…

Let me try to distill this into easy to grasp concepts:

A person who is running away from Windows says, “I hate Windows! I’m switching to Linux!” 

A person who is running towards Linux says, “I’m curious about how Linux works, and I want to make it work for me.”

They’re two very different mentalities and, as one might expect, often have very different results. No, not always will the results be different – I’m speaking about averages and observations. It’s very much possible to run away from Windows while becoming a very proficient Linux user. The opposite is also true, you can run towards Linux and fail. This post just speaks to generalities. Outliers exist.

Running Away From Windows:

These folks tend to ask questions that can be easily answered. They rely on you to do the work for them, and expect to be spoon-fed the help they need. I saw a good example thread today where someone was asking about Python and when they were fed all the information they needed, they responded with “… Now what?”

These people fight with Linux rather than embrace it. They never take the time to understand that Linux is not Windows. They’re not that interested in actually learning to use Linux, they’re interested in not using Windows.

Six months later, they’re still  making the same mistakes only now they’re convinced that Linux is broken – and they have the answers about how to ‘fix’ Linux. When they wear out the welcome mat at one support forum, they’ll move to another. Odds are very good that they won’t use Linux for a full year before they quit. They’ll go back to Windows for various reasons, but mostly because they refused to learn. They’ll say things like how Linux is too hard, not ready for mainstream, or fundamentally flawed to the point where it’s not useful as a desktop operating system (even though many, many millions of us do so every day).

Think of it like a zombie movie… The people who are running away are the ones that get captured and eaten. They spend half their time looking back to see what’s chasing them. Their fear leads them to irrational decision making. They lack purpose, confidence, and cognition simply because of their mindset. It doesn’t have to be that way. What they could have been doing was running towards something – like a weapon and higher elevation.

Running Towards Linux:

Now these are the folks I prefer – and for obvious reasons. They’re hungry for knowledge and really eager to learn as much as they can. They’ll burn out, of course, but quite a few will make it through and maybe become proficient forum helpers themselves some day. You can spot ’em pretty easily. They have laser focus. That is, they have clear goals that can be articulated, and the drive needed to reach those goals.

They ask precise questions – questions that can actually be answered. If you want, you can just give them a few keywords and send them out searching on their own, knowing that they’ll do just that. They’re the types of people who try, try, and try again – and then ask for help about the specific area where they got stuck.

They don’t want to be spoon fed, unless they ask for a detailed answer. They don’t need to be spoon fed, because after reading your answer they either understand or they’ll go searching to find more information. They are ‘self-starters‘ with ample motivation.

I don’t want to say that these are the kinds of people who should be using Linux. After all, I think everyone can use Linux – provided they put the effort into learning. (I think people also tend to overlook how long it took them to become truly proficient with Windows, Apple, or whatever OS it was they have been using. They seem to expect their prior knowledge to be some sort of shortcut, even though it’s not that applicable ’cause Linux ain’t Windows!)

But, I will say that those people running towards Linux are more likely to have a better time of it, and remain a Linux user longer, than those who use Linux because they’re running away from Windows. If you’re going to decide to use Linux, make sure you have good reasons to do so. Run towards the goal, not away from a fear. The motivation behind switching to Linux matters.

Final Thoughts:

When you’re running away from something, you’re not making good choices. You’re not looking where you’re going. You stumble and fall and the zombies chasing you end up cracking open your skull to dine on the delicious gushy bits within. 

When you’re running towards something, you’re focused. You don’t just want success, you want to get there as rapidly and as best as you can. You want to know everything you need to know to win the race and you’re motivated to pull yourself up over and over again.

So, before you decide to give Linux a try, you should stop and think about why you’re doing so. Are you running away from something? If you are, maybe think about it a while longer and try Linux when you’re running towards it as a goal – and not when running away from something else as your priority.

The goals and priorities are very different for each mentality and you’ll have a far better time if you’re running towards Linux than you’ll have if you’re running away from Windows (or Apple, or Chrome, or whatever else you might be using).

Just some food for thought.

Me? I ran towards Linux because I wanted something new. I wanted new challenges – and a familiarity of the old (I was a Unix user for part of my life). Additionally, I wanted the comfort that comes from knowing my operating system is gonna be just fine and that I don’t have to worry about it. Plus, I wanted to experience Linux on the desktop as my sole operating system.

Learning new ways of computation was a goal, as was understanding my computer better. I’m happy for those choices and goals and every time I sit down at my computer, I’m still running to meet those objectives. Every day, I make certain to learn more about Linux than I knew the day before.

For the record, I don’t mind Windows users. They don’t concern me. If it works for them, it works for them. ‘Snot my job to change their views. If they want to run towards Linux, we’ll be here to help them. Use the tools you need to get the job done. If that’s Windows, it’s no skin off my back. My ego isn’t so frail that I need people to agree with me about desktop operating system choices. But, don’t switch because you’re mad at Windows, switch because you want to love Linux.

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.

Backup Optical Media To .iso

In today’s article, we’re going to learn how to backup optical media to .iso. If you have optical disks you want to backup, this is an easy way to go about it. It will not work with all disks, especially those encumbered with DRM.

This is useful for data disks, for example. It’s also useful for music CDs. It’s less likely to be good for things like game DVDs or movies. Those use various methods to stop you from copying your discs. While there are ways to backup some of them, this article won’t be getting into it.

Instead, we’ll just be using ‘dd’ for this exercise. If you’re unfamiliar with ‘dd’, it stands for:

convert and copy a file

If you’re unfamiliar with the command, you should pay extra attention to the way it is used in this article. It’s a powerful tool and using it with just the slightest error can (and will) make you run for your backups.

So, with all those things in mind, let’s learn how to …

Backup Optical Media To .iso:

This article requires an open terminal, like many other articles on this site. 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, we should probably figure out where your optical disk is. One way to find your optical media drive is with this command:

Inside the results of that command you’ll find something like “[sr0] scsi3-mmc” from which you can glean that /dev/sr0 would be your optical drive. With that information at hand, you’ll fun this command:

Be really sure that the path to save is correct, though this command is less likely to harm you than other ‘dd’ commands.

Anyhow, you can verify the integrity of the file created. That’s an easy enough step to take and looks a bit like this:

That should spit out two numbers. Those numbers should match. If they don’t, then something has gone wrong and you might want to try it again.

Closure:

There you go… Another quick and easy article. This one teaches you how to backup optical media to .iso, a handy skill if you want to preserve the data on the disks before they get worn out, broken, or lost. 

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: Show Hidden Files And Folders

Today, you’ll read an article that tells you how to show hidden files and folders (in Linux, of course). This is something everyone should know. This is a basic skill that you’re almost certain to need if you make the decision to use Linux.

Fortunately, it’s pretty easy to show hidden files and folders. You’ll see…

First, I should probably explain what hidden files and folders are. They’re files and folders that start with a period. So .foo.txt is a hidden file and .bar could be a hidden directory. One should remember that Linux is, by design, a multi-user system. With that in mind, having hidden files makes sense – if you don’t want those files to be accidentally (or maliciously) edited.

Any files or folders that begins with a period will be a hidden file. If you’re new to Linux, you might want to leave them hidden until you’re a bit more comfortable working with system files. Or not… It’s your system, you do what you want with it.

In a GUI file manager, you can usually figure out how to show hidden files and folders pretty easily. Sadly, it’s not universal in a GUI. Look in the right click menu, under the “View” option, or in the application’s preferences. It’s also often ALT + H and I want to say I’ve even seen it be ALT + F4. Look around, you’ll find it.

This article is more about showing those hidden files and folders in the terminal. It’s a really easy command and won’t take too long to explain it to you. So, enough preamble, let’s begin.

Show Hidden Files And Folders:

This article requires an open terminal, like many other articles on this site. 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.

We’ll stay right in the default directory, your home directory. If you’re not currently in your home folder,  you can get there with:

Your home folder should have all sorts of hidden files and folders. First, let’s see your home directory without showing the hidden files and folders:

Unless you’re in the habit of storing files in your home directory, you should have a fairly tidy list of folders and files that you’re likely already familiar with. 

Now, let’s try again – this time showing hidden files and folders:

Or, you can get a more easy to read output with this command (and you get more information with it):

If you want to see it in action, you can try this command:

Now, if you use the ls command you won’t see that file. If you use the ls -a command you’ll see the hidden file that you created called .foo.txt. This of works with directories, as they too can be hidden.

Yup, that’s it. That’s today’s article. See? I told you it was easy.

Closure:

Indeed, it is an easy article – and one most of my readers will already know. This one is aimed squarely at the new user who has yet to learn how to show hidden files and folders. It’s a pretty important skill to learn, and it’s also important to know which ones you probably shouldn’t edit. So, judicious use is important.

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: Free Some Disk Space By Deleting Old Logs

In today’s article, we’re going to free up some of your disk space by deleting old logs. It’s a relatively safe and easy thing to do, and can free some space up if you’re running low. Unless there’s a problem, you really don’t need a bunch of old logs kicking around and taking up space.

There are other reasons for deleting old logs, such as keeping things tidy or even ensuring old activities aren’t easily discovered by browsing old log files. You may have done some debugging and now want to start with a new slate, so there’s another reason to delete logs. 

Who knows what motivations you’ll have, but today we’ll be covering how to do it. The tool we’ll be using for log cleaning is ‘journalctl’, which is used for (according to the man page):

journalctl – Query the systemd journal

While ‘journalctl’ is a pretty nifty tool, we’re only going to scratch the surface. This article is only about deleting old logs and ‘journalctl’ is just the tool we’ll be using. If you want an article about all the features of ‘journalctl’, this is not that article. See? I’m saving at least a few people some time!

Anyhow, this article obviously requires a distro that uses ‘systemd’. If you don’t have ‘systemd’, you probably don’t have ‘journalctl’ and you’ll have to find another way to delete your logs. As most mainstream distros are using ‘systemd’, there’s a pretty good chance that you have ‘journalctl’ available.

So, with all that preamble gibberish out of the way, let’s go about …

Deleting Old Logs:

Like oh so many articles here, this one requires an open terminal. Why? Because of course it does. 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.

Now, with your terminal open, let’s have a look and see how much space your logs are taking up. You can do that with this command:

Now that you’ve seen how much space your logs are taking up, there are a couple of commands you can use for deleting old logs. If you want to go by space, you can use this command:

You can edit the ‘100m’ to whatever suits your needs. You can also use ‘g’ for gigabytes if you’d like to keep using that much log space.

If you want, you can also delete your old logs by the day. Let’s say you want to retain the last 3 days of logs. Well, that command would be:

I suspect you can figure out that the ‘d’ stands for ‘day’ and the 3 is how many days. You can, of course, change that to any number of days you wish. If you want, you can even use ‘w’ for weeks. Though, if you’re deleting log files to clear up disk space, you’re probably going to want to trim the logs even more than that.

Anyhow, when you’re done running one of the cleaning commands from above, you can verify that the space has been cleaned by running the very first command listed. That will do exactly what it did the first time you ran it – it’ll tell you how much space your logs are taking up. If they’re still not small enough for your liking, feel free to edit and run one of the above commands a second time.

Closure:

Well, there you have it… You have another article! This time I tell you how to go about cleaning old logs from your system. It’s a handy skill to have, though most folks probably have ample disk space – except those running on stuff like Chromebooks or the likes. If you’ve gotta live within 16 GB, you’re going to want to keep your logging to a minimum. Also, I still haven’t skipped a day from writing articles. It seems likely that I’ll do so eventually!

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.