Quick Tip: Little Snitch first-run

I finally got around to purchasing and installing Little Snitch today. I should have expected this, but upon first launch (after rebooting the computer) Little Snitch went crazy with the snitchin’. A couple of quick tips to make this go a little more smoothly:

  • You are going to have to choose to approve or disapprove many background processes, many of which request some pretty shady-sounding URLs. If you only approve them “Until Quit,” they will go into a list of “Temporary Approvals.” At this point, you can go through that list at your leisure, making the rules permanent, leaving them temporary, or denying them permanently as you see fit.
  • Although Little Snitch comes with reasonable defaults for Safari and Mail, it does not come with anything for Chrome or Firefox. If your web browser of choice is launched on startup, create the same rules for it as already exist for Safari; this will save you a lot of clicking. Additionally, Mail does not come pre-approved for ports 80 or 443. When it tries to render HTML messages, you will see popups. If you already are OK with HTML messages, might as well copy those rules (open port 80, 443) from Safari over to Mail as well.

Hopefully this saves you some time and clicking.

LVM, mdadm, and partitioning.

This is a mind-dump after an excruciatingly mind-numbing week.

Somehow, with a FreeDOS installer USB I managed to accidentally corrupt the LVM data on my RAID array. This thing has files on it that go as far back as 1994*, so I was reasonably upset about the loss. Fortunately the situation was resolved, but I wanted to leave some notes for the next time I have completely forgotten how LVM works with mdadm.

First, disks used in the mdadm array do not need a partition table. I remembered this and didn’t mess with the (functioning) raid array.

Second, LVM does not need a partition table when it is using an entire device. I forgot this, and went directly to “trying to restore a corrupted partition” instead of “trying to restore last-known-good LVM data as found in /etc/lvm/archive/”.

Using testdisk, gpart, etc is a BAD IDEA if your disk never had a partition to begin with. These tools will recognize that you have a file system on the disk, but they can’t figure out that it was an LVM-only construct. The result will be an unmountable, mis-sized, “partition does not start on a sector boundary” mess. As you can see from the answer to the question I posted on SuperUser, I actually had to zap the partitions I tried to create to be able to move forward.

Note: fdisk is for MBR, <2TB disks. parted is for GPT, >2TB disks.

* Even I am surprised by this! Apparently it is a Palm Pilot archive… that can probably be deleted, huh?

Good Old Disk Utility

If you have been sadly struggling with the new Apple Disk Utility software, I can confirm the instructions on this page work to restore the old Disk Utility. I can make no claims as to the reliability of running the old Disk Utility on El Cap, however.

https://justus.berlin/2015/10/restore-old-disk-utility-in-os-x-el-capitan/

Replacing drives with mdadm

Simple, but very helpful.

SATA hotswap drive in mdadm RAID array.

I usually am just swapping out failed drives, which is pretty simple when you are running a spare. However, to increase the size of the array I need to swap out otherwise healthy, running drives. An easy but nerve-wracking procedure.

Remote linux-based Time Machine using netatalk instead of smb

Update 2015-12-12: The info in this post is no longer correct; you can now simply follow the instructions on this ubuntuforums.com thread, particularly this post on Dae’s blog to get Time Machine up-and-running. 😄

If you previously followed my instructions, to back out of the home-built netatalk, you can try the following:

sudo apt-get remove netatalk
cd /usr/local/src/netatalk
make uninstall

Then follow the instructions posted above.


My large file server once was able to act as a Time Machine provider over-the-air, back before Apple disabled the ability to use Samba shares as Time Machine disks. However, following a few simple instructions from these helpful folks below, I was able to make OTA Time Machine backups happen again.

Thanks, Daniel and Pepijn!