I was going to buy the Lego Star Trek enterprise, but it was sold out before I got there. Oh well, they saved me from myself with artificial supply restrictions.

Instead, I didn’t buy anything.

I think this is the right answer.

If the drive isn’t ext4 formatted, steam os won’t automatically mount.

Here’s a tool that seems to be able to do it for any drive: https://github.com/scawp/Steam-Deck.Mount-External-Drive

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.

Pioneer Kuro or Panasonic Z series.

No other contenders that I can remember.

I still regret not getting a Z series. My S series from 2008 is still cooking (literally) the basement.

Layers, intentional or not.

Template:

Goddamn, I wonder how much this would explain about my grandpa. He was David but went by Steve. Named his first kid Steve too.

Seems like it would be easy to find one in Portland.

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?

It is. I got it working wirelessly once for shits and giggles using USB/IP.

Dug up the comment: https://lemmy.world/comment/3637478

Once podman is installed (iirc the network package is marked as a dependency for most package managers) and your user is configured (provide subuids/subguids), I really think podman is a simpler model. The containers you run are actually yours (not root’s) and you don’t need to be part of a privileged docker group to run them. Of course, you can run containers as root with podman too: just use sudo.

You’ll actually need to configure your user the same way for running docker in rootless mode, which should be the default.

Your dockerfile will work with podman. Your docker-compose file will too (via podman compose). You’ll have access to awesome new capabilities like pods, and defining your containers with kubernetes style yaml, and running your containers via systemd.

However, with rootless podman/docker, you should remove any/all of the USER silliness the rootful/default docker people do to protect themselves a bit from rogue processes effectively running as root and/or container escapes to root.

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

Yeah, it is pretty great!

I’m building software to bridge an in house legacy system and a CLI program. It has 1 partial restful API endpoint (no delete, no patch/put). But it does have 3 cyber security suites including one that wraps the runtime. It is not a public API.

I have 4 meetings a week.

Did I mention I work from home?

Going on 22 days waiting for a firewall rule change so I can pull containers from the enterprise GitHub enlistment.

I’ve had discussions with 4 different OUs. Not one of them has been able to tell me why the firewall is different for this VM. There is no way for me to see the state of each and compare.

I’ll probably come off as a crusader, but rootless Podman is a great way to accomplish this out of the box.

Podman maps your user ID to root in the container, but you don’t need root (or a rootful socket) to run the container.

Docker also has a rootless mode now, but I’ve found no reason to go back.

I have entire conversations and then 5-30min later realize I had a conversation and panic because I can’t remember anything about it except that words were exchanged.

Honestly, a real plumbing store.

Brands we considered/bought during our remodel that I can also remember:

• Brizo (Delta’s “luxury brand”)
• Artos
• California Faucets
• Hansgrohe

All of them are way, way nicer than the best thing you can find at a box store.

We spent a ridiculous amount on plumbing fixtures though (kitchen and 2 bathrooms), so be prepared for sticker shock. BIFL is the tune I kept whistling though.

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.

Looks like there probably isn’t much [toe] nail in that shot.