Since the 70’s, Vi is one of the programmer’s best friend. Nevermind you’re new to Vi or not, here’s a big list of 100 useful commands, organized by topic, which will make your coder life better.

To use Linux nowadays, you don't have to touch the command line to get going. This may be true.

Today's post is yet another in a somewhat disjointed series of posts on "stuff you might not know and you might find interesting" regarding very common commands. And they don't get much more common than the "who" command.

The primary reason for writing this is to help new users develop an understanding of the Linux file system commands. Not all of them, just some of the more common ones. Let's look at what they do and why I would need to use them, what not to do, what each thing means and what it's for.

Unix systems provide a number of commands to manage files and directories. Their strong point is the ability to use them in a rather simple manner against a group of files/directories meeting certain conditions. For example all the files satisfying specific criteria can be deleted or have their names changed en masse.

There is always a time when working with the CLI that you will want to find a set of files by name, such as all JPEG images. The `find` command lets you do this and more. Let’s jump into the basic structure of a find command:

In an attempt to find a good Unix reference for you FOSSwire readers, I was unsuccessful at finding a decent one on the Internet. So, why not make one?

Linux has come a long way in the past two years. Today much of what needs to be done on a Linux machine can be done using a mouse and a little pointing and clicking. Occasionally, however, there are things that still require a little under-the-hood tinkering, where a rudimentary understanding of the command line comes in handy.