After multiple attempts, finally made my own stable image of Bookworm 12.4 for BeaglePlay. With xfce desktop even.

For now, I'm saving every build log, pass or fail, mostly on the sheer wtf of some of the failures.

Little known fact: my learning curve thrives on finding all the ways I can make something fail. That's basically the fastest and easiest way for me to learn something; break it. This is fun for me, so fuck yes those logs are amazing.

Even if I didn't cause it.

In logs for part one of initial build using image-creator, errors that I did not cause and vanished on their own:

1.) Pauses because the password of the default user of that build had expired. The build had not yet even gotten past the first script; there was no rootfs yet.

I still have no idea wtf happened there and it happened twice right after the user creation function.

2.) resolv.conf vanished right before the final package installation. No reason. No idea what was up with that.

3.) It didn't like the test function I added the first time. Second time it did. Just--what?

No problems after this, until we get to writing it to an sd card with baletcha and/or Raspberry Pi Imager. All bets were off.

Using the same final image:

Baletcha: I went through thirteen perfectly good cards; it failed every time at the end of validation at 98%. I do not know how many times I re-imaged each of those cards but it was a lot.

Raspberry Pi imager with the custom image option: failed all but the last time. Fine, whatever.

It worked perfectly when I booted it with #BeaglePlay

@seperis flashing images with dd:
@tekeous ...why can't I stop watching this?