This is a repository for the thoughts, notes, and achievements
of Mr. Jacob Hume. It contains posts on a large variety of
subjects, technical and otherwise.
Every piece of hardware I have seems to have its own built-in sound device.
Thunderbolt docks, USB3 hubs... even HDMI and display port carry sound. On my
laptop, I only want to use a few of them - but every time I connect another
device, it becomes the default sound card.
After creating a whole host of backup DVDs, you might be faced with a dilema;
how to verify that each disk was burned properly. Backups aren't backups until
they are tested!
I use rsync to back up many servers and other machines. Because of my very
different sources and targets, I have a collection of very complex bash scripts
that manage these backups. When I moved one stage of these backups to a new
server, it started behaving strangely - and it was difficult to discover why.
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.