Once upon a time, my websites originated from a couple of well-known hosting providers. During those years, I regularly needed to log into the servers that hosted my web sites to change or upload a file. For the longest time, I did that using FTP, but stopped because the passwords are sent in plaintext. Wasn't that reason enough?
While I often used FileZilla for secure connections, it was overkill when I needed to change or transfer one file. Instead, I turned to the command line and used SSH and SCP. Both offered me a level of security that FTP didn't. Why? They create an encrypted connection with a server — no plaintext is allowed.
Let's take a quick look at SSH and SCP.
Note: This post isn't a comprehensive guide to SSH and SCP. It's a quick and dirty introduction for someone with few technical skills. What you read here will help get you going. You can get more information from a number of sources, including this one.
It's been seven years since Google pulled the plug on Google Reader. Seven. Years. And, believe it or not, there are people who are still whining about that. Some of them even say that by sending Reader to the digital glue factory, Google killed RSS.
RSS isn't dead. Far from it. RSS is still a great way for you to take control of the information you ingest from the online world. You choose what you want to read, not an algorithm.
All you need is a good RSS reader. If you want to go back to basics with your RSS reader, a solid option is Newsboat. It's a command line feed reader, forked from the venerable Newsbeuter, that's easy to use but packs a good number of features.
I've never been much good at keeping a journal. I've tried. Believe me, I've tried. It's just never worked out. Chalk part of that up to laziness and part of that to the belief that little in my life is worth chronicling.
Every so often, though, I take another kick at the journalling can. This time around, I went back to a command line app that I tried and liked a few years ago. That app? jrnl. It's a quick, easy, and minimalist way to keep a journal. Let's take a look at it.
To install jrnl, you'll need Python and a tool called pip installed on your computer. If they aren't installed, do the deed using your Linux distribution's package manager.
Open a terminal window and run the command pip install jrnl. It should only take a few seconds to install.
One of the great things about the command line is that you can do just about anything there that you can do within a graphical environment like GNOME, KDE, xfce, OpenBox, or whatever window manager you use. Sometimes, you can do it faster and more efficiently.
One of the tasks I do at the command line is renaming and deleting both files and folders. That's often because I've converted or combined files and need to change their names or get rid of the ones that I don't need any longer.
There are three commands that let me do that quickly and easily. Let's take a look at how to use them.
Just to spare you the pain, I won't go into my usual spiel about how useful the command line is. It is, even for the non techie.
In the terminal window, there are so many commands and so little time to learn them all. And there are so many little tips and tricks that can make life (or even just a visit) to the command line a bit easier.
Let's take a look at a few of my favourite tips. If you've been using the command line for any length of time, these tips will probably be old hat to you. But if you're still learning about the Linux command line, then you might find these tips useful.
(Note: This post was first published, in a slightly different form, at Opensource.com and appears here via a Creative Commons license.)
There are dozens, if not more, tools out there that can help you manage your ever-expanding task list. If you want to manage your tasks like a techie, or just feel like going back to basics, the best way to do that is to turn to the command line.
With the software that's available, there's no reason why you can't effectively manage your tasks from the command line. You don't need to worry about sacrificing features and functions, either. The three task management tools I look at in this post have something for everyone.
For most people (especially non-techies), the act of writing means tapping out words using LibreOffice Writer or another GUI word processing application. But there are many other options available to help anyone communicate their message in writing, especially for the growing number of writers embracing plain text.
There's also room in a GUI writer's world for command line tools that can help them write, check their writing, and more — regardless of whether they're banging out an article, blog post, or story; writing a README; or prepping technical documentation.
Here's a look at some command-line tools that any writer will find useful.
When I tell people I have 10 thumbs when it comes to anything technical, they don't believe me. In fact, they point to all the articles and blog posts I've written about using the command line to try to refute my claim.
I'm no expert or wizard with the command line. Far from that. And I'm not one of those people who believes that you absolutely must be fluent in command line/shell/terminal (or whatever you want to call it) to be able to use Linux. I know any number of folks who happily and productively use Linux. Not one of them have ever cracked open a terminal window.
So why do I write about the command line, especially in posts and articles aimed at those without many (or any) technical skills? Aimed at people like me? Two reasons.
Second, you don't need to be an expert to use the command line. You don't need to know how to script. You don't need to remember ever option for every tool that you use. You only need to remember the options that you need to remember, nothing more.
Yes, anyone can use the command line.
That said, being able to use the command line isn't a requirement for using Linux. But using it can expand what you can do with Linux.