Since that Parnell is most recently known for Jerry in Rick and Morty, I feel like we’re missing out on “Star Trek: Jerry”

Picture it: Alpha Quadrant, 3070. Captain Jerry Smith’s is one of the few ships to survive The Burn.

Captain Jerry: I just kept maintaining course and speed at full impulse, and it just kept working.

The Doctor didn’t consider that in “Phage” and I only recall VOY using the transporter buffer trick once when they had to hide the telepathic crew members when they’re traveling through Devore space.

Lizard babies, space cheese that makes the ship sick, yeah, I could see this going down in VOY.

I feel like this is the kind of joke Frasier would have told Freddy when he was a kid.

I read the punchline as “Frasier: In Space!” and would watch that.

Twice a year I fill in as DBA when our lady graybeard Oracle DBA takes vacation. This month is one of those times. Yay me.

For my org, it’s just the massive in-house developed line-of-business application that’s tightly coupled to Oracle that keeps us chained to it. It’s technical debt from top to bottom, and has been accumulating steadily since the early 2010s, but no one seems willing to start replacing it.

The new projects typically go with Postgres, MariaDB, or if all else fails, MSSQL. But the Oracle monster in the closet isn’t likely to leave any time soon.

I thought I was above enjoying all of the really campy episodes, but apparently not. I thoroughly enjoyed “Rascals” just for the Guinan / Ro Laren sass.

If they took Subspace Rhapsody to Broadway, I would happily make that my first show.

and That Puppet Episode

I was ambivalent about “Those Old Scientists” and bringing the LD cast in as live-action characters. Ended up loving it.

I was ambivalent about “Subspace Rhapsody” and a musical episode in general. Also loved it.

I was initially ambivalent about the puppet episode, but if history is anything to go by, bring it on.

I dunno. It’s at least a tie with the time he got to eject Solok from the baseball game. Look how happy he is there.

lol. My guess would be either really, really long and covers every possible scenario or extremely short and brutally honest.

Security is pretty minimal, not gonna lie.

There’s a 50 GB LUKS partition that stays locked unless I’m actively using it. It’s got backup copies of my important/critical documents and password manager exports but the rest of it is just media and doesn’t really merit encryption.

All applications have local accounts but I’m not using LDAP or any kind of SSO like I am with my main stack.

At home, I keep the firewall disabled on the interface configured as “WAN” so I can access its services directly via their hostname (I point its wildcard DNS record to its local “WAN” IP) but do enable firewall when I’m using it on an untrusted network. Granted, I have to manually remember to do that, so that’s kind of a security risk if I forget. Generally, though, when I’m using it remotely, it’s using my secondary phone as a USB-tethered uplink so even if I leave its internal services exposed to WAN, the NAT from the phone blocks that. One of my goals, eventually, is to automate some of the firewall rules depending on where I’m using it.

I addressed that in a few ways:

1. I bought a quality SD card to start with. A 1 TB card is a lot of eggs in one basket so I wasn’t about to cheap out on that part.
2. The board has 32 GB of eMMC which is where the OS is installed
3. There are very few writes to the SD card during normal operation (after initially loading content onto it). Running data (DBs, caches, log dirs, etc) for most applications is stored on the eMMC rather than the SD card or in some cases written to tmpfs (logs).
4. The subset of content I loaded onto this from my main media server was all chosen because it has the most re-watch potential, so re-loading close to a TB of media isn’t something that’s going to happen too often. The largest write it sees is the semi-annual refresh of the full ~130 GB Wikipedia ZIM dump, but I may push that back to once a year. I’ve only updated it twice so far.
5. Armbian assumes it’s going to run from SD card and does a pretty good job about minimizing the number of writes. Logs are all written to zram and only occasionally written to disk, it has no swap file, etc. If those are good enough to keep an SD card happy, they should keep an eMMC even happier.

Basically, I tried my best to configure the SD card so that in day to day use it’s WORM (write once, read many) without actually going so far as mounting it read only. The data that gets synced daily from my main servers is incremental and usually has few changes.

I’ve had PIs running for years without issue with the SD card mounted read only and retired them from service before the SD cards ever started showing issues. My Meshtastic EAS Alerter project is using one of those Pi Zero W2’s I retired from an older project and its 6 year old SD card.

This is actually the second iteration. Originally I attached a 1 TB SSD via a USB->NVMe enclosure. That worked, but also made the unit sprawl which was something I wanted to trim down in the final version. It worked but had random glitches and instability that I initially chalked up to the board and/or Armbian. I didn’t realize it was EMI from the Wi-Fi coming in through the USB cable until after I switched to the 1 TB SD card. That’s why I added some ghetto shielding to the power cable for lack of having ferrite beads on hand lol.

Should the SD card prove problematic over time, I can always go back to the USB->NVMe solution and lose its “keychain” form factor.

   /_\  _ _ _ __ | |__(_)__ _ _ _  
  / _ \| '_| '  \| '_ \ / _` | ' \ 
 /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|
                                   
 v25.11.2 for BananaPi BPI-M4-Zero running Armbian Linux 6.12.58-current-sunxi64

 Packages:     Ubuntu stable (noble)
 Updates:      Kernel upgrade enabled and 52 packages available for upgrade 
 WiFi AP:      SSID: (BananaAP), channel 6 (2437 MHz), width: 20 MHz, center1: 2437 MHz
 IPv4:         (LAN) 192.168.5.1, 10.10.10.15 (WAN) 192.168.1.12
 Containers:   postgres_postgres_1

 Performance:  

 Load:         4%           	 Uptime:       18 weeks, 22 hours, 49 minutes	 Local users:  2           	
 Memory usage: 45% of 3.83G  	 Zram usage:    74% of 1.91G  	
 CPU temp:     63°C           	 Usage of /:   35% of 29G    	
 RX today:     6 GiB  

Ha, yeah, that UPS board isn’t going on any plane. I’d just use an approved power bank in that case.

I have that same remote/keyboard and love it.

Had the same problem and similar solution with some LED candles since I kept losing the little mini remote. I taught C1 from the power button on the candles’ mini remote. It would turn them on, but not off. So I had to make C2 the “off” command by learning it separately.

I have absolutely no frigging clue why that works the way it does. You’d think it would be the same signal either way, but something is definitely different.

So far, that’s the only device that acts like that. I programmed the power and directional buttons to control my Eufy robo vac, and those work as expected. The buttons above C1 and C2 work to toggle power (left button) and cycle thermostat settings (right button) on my electric fireplace correctly as well.

Had to go out of my way to find the Betty White one.

Yep. The QR code is only the encoded BT address to make connecting in the app easier than…selecting it from a list.

I thought about that, but one of the safety features of these batteries is an active fire suppression system that fills the interior with some kind of fire-extinguishing foam. I’m terrified to try to take these apart for fear of somehow triggering that. Plus, they’re hella expensive lol.

My house batteries for my PV system are also susceptible to this. Ugh.

They’ve both got Bluetooth for monitoring and configuration. Some config changes require a PIN but not the settings to enable/disable charge and discharge. Someone could just get within range of them, install the official app, and set discharge to “off” and shut down my house.

I’ve also not found a way to disable bluetooth on them. Gonna have to put them in a damn Faraday cage if I decide to worry about that possibility. :sigh:

Lol, that would certainly make the station regulations much more concise.