a report on retirement so far

It’s been seven weeks (since this past Thursday) when I “officially” retired from my current job. It’s been an odd passage of time, as I’ve been doing all sorts of little tasks, some of which have added up to bigger projects. And example of little tasks adding up is when I go puttering about in the garden. I will spend some time in an area trimming until I get tired of trimming. Then I’ll see some weeding or other bit of clearing that needs to be done. Then I’ll stop that after a bit and do some trimming. Or some transplanting. It all seems a bit disjoint at that level, but after about a month of doing that I suddenly noticed now much neater the entire garden seems to have gotten, even neater and trimmer than the same time last year. My level of satisfaction in the garden is considerable. I see green and many blooming flowers, and I’ve even begun to see some bumble bees flying amongst the azaleas that have been blooming since early January.

I’ve also noticed that my writing on the blog has once again fallen considerably. I wrote all those wonderful promises about how I wasn’t going to let that happen, and yet here we are. I was also supposed to use Ulysses to do my writing instead of sticking to the WordPress old-style web browser editor. And yet, while Ulysses allows the writing to just flow (I’m using it to write this), I keep going back to the web editor because it lets me do what I want to do to create my postings, which also means formatting and inclusion of photographs and other graphic images, which Ulysses doesn’t support very well. In particular I want the image in my WordPress site to be linked from within the post. I can add images to my writing and then upload the entire thing via Ulysses, but I can’t get Ulysses to create the necessary HTML link so that clicking (or touching) the image in the post will call it up. That feature is very handy with a screen capture, for example, when the reader wants to view the image in much greater detail.

I did finally mange to figure out how to pair my logi MX Ergo trackball with my iPad Pro 12.9” second generation. It turned out to be very simple using ipadOS 13.3.1. Now that it’s enabled it makes writing on the iPad that much easier, as I can rapidly and precisely place the text input cursor anywhere the document.

Other things of note:

  • I’ve lost weight (slowly) since retiring, and that’s with me not even trying to diet. I’m down about five pounds from Christmas, and the weight loss seems to be slowly continuing. Personally I attribute that to not eating any junk food or eating out for lunch. I eat nearly all my meals here at home, being careful to control refined sugars, salt, and keeping a reasonable balance of vegetables and animal protean in my meals. Back around 2000 I cut my red meat consumption down to an absolute minimum (there are still some amino acids I need), depending more on poultry and seafood for my needs. Nothing is fried. I either grill or sauté it on low heat, and minimally cook the vegetables if called for.
  • All the little critters are a lot more relaxed because I’m nearly always home. The only time I’m not home is when my wife and I are out on errands or doctor appointments. Otherwise I’m here with them. My cats in particular love when I’m sitting in my chair, as they now come up and stretch out on my chest, with their head up next to my jaw. Then they relax, close their eyes, and purr until they’re asleep napping.
  • I’m getting ready to sell one of the two Priuses. I figured this would happen as I no longer am commuting. When I do have to do a bit of travel, I just take my wife’s car. Her car has about 40,000 less miles on it than mine does.
  • My wife and I have cleared out a lot of stuff from within the house. We still have quite a bit more to unload, but what has been unloaded has allowed me to bring the middle bedroom back into use and to open the door so that it’s now a part of the house, which helps air conditioning and heating. I could have never done that while working, even part time there at the end.

I guess in retrospect I’ve been fairly busy. For example I can now go up on the roof every weekend and use my electric leaf blower to keep the roof under the live oak clean as well as the gutters, which means that the leaves are decomposing on the roof. It was extremely annoying in the past to just happen to look up and see seedling growing out of the gutters because of the leaf decomposition buildup. Which of course led to me raking up six 44 gallon bags of oak leaves, which got picked up today, along with two roll-around cans of full of crepe myrtle branch trimmings. I haven’t trimmed the crepe myrtles in the back yard in years.

Here’s to getting even more done, and the sincere hope that the retirement lazies don’t strike any time soon, if ever.

ugly surprises with raspbian buster and external file systems


A while back I wrote about adding an SSD to a Raspberry Pi 4 and modifying /etc/fstab so that it would automatically mount when it booted. This is different than having it automount through /media/pi, since that type of automount only occurs after the OS is fully up and then scans for attached devices, such as those on USB. For nearly all use cases you can’t tell one from the other. But for those very few use cases where you need the kernel to mount the attached storage device before the rest of the system comes up, you need to define it in /etc/fstab.

That wasn’t a problem with Raspbian Buster up until just recently. Before that time, I had an entry for my SSD in fstab that started out like this:

/dev/sda1 ...

It worked just fine, until one day after a recent update that included the kernel, it didn’t. No warning that this was going to happen, none at all. After the update and subsequent reboot, the Raspberry Pi refused to boot, and instead dropped me into a prompt waiting for me to log in as root to fix the problem. Oh, wait, root is disabled by default in Raspian, so that just put me in an endless boot loop.

It took two attempts rebuilding a minimal boot micro SDXC before I finally figured out what was happening. Fortunately, that second micro SDXC card was a new one with a minimal Raspbian system, so it didn’t take too much effort to see that adding the entry to /dev/sda1 was causing it to fail to boot. Fortunately for me I have other Linux systems (my ten-year-old Samsung R580 running Ubuntu 18.04.04 came to the rescue) that allowed me to mount both micro SDXC cards, edit fstab and remove the entries. Once removed, both micro SDXC cards booted just fine in the Raspberry Pi 4.

Once I got back in I enabled root with ‘sudo passwd root’ and gave it a password. Now, if I have a problem where a Raspbian boot failure wants to dump me into the root account in single user mode, I can actually log in at that point.

The other problem was getting the USB SSD to mount. Here’s what I did to fix that. But first, a tiny bit of background.

The kernel in Raspbian buster uses what’s now known as a PARTUUID to identify a storage device instead of the old school device name in /dev. To find out what that PARTUUID is, you have to run this command at the command line in a terminal window:

pi@rpi4-4-01:~ $ sudo blkid/dev/mmcblk0p1: LABEL_FATBOOT="boot" LABEL="boot" UUID="69D5-9B27" TYPE="vfat" PARTUUID="d9b3f436-01"/dev/mmcblk0p2: LABEL="rootfs" UUID="24eaa08b-10f2-49e0-8283-359f7eb1a0b6" TYPE="ext4" PARTUUID="d9b3f436-02"/dev/sda1: LABEL="SSD" UUID="ad89d540-a007-4d0a-887b-0b0dbefe3e8e" TYPE="ext4" PARTUUID="937a0120-01"/dev/mmcblk0: PTUUID="d9b3f436" PTTYPE="dos"

Since I already know the label on my SSD is “SSD” it’s quickly identifiable in blkid’s output. Copy the PARTUUID at the end of the entry, and use that in the fstab entry for the drive, like so:

PARTUUID=937a0120-01 /ssd ext4 defaults,auto,users,rw,nofail,x-systemd.device-timeout=30 0 0

Note that the quotes are not added to the entry. Also note all the flags I use, especially the shortened timeout (systemd.device-timeout=30) to shorten the wait during boot in case the SSD isn’t plugged in. The default is 90 seconds.

The primary reason I want the SSD mounted is because that’s where I put swap. In /etc/dphys-swapfile I add the following line:

# where we want the swapfile to be, this is the default#CONF_SWAPFILE=/var/swapCONF_SWAPFILE=/ssd/swap

I want my swap on the SSD because testing has shown the SSD is an order of magnitude faster than the boot micro SDXC. I use the Raspberry Pi 4’s as development and native build machines, rather than set up an emulation and cross-compile tool chain on my Mac. Believe it or not, it’s a lot simpler the way I have it set up. This is a decent compromise that doesn’t require me to put the entire OS on the SSD and then configure the Raspberry Pi to boot off the SSD. There are some significant problems with that, such as the Rasberry Pi 4 wasn’t set up to do that for quite some time after its release, and the fact that once configured that way, you can’t go back. So I put swap on the SSD, then cd onto a work area on the SSD and develop and build away.

This all gets back to the bigger question: why did this change, and when did it change? I use the same type of setup, and the same SSD, on the Jetson Nano, and it’s running a tweaked version of Ubuntu 18.04.04, complete with the Ubuntu graphical desktop. The fstab entry for that is the regular device entry, /dev/sda1.

Oh well. I just keep reminding myself that this is just a hobby, and I’m retired.