Author: Michael Lucas

Writer. Sysadmin. Owns this site.
Posted on

February’s Febrile Sausage

This See the Sausage Being Made post goes to Patronizers in February and becomes public in March. Not a Patronizer? You could be! $12 a year gets you my latest updates, occasional free tidbits, and the completely pointless MWL Footnote Fortune File, freshly updated for the new edition of Networking for System Administrators.

Yes, I just published a StSbM post last week, but I need to get back on track and I have news.

Most importantly, I’m making some words. The writing in the original ZFS books isn’t bad, but it could be better, so generally applicable ZFS discussion is getting redrafted. The FreeNAS miniXL makes a fine test server, and I’m even discovering FreeBSD bugs through bhyve. (The docs say you can install FreeBSD 15 with 256 MBRAM, but for a ZFS install you need at least 350MB to install from packages on ISO. I’d call this a doc bug rather than an OS bug, because if you’re running ZFS on a host with less than 350MB RAM you’re daft, but reducing pkg(8) memory usage is worthwhile.) I’m fixing some of the inconsistencies and standardizing language for certain concepts and tools, which I really should have done the first time around but nobody noticed so I guess we got away with it and that’s all that matters.

The challenge for this book? Linux. ZFS considers Linux a Tier 1 platform, but Linux does not consider ZFS a Tier 1 filesystem. ZFS works. You can install it. But there’s no standard way to use ZFS as a root filesystem on Linux. Many people maintain constantly evolving hacks to support ZFS on root. Some variants added support to the installer only to remove it. Proxmox uses ZFS as its primary filesystem, but very few people run Proxmox on their laptop. I think the majority of the book must assume that Linux users have their root on extFS and data disks with ZFS. It seems that ZFSBootMenu is the current leading Linux ZFS boot manager, so I’ll probably do a final chapter discussing that. Such chapters are the shortest-lived part of any book. Putting it at the end makes it easy to ignore when it becomes obsolete.

Which brings me to the big reason for posting this now: Eddie Sharam sent me the cover art. Behold, an ancient Mediterranean vase.

This is an actual painting, available for sale once the book is released, probably as part of the Kickstarter. I pay Eddie reasonably for his work, but making a living as a visual artist is even more fraught than making a living as a writer. If he can get a few bucks more, I’m all for it. Central front and back images mean that we’ll have to do some digital manipulation to make the spine work on the hardcover, but Eddie’s down with that. (No, I don’t digitally alter images. That would require visual skills I have no desire to develop.)

Last month’s cleaning efforts highlighted a problem that’s a decade in the making: my surplus copies warehouse.

The printer screwed up on the N4SA2e special editions, shipping me 32 regular hardcovers with the special dust jackets. I couldn’t use those for Patronizers, sponsors, or Kickstarters. They did, however, overwhelm my ability to ignore these shelves and force me to face reality. I need to do something with these.

The good news is, crowdfunding forced me to solve the problems of shipping.

I’m going to add them to the TWP bookstore, signed, at list price.

Parts of it will be clunky, because WooCommerce shipping is arcane and inflexible. I hired expert help to solve this problem. They failed, so I’m not investing more effort therein. All shipping will happen on Mondays, unless I fry my brain and can only perform a mechanical task. But between good shipping envelopes, a label printer, and my newfound skill in tape gun reloading, it’s manageable.

I have a handful of tech books, a whole bunch of Prohibition Orcs, and a scattering of novels. The troublesome one will be the chapbooks. I might do a “random chapbook, $5” add-on item. Short story roulette, anyone?

Patronizers, you get dibs. If there’s something you want, drop me a note.

Somewhere in here, I have to set up the 1 April Kickstarter. Yes, I’m doing another one. I promise it’ll be stupid. You might laugh. A handful of you will leap at it, probably as a gag gift. But it’ll amuse me as I’m scrabbling through the ZFS book.

I’m also looking at the production tools for the tech book after OpenZFS. The first edition of SSH Mastery was originally laid out in LaTeX. The PDF looked great. I sent it to the print-on-demand networks. Some indie printer, somewhere in the world, choked on its lack of Adobe-specific and Microsoft-specific gunk. The book was pulled from distribution globally because one location had trouble. I had to hire someone to redesign it in Adobe InDesign, and quickly. Afterwards, I had to dive into the InDesign gutter myself.

That was sixteen years ago.

Are those printers still running in Farawayistan? Perhaps.

But other people are reporting good results replacing both Adobe and Microsoft Office with LibreOffice in producing complicated books. I’m seriously considering trying it for the next tech book. This has risks. If one printer in Farawayistan can’t print the book, distributors will yank the book from distribution globally. I’ll have to redo the book in InDesign, and perhaps even in Office. Sponsors and Kickstarter backers have changed buying patterns, though. I need to produce books for signing in the US, and books for dropship in the US, UK, and Australia. My printer (today) is Ingram. Ingram maintains its printers in those locations quite well. I expect to print those easily.

Worst case: I release book for wide distribution, some printer can’t handle it. I redo it in LibreOffice/InDesign. If that fails, I convert everything to Office and InDesign and start over. My hardcore readers will get the book on time. The rest of the world waits an extra month for print.

The worrisome thing is opening old InDesign files, but I have a license for the Affinity suite. Not the new subscription model, not the newer freeware trap, an actual “you bought this software and can use it forever” license.

Truly, I’d love to be rid of Adobe. And Microsoft. And Adobe. Adobe.

I better sign off before I choke on my own rage. Thank you all for your support, it means the world to me–especially in these times.

Posted on

Talking at NYCBUG 1 April 2026

A few days ago, Patrick McEvoy said that NYCBUG had no topic for their 1 April meeting and asked if he could persuade me to present something, anything. Anything at all.

Anything? ANYTHING? On April Fools’ Day? The day I’m launching my next Kickstarter? The fact that I had absolutely nothing of worth did not dissuade me–indeed, it never has.

I’ll be presenting “What’s Changed Since The Last Time I Came this Way – a talk that was supposed to be about OpenZFS.”

Michael W Lucas and Allan Jude are busy working on a new OpenZFS book, which means not only documenting everything that’s changed in the last 12 years but discovering everything that they got wrong the first time. The quest for accuracy has taken Lucas deep into mailing list archives, Usenet, VAX installation manuals, the Kremlin’s first Internet connection, the United Nations’ effort to merge the BSD projects, and the ULTRIX and S51K filesystems, and left MWL more convinced than ever that filesystems are nothing but a April Fools’ prank. This hurriedly conceived and hastily assembled talk will update you on new OpenZFS features, but will also try to determine if it’s a good prank–or not.

Michael W Lucas’ name may ring a bell for some in the BSD community. He’s written several shelves of books. But for anyone who has seen him speak in public during Ante COVID days, it was clear they are mere transcriptions of his rambling presentations. For this NYC*BUG meeting, he is unlikely to edit out any of his expected corny jokes we endure during his conference presentations.

More likely, you know his name from his grotesque horror fiction. In the same way his technical books are just transcriptions of his presentations, his fictionaal horror is just a simple reflection of someone who lives in a haunted house filled with (pet) rats in Detroit.

18:45 EDT or 22:45 UTC. The talk will be streamed, so you can catch it from anywhere. Instructions are on the NYCBUG web site.

Posted on

FreeBSD security report on successful logins

By default, FreeBSD sends a daily security report listing all sorts of good stuff, and failed logins.

I don’t care about poorly-programmed password gropers fumbling at a service that doesn’t accept passwords. I don’t want to read pages of stupidity. Over the years I’ve trained myself to skip the stupidity, which is bad practice. If I get automated email it better contain only things I care about.

I care about successful logins. The number of folks who log onto my hosts is minuscule. I want to skim a short list of logins, recognize them all, and move on with my day.

I’ve trivially modified the failedlogin script to recognize successful logins. No, I’m not going to put this on github. I quit using github several years ago.1 Drop it into /usr/local/etc/periodic/security and enable it in /etc/periodic.conf.local.

security_status_loginfail_enable=NO
security_status_loginsuccess_enable=YES

This only catches SSH logins, though. If anyone has suggestions for improving the regex catching assorted logins for the services you use, I’m open to it.

Will I submit it as a PR? Uh, maybe? Depends if anyone cares.

Posted on

Original N4SA2e cover art for sale!

The original cover painting for Networking for System Administrators, 2nd edition is on sale at my bookstore.

Minimum price is $600, but I’m sure Eddie would appreciate a couple extra bucks if you’ve got them.

I make nothing on this. Your entire payment (minus processing fees) goes to Eddie and he ships you the painting.

There’s only one, so grab it quick if you’re interested.. As an aside, this is the first time I’ve enabled stock management on my store. Supposedly this will disappear immediately when someone buys it, but I’ll be watching on the off chance it doesn’t.

Posted on

Fundraising Auction Over

The fundraising auction is over.

Seth Hanford won with a bid of $777. I wouldn’t normally declare 777 to be a suitable solution to any problem, but I am compelled to sign off on this one.

Seth, send me your receipt and you will get your pig in a poke–uh, your prize. I don’t care which of the suggested charities you donate to, they’re all worthy.

By the way, spectators and other bidders: the anonymous person who bid $550 also donated their bid to charity. If you felt like doing the same, they’d appreciate it.

Posted on

Kansas or Minneapolis Fundraiser

My country is in trouble, and I’m just a tiny rat dude making a marginal living writing about stuff very few folks care about. Not much I can do directly.

My 1 April Kickstarter required some unusual tests, so I produced a physical artifact of interest to a certain subset of sysadmins. I have that artifact. It’s a real thing. I have to make a couple tweaks and add tidbits here and there, but the thing exists.

You want proof it’s real? Here you go!

Mildly redacted to preserve the surprise. Also, this photo is legitimately a hint.

Folks have started asking what it is. I’m not saying until the Kickstarter launches.

I am, however, auctioning off the prototype for charity.

Yes, I’m asking folks to give money for a sysadminny thing sight unseen. The money doesn’t go to me, however! I want you to support a worthy cause. I have a choice of worthy causes: supporting Minnesota folks trapped by ICE, or helping trans folks in Kansas.

What do you get?

When you send me the receipt for your donation, I will mail you the thing and send you a Kickstarter preview link. I will also include a letter declaring that your direct financial support of charity grants you moral superiority. Once the final product escapes, I’ll ship you one of those. So really, the physical good will be unique for only a few weeks.

Intangibly, though? Ah, the intangible benefits! BRAGGING RIGHTS. You’ll know what the thing is before anyone else! You’ll have grounds to call me a dumbass before anyone else! People will call me a dumbass anyway, but your comments will be evidence-based and thus folks will take you seriously.

I will pay for standard Priority Mail shipping. That’ll be three days within the US, and a couple weeks overseas. (If you’re outside the US and want fast shipping, I’ll ask that you send me a few bucks for the upgrade. Sorry, but overnight to Germany or Australia ain’t cheap.)

All I ask is that you don’t ruin the surprise for folks. If you blab, I can’t do much. Sure, I’ll never do a fundraiser like this again and I’ll call you a jerk, but that’s about it. Unless you live within wedgie distance.

I am, of course, perfectly fine if you post something like “holy crap Lucas is a jerk this thing is a total ripoff like I’ve never seen before don’t you dare go to https://mwl.io/ks and follow it you’ll only encourage his next lame travesty.”

Bid by leaving a comment on this page.

The auction runs from now until 5PM EDT on 9 March 2026. If the bidding goes nuts in the last few minutes, I’ll leave it open until it settles down. There’s no sniping this auction at the last moment, as I want bids to escalate beyond all sensible limits.

The winner gets to pick a charity off of https://www.standwithminnesota.com/ or Trans Continental Pipeline and donate their bid. Send me the receipt and I’ll send you the thing. I want you to be able to enjoy knowing the secret for as long as possible, so I’ll ship it ASAP.

Bid early! Bid often! Bid to be the first one disappointed!

Posted on

January’s Jammed Sausage

This See the Sausage Being Made post goes to Patronizers in January and becomes public in February. Not a Patronizer? You could be! $12 a year gets you my latest updates, occasional free tidbits, and the completely pointless MWL Footnote Fortune File, freshly updated for the new edition of Networking for System Administrators.

I have one “job.” Yes, I write books. I get paid for that. But the thing I get a “paycheck” for is writing one blog post a month, at the beginning of the month. For Patronizers.

Here we are at January 28, and I am just getting to writing that blog post.

Absolutely zero excuses, only a procedural failure.

I like to write the blog post when something happens. What happened in the last six weeks?

Nothing.

Well, there’s The Longest Dark, the orcish solstice holiday. I took time off for that. Come January, I started to get to work and realized that my test lab was, at best, suboptimal. Many of the topics I write about can be tested and deployed on virtual machines, but I like to do filesystem books on real hardware or at least real disks. I have a host for that–it’s old, but who cares? Disks are disks, and this thing has eight SATA drives and a couple SATADOMs for the OS. Eight drives lets me test most common ZFS configurations. The host is large and noisy, but I have a basement and it has a BMC so I can kick it as needed. Creating a hard drive failure means two flights of stairs and opening a case, but I can live with that.

Mind you, I had stolen some of the hard drives for other purposes. More drives were needed. I descended into the Parts Closet. Well, I call it the Parts Closet. Other people call it a trash heap, or perhaps a Do-It-Yourself Toxic Gas Cloud Kit, Add Your Own Fire. Old computers, old printers, all precariously balanced. Laptops preinstalled with Windows XP with wobbly lids, cat5 wire crimping kits, pristine Unicomp Model M keyboards with button mice, Keyboardio Model 100s with Dvorak keycaps, a wall of small storage boxes with labels like SOEKRIS and PCCARD and SCSI TERMINATORS. The POWER OVER ETHERNET box sits right next to ETHERNET OVER POWER, which I do recommend as a convenient trick if the electrical system in your home doesn’t date from 1949 and wasn’t engineered by a PTSD-stricken pipefitter with delusions of grounding. (Fortunately cable TV is historical, so I can run Ethernet over the old coax someone paid big money to install.) Once I started digging for hard drives and discovered several expensive 250GB IDE disks, the necessity of a purge overcame my unwillingness to perform said purge.

Finding the cable crimpers reminded me that I needed to check some of the long-haul cabling in the house. The cable tester showed that I shouldn’t ask questions I don’t want answered.

Now let’s detour into backups.

I have a iX Systems miniXL running FreeNAS for local backups, and rely on Dropbox and Tarsnap for external backups. All the backups get tested monthly, mainly because I routinely screw up and must recover from backup. The miniXL also serves as my MP3 storage, because cleaning out the parts closet demands a soundtrack.

Naturally, I’m halfway through the ghastly purge when the music dies.

The miniXL’s boot SATADOM was no longer a boot device in the BIOS.

Fine. I’ve never worked with SATADOM hardware before, but how bad could it be? I ordered an inexpensive replacement.

The Supermicro power cable didn’t fit. Apparently that’s a well-known example of vendor lock-in, so I ordered a more expensive guaranteed compatible Supermicro SATADOM that was not at all compatible and immediately went back to the dealer. Fortunately, some ex-iX folks mentioned that the miniXL had space for an SSD. I had found a couple SSDs in the Parts Closet.

But then I realized that the miniXL has eight removable hard drive bays, is much quieter than my test system, and would easily fit under my standing desk (pic). Causing a hard drive failure with this host doesn’t require going to the basement and opening a case.

The critical service, music, is now being shared from my Mac desktop.

Backups? I have external USB cases for local hosts to back up to. I used the FreeNAS box because it was there. The miniXL is now running raw FreeBSD 15 and bhyve.

I now have a less unsuitable test environment and the toxic waste accident has been relocated from my home to the recycling center. Well, technically, I’ve converted one large toxic waste accident into two smaller accidents and added one of those accidents to a full scale disaster, but I’m not responsible for that disaster so I’m going to be a good citizen and ignore it.

In other news: last month I said I had completed fulfillment of the new Networking for System Administrators by packing and shipping a few hundred books. Uh… not so much. Yes, I finished packing the books. The US Postal Service hauled them off my porch. All good?

No.

More than one backer contacted me to say that their books were weirdly delayed. The USPS hauled my overseas books from Detroit to the big processing center Chicago, where most of them sat for a month. A handful ricocheted between Chicago and NYC for weeks. Several folks told me that this is unacceptable. I agree. I have no leverage nor any ability to fix this, however. My country is increasingly hostile to small business. I’m pretty sure that if I used USPS’ expensive two-day shipping, they would arrive speedily. I could use UPS or Fedex, except they’re expensive and might charge $50 to collect $3 in VAT depending on criteria so complicated as to be effectively unpredictable.

There’s also been other surprises. US Export Compliance returned one package because they require a full recipient name. A recipient like “A D Smith” is not acceptable; the shipping label must spell out Anonymous Doof. I’d expect the destination address to establish an internal protocol for demultiplexing initials, but apparently my government needs to know exactly who backs me. This has never been a problem before, but fine, rules change and there’s probably an announcement somewhere.

All I can think of to do is: warnings on my crowdfunding campaigns. Lots of warnings.

Much like I do when I warn you Patronizers that backing me is a terrible deal. January had no progress, but many tiny fixes. Yes, yes, that’s its own kind of progress but it doesn’t get words on the page. I do appreciate y’all. Thank you.

Posted on

“OpenZFS Mastery” device names options

The original FreeBSD Mastery: ZFS books recommended managing disks by labels based on serial number.

  pool: vm
 state: ONLINE
config:

	NAME                   STATE     READ WRITE CKSUM
	vm                     ONLINE       0     0     0
	  gpt/WD-WCC4N0JSJDKF  ONLINE       0     0     0
	  gpt/WD-WMC4N0M8NRXM  ONLINE       0     0     0

errors: No known data errors

I do this on hosts with multiple storage devices. It’s great for reality, with copy-and-paste terminals. It’s terrible for an educational book. The brain cannot absorb this easily. I see two ways around this. There’s the method used in the original books:

  pool: compost
 state: ONLINE
  scan: none requested
config:

NAME       STATE READ WRITE CKSUM
compost    ONLINE   0     0     0
gpt/zfs0   ONLINE   0     0     0
gpt/zfs1   ONLINE   0     0     0

Easy to understand. A terrible example. Readers of the first book did this, despite the copious warnings not to.

It was suggested that I could use truncated fake serial numbers from different manufacturers.

  pool: vm
 state: ONLINE
config:

	NAME             STATE     READ WRITE CKSUM
	vm               ONLINE       0     0     0
	  gpt/WD-WCC4N0  ONLINE       0     0     0
	  gpt/SEA-4N0M8  ONLINE       0     0     0
	  gpt/TOSH-9262  ONLINE       0     0     0
	  gpt/NCC-1701A  ONLINE       0     0     0

errors: No known data errors

This is obviously fake. It also obviously represents serial numbers.

So, the question for my nonfiction readers is: how does the latter example stick in your brain? Is it not only readable but absorbable?

Posted on

Paypal re-enabled on my store

Seems that during a round of troubleshooting the Tilted Windmill Press store, I temporarily disabled Paypal. Turning off features until you figure out what’s broken is standard troubleshooting.

Apparently I skipped the part where I turn features back on. Oops. Paypal is back. Sorry, folks.

Nobody complained, which makes me curious. Does anybody have reason to need Paypal rather than a credit card? I want to offer all reasonable payment options, but I don’t want to carry unnecessary stuff.

Posted on

December’s Dastardly Sausage

This post goes to Patronizers in December and becomes public in January. Not a Patronizer? You could be! $12 a year gets you my latest updates, occasional free tidbits, and the completely pointless MWL Footnote Fortune File, freshly updated for the new edition of Networking for System Administrators.

A month of paperwork here.

The N4SA2e Kickstarter is “fulfilled,” meaning “Lucas has done everything that he can do” and not “everyone has received their books.” The printer (Ingram) has acknowledged all the drop shipment orders, but they’re backed up for the solstice. I am told that Ingram is running extra shifts to catch up, but physical products take time no matter what you do. This is the second time a campaign went large, and I’ve reached a couple of conclusions.

I am the wrong person to be doing this work.

Chasing a handful of people for their phone number and shipping address? No big deal.

Chasing a few hundred people for same? Big deal.

Some folks handle that just fine, but my brain is wired in such a way that I find it painful. I could just say “eh, they gave me money but didn’t give me an address, not my problem,” but that way leads to unhappy supporters. I want folks coming back for the next book. The photo in this Bluesky post is my goal–folks coming back, book after book, and buying them directly from me. The only way that happens if I make it work transparently. Catching Covid halfway through this fulfillment didn’t help. I need support.

The good news is, my “contact all sponsors and get their correct current shipping address” script worked. I had one misaddressed package. Seems the sponsor runs their own mail server and hadn’t got my email. I can deliver messages to the Email Empire reliably, but one dude on his own? Not so much. Still, I’m calling it a success. That wasn’t so bad.

Dropships are simple, in theory. I prepare a spreadsheet with the hundreds of orders on it. Each spreadsheet has an ISBN, title, address, phone number, shipping method, and so on. I send the spreadsheet to Ingram. They acknowledge it, print the books, and ship. Not a huge job, but tedious and annoying.

I know many detail-oriented people. I could easily hire one for short-term spreadsheet wrangling.

The annoying thing would be training them. Training means explanations. Explanations are best served by documentation. I’ve put off documenting Tilted Windmill Press business processes, in part because the whole time I’m committing them to writing I would have to suppress my fully natural desire to shriek THIS BUSINESS IS RIDICULOUS and while that’s certainly true I’ll eventually run out of air and black out.

But needs must when the devil drives. Capitalism is a pretty senior devil.

The material changes slowly, but too quickly for a book. The sensible way to document my processes in a way accessible to external employees would be… ugh… I don’t want to say it… a (gag) wiki. (I guess I’m now looking for recommendations for simple wiki servers that run well on BSD?)

The logical next question, though? If I’m going to document my processes, and they’re going to be on a web site, should I make the documents public?

Businesswise, I am a unicorn. Very few people make a living writing. Of those, most write for an organization like a publisher or a business. I write books independently and fling them into the public, at scale. A handful of other folks manage it. Huge names? Yes, Brandon Sanderson’s last Kickstarter had 185,341 backers and grossed $41,754,153, so that dude has an entire staff complete with HR department and a full-time spreadsheet wrangler and a single manager to insulate him from all of that. The minuscule gang at my size have all built our own systems for dealing with a hostile industry. Dealing with the vagaries of IngramSpark dropship spreadsheet? There’s maybe a few dozen authors in the world that have to do that for themselves.

But when you first meet the system it feels overwhelming. The newly initiated would welcome documentation.

Ditto for folks who have never used USPS to mail a thousand books from their living room. How do you prepare that spreadsheet? How do you manage the packages? What’s a manifest? It’s a straightforward job, easy to outsource–once you provide instructions.

But if I make this public I would attract comments. “How do I sort columns in LibreOffice?” “Apple Music doesn’t let me export spreadsheets.” “No way a woke doofus like you could have that many readers.” And, of course, the all-purpose “You are wrong.” Yes, I can open each page with a disclaimer and remove all contact information, but people are weirdly persistent in finding a mailbox to complain at.

But when an Ingram spreadsheet first assaulted my eyeballs, I would have cherished an experienced person’s scribbled notes.

But, but, but. Lots of back sides, no front sides.

I’ll be setting up a wiki for internal use, but we’ll have to see if I make it public or not.

The real time and energy savings of hiring someone won’t hit until the second time I hire that same person to help ship books, because the first time I’ll spend more resources documenting and training than I would doing the work myself. Writing this out, I should perhaps hire someone before I have a large campaign. It’s probably better to train them on a Dear Abyss or a Laserblasted than on a viral tech book.

Anyway, what else is going on?

I’m in a new Storybundle that supports World Central Kitchen! That’s cool. My book, Beastly Virtues, will never be in stores. I created this collection just for this Storybundle. I have enough short stories that I can create themed collections on just about anything–well, okay, maybe not for “hope.” Or “joy,” sure, but almost anything! This bundle is all about Wee Beasties, and is a great deal. Digital Reader patronizers, you’ll get a copy of my book but you should definitely check out the bundle.

With N4SA2e out the door, I should have the decks clear to start really cranking on the new OpenZFS book. It’s open for sponsorships, by the way, so do tell your friends. I don’t know if I’ll do a challenge coin for this book, though. Business thrives on predictability, and I don’t know if coins will be available by the time I finish the book or what the tariffs on them will be. I budget about $7-$8 for a coin, which makes print sponsorships slightly less profitable than Kickstarter backers who buy the special edition without the coin. If that becomes $20 a coin, there won’t be a coin. If inflation keeps climbing, there won’t be a coin. I really, REALLY want to not raise the price of sponsorships. I last seriously considered a sponsorship price increase in 2022.

The real answer is that the value of the dollar will continue to degrade until I am forced to raise prices. Then it will degrade further. Because that’s what the dollar does.

N4SA2e was my most sponsored book however, though, and if I can continue to attract numbers of sponsors I can hold off that price increase.

Anyway: docs. N4SA2e. Wee Beasties. OpenZFS. I think that’s it?

Thank you for your support. My Patronizer income might not be huge like some folks, but it’s predictable reliable and steady and that makes a world of difference when it comes to keeping the lights on.