As a person who uses Linux regularly, often I am asked about my opinions about other operating systems, especially those coming from large companies located in Redmond, Washington. Here's the deal. Operating systems are tools. We use them to do jobs. It is always a good idea to think critically about what tools you are using, and verify if other tools can do the same job in a more efficient or flexible manner.

To see the interrupts occurring on your system, run the command:

If you use sudo to run commands as root, you've probably run into “permission denied” problems when only part of a pipeline or part of a command is running with root permissions. This fails with “permission denied” because the file is writable only by root:

When writing bash scripts you sometimes need to run commands in the background. This is easily accomplished by appending the command line to be run in the background with an ampersand "&". But what do you do if you need to run multiple commands in the background? You could put them all into a separate script file and then execute that script followed by an ampersand, or you can keep the commands in your main script and run them as a sub-shell.

If you're anything like the average System Administrator, you are understaffed, underfunded, and overworked. By now, you've also gotten used to the idea that no one knows you exist until the mail server goes down, then you're suddenly on America's Most Wanted. In this article, I'm also assuming that you have many servers that you are responsible for. I'm also assuming

Keeping the files on multiple machines synchronized seems to be a recurring problem for many computer users. Until I discovered Unison (https://www.cis.upenn.edu/~bcpierce/unison/) I never really had a completely satisfactory solution.

If you come from the world of Windows, you undoubtedly understand the concept of a shortcut. In the Linux world, shortcuts do exist, but they're generally referred to as symbolic links, or symlinks. They are so named because, like shortcuts, a symlink is really just a symbolic placeholder or link to the file or directory you're trying to get at.

If you need to deploy hundreds of server or client nodes in parallel, maybe on-premises or in the cloud, and you need to configure each and every single one of them, what do you do? How do you do it? Where do you even begin? Many configuration management frameworks exist to address most, if not all, of these questions and concerns. Ansible is one such framework.

Bring your GitHub repository to the next level of functionality.

How to create your own search engine combined with a crawler that will index all sorts of documents.