They mentioned it at the bottom of the blog: works ok Linux and macos. And they want you to enable it because there a bug they’re trying to reproduce.

TRS-80 then IBM PCjr here. Both hand-me-downs though.

Mom wouldn’t let me on the 386 until I could touch-type and write a program in BASIC. She was a Cobol and IBM RPG programmer.

“Vexillophile” is a word you probably won’t ever need again.

Omg thank you for the money!

It will depend on where you live.

Many US states have laws that carve out exceptions for work done on your own time and equipment. If the contact doesn’t call these out as exceptions somewhere, it’s a lazy contact.

I see. Yeah, that compose file is gross unless you’re running this on a dedicated vps, and even then…

I haven’t run snikket before, but it looks straightforward to me. Maybe the documentation has improved?

Tiling WM and Gruvbox. Doesn’t get any better!

It seems like the only time I encounter this oddness is when some upstream docker image maintainer has done a weird with users (I once went 3 image levels up to figure out what happened).

Or if I borrow a dockerfile and don’t strip out the “nonroot” user hacks that got popularized years ago.

Next, he’ll be going around trying to get kicked out:

“Bun cha fools around here, I dare you to banh mi”.

99 Honda Odyssey: Walmart Wasteland edition.

You can search the package database to determine which package(s) provide a file with dpkg --search $file

I might recommend starting with a project.

Something like getting pi-hole running. This would help you learn some of the networking basics. But I’d recommend reading at least enough to have a conceptual foundation about the things you don’t understand along the way (DNS, DHCP, etc).

You’ll want one of their supported OS choices to keep things simple. That means one of: fedora, debian, ubuntu, or centos. I might steer you away from centos just because its user base is a bit more linux-pro so finding specific help might be more daunting, but I don’t have much experience with it either. Maybe use a “server” variant to keep your system demand to a minimum (boot to terminal only).

The framework 13 definitely has a fingerprint reader. Top right corner power button, just like a Mac.

https://frame.work/products/fingerprint-reader-kit?v=FRANFF0001

Just as usable as the one on my old M2 Pro work laptop too.

Fwiw, I did the DIY and brought my own 32gb of ram and 2TB nvme to keep the costs down a bit.

You might want to check out distrobox. Nice way to access apps for other distros or package managers like they’re native.

I’m also on Garuda for my main box (Bazzite on the framework 13), and I have an Ubuntu distrobox for dev work with one dev project, another for general tools that are only released as .debs, one running fedora for things that “only support RHEL”, etc.

Windows was just the boat you already knew.

Now you have a new (more adaptable) one and don’t know all it’s squeaks and rattles. You’re neither dumb nor is something wrong. You just aren’t familiar with what it needs from you.

Give it some time (a week compared to how long in windows?) and attention and soon you’ll wonder why you ever second guessed it.

Totally.

Port knocking is one of those “of course someone did that” things to me too. A replay attack is enough to make it security theater.

An IP allowlist is a more useful addon.

We can go harder: port knock to open the port to a cert-only VPN (on top of all that)

https://wiki.archlinux.org/title/Port_knocking

I would ask for a healthy margin above 100%, especially if you’re bringing an older PSU. There are a ton of variables for determining what is needed, but if your TDP on those 2 items is pushing 400W, we should be aiming for 500+ with an 80 Plus certification.

This definitely plays like a failing PSU to me as I experienced similar issues when mine started dropping on one of the 12V rails with similar hardware (fx8350, r9 290) several years ago.