Sometimes I need to uncompress large archives located in remote locations - for
instance, in Amazon S3. Most normal approaches to uncompressing archives involve
resource-intensive processes, like downloading the entire file into memory - an
approach not tenable for multi-gigabyte files.
Whitespace causes lots of interesting issues with the command line - whether
it is present in file names, arguments, or any other data flowing between
commands. Quoting can help, but there's some very particular edge cases I've
encountered in my scripts.
As an enthusiast of encryption, it always felt a little strange that my servers
kept all of their data in the clear. But the problem with encrypting a headless
server is that, inevitably, you have to reboot it. So how do you connect to your
server and unlock the drive before it boots? It's quite the catch-22.
I often have a need for a quick virtual machine. Many of them don't require any
video output, so having a virtual monitor is a little overkill. Luckily, with a
few QEMU switches and brief configuration of the guest VM, you can view console
output in a standard terminal on the host system.