For sure.

I am excited to see more arm-based Linux devices for consumers. And the Snapdragon-based VR is exciting on that front.

It definitely won’t change anything for tomorrow or next year, but it does make me hopeful that better support is in the relatively near future.

I run Bazzite and Garuda (with the cachyos kernel). Only the Garuda box is Nvidia and has been great since kde+Wayland+Nvidia stabilized a year or so ago.

I think any of them (including cachyos) is a good choice. Optimization is diminishing returns, so I’d be looking for a distro with the default settings and tools I like as a much higher priority.

For example, I like Garuda’s btrfs with automatic checkpoints on upgrade so I can just send a garuda update (which is pacman Syu with bells and whistles) and almost ignore the output even when I get lazy and don’t update for a month. Don’t take this as a recommendation to ignore updates on an arch-based distro. There will eventually be consequences.

With bazzite, updates really are in the same class because of the immutable base. But I’m also deep into containers and have no issue with the ergonomics of layering and management, which are improving, but definitely not very newbie friendly.

Anyway, give them test drives. You’d be surprised how much changing a package manager can impact your ability to do things for a while if you aren’t familiar.

I really wish the bot curated the feed a bit. The number of times I have clicked through to the comments only to find a flagged/removed post because I wanted to enjoy watching the fireworks…

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?

Allegedly:

Lol, a golang binary to reformat output and do a lookup against a hard-coded map of maximum supported speeds for only pixel phones.

1100 lines of vibe coded insanity.

https://github.com/kaushikgopal/dotfiles/blob/master/bin/usbi.go

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.

Oh no.

The direct cause of the errors seems to be that the package or one of its dependencies isn’t pulling other dependencies. That is, they’re making assumptions about the environment.

If a flatpak is available, try that first. If not, you’ll probably need to do some investigating to see what dependencies are needed.

Start at the top and search for the packages that address the errors. Try again after each install. It looks like qtwayland5 or qt6-wayland might be the first missing dependency.

Probably 5 because of the pyqt5 references in the error logs.

!anythingbutmetric@discuss.tchncs.de

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.

And everything old is new again.

Congratulations to any of today’s lucky 10k.

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.