I suppose I could have phrased that better. The registers themselves correspond to particular applications/stages, but the values store in those registers should change based on how the application/stage was loaded. Switch the order or inject a new binary and the hash from that stage on should change.

Any changes in the boot process should change various PCR registers. https://wiki.archlinux.org/title/Trusted_Platform_Module#Accessing_PCR_registers

And what do you think that polling rate was to fill up a 512 GB SD card? It’s all speculation but this isn’t a super collider, we shouldn’t need sub second polling of a vehicle that can only move 5.6 km/h.

This is so dumb, how could anyone at the FCC even humor such a request?

“Please help us, we overcomplicated billing and don’t want to explain it to anyone”

Honestly surprised nobody has tried to sell some bolt on diffusing/screen mask for this reason

I’m pretty sure the mirror was setup before that was an option. No reason to turn it off now that it’s a source of entertainment.

https://wiki.archlinux.org/title/Wayland#Automation

Honestly, I was running into the limits of stow. Want to unstow some configs on a bare machine? I hope you wanted that entire directory to be a symlink. Then I saw that someone had actually fixed that many years ago but the maintainer at the time was caught up in some personal crypto related projects and did not appear to be looking at the mailing list.

Chezmoi fixed that, applied a templating engine and added a data mechanism. In moving my stow configs I realized that application specific config file deployments are nice but shouldn’t be necessary. Templates fill that gap, and meshing them with scripts allows you to do some cool things only when variables change.

Plus I was beginning to play around with go at the time, so it just seemed like a good idea to use something I could contribute to if I needed.

I still don’t think I’m using chezmoi to it’s full potential, but I am fairly proud of the script I use to determine data sources for my waybar config on all of my machines.

All public and I regularly link people to my bash functions. Started with git bare repos, moved to stow, now on chezmoi. If I need anything more complex than chezmoi for these I’ll probably give up syncing them altogether.

https://github.com/StaticRocket/dotfiles

The problem here being these payment processors are global and none of this is illegal in the jurisdictions affected. This regional blocking, while nice, shouldn’t even need to be a “solution” to this. It’s a sledgehammer “solution” to something that was never enough of an issue for actual legislation.

Edit: clarify point

Well, to be fair the 10 series was actually an impressive improvement to what was available. Since then I switched to AMD for better SW support. I know since then the improvements have dwindled.

Those have all been replaced with em dashes (—)

Why? They are just bringing to light the tools already being used by corps behind closed doors.

Edit: Seems the author wants to paint a different picture. Either extreme CYA or you were correct.

Nah man, waterfall technique applies to everything.

I could never write essays by hand. Too often I would write out a paragraph just to read it, break it up, and subsequently rewrite both parts.

Pinchflat is one of the good containers that doesn’t try to play with ID remapping or anything. You just need a container quadlet like the following:

[Install]
WantedBy=default.target

[Container]
Image=ghcr.io/kieraneglin/pinchflat:latest

Environment=TZ=CHANGEME

Volume=CHANGEME/config:/config
Volume=CHANGEME/downloads:/downloads

PublishPort=127.0.0.1:8945:8945

It’ll run as the quadlet user id by default.

I haven’t heard anyone talk about puppy Linux in a bit. That used to be the go to for ultra lightweight setups.

“I want to know why this is broken. How to fix it can come later.”

Or override the TERM variable in your ssh config. Setting it to an xterm value has been supported by any niche term I’ve used over the years without sacrificing any of the usual functions.

Arch. Started using it in high school. Never had a reason to switch. Now I’m just regularly frustrated by other distros trying to make things easier by abstracting simple configurations behind layers of custom scripts.