No, sadly not. Maybe it’s implemented in Fish?

That was what I was expecting, without trying.

Maybe it’s just the right Decky add-on away? I have used add-ons for enabling VPNs so this should be possible, if not done already.

1. Can you connect to the same WiFi? If not, it’s gonna be impractical to connect without a cable. The Steam Deck has pretty fast WiFi, so if it lags i would bet your router is the bottleneck.
2. Civilization is mostly strategy, it’s turn based so there’s plenty of time to talk strategy, it takes some time to get a hang of the game but the beginning isn’t too rough.

And I appreciate you saying that

Funny how Microsoft registered the domain on PorkBun, and chose not to publish the ownership information. And yet you know the real owner.

That, or you’re just lying IDK…

Only so I don’t have to turn down the volume, and turn it back up when the episode starts.

It uses the Xen hypervisor, not qemu/KVM. Technically it is a Xen kernel virtualizing Linux since it is a type 1 hypervisor.

TBH i used to alt-tab away from what ever non-work-related thing i was doing, to a terminal emulator when ever my boss walked in.

It was usually showing my latest package upgrade.

I think you mean Cole’s Law

Lots of people have already mentioned Ventoy.

MediCat is Ventoy with a ton of images and a config file. It seems great, although I chose to roll my own as MediCat had a lot of Windows-centric images i have no need for.

No Children - The Mountain Goats

But not in a “fuck you world, I’ll do what I want” kinda way. More of a “I wanna watch it burn” kinda way.

1. Fedora has a major update every 6 months, and every version is supported for 2 releases + 1 week (= ~1 year).
   Updates have always been pretty painless for me. Most of my problems during updates have come from NVidia drivers (on a laptop), but a fix has always been available from the community.
2. Fedora has auto-update systemd services for both DNF and RPM-OSTree (more on this later). IIRC it’s just enabling a service and maybe editing a config file, but this is easy to search for, so I won’t tell you stuff I might not remember.
3. SELinux mostly just works, and if it doesn’t it’s probably a bug (if something is a package for Fedora, SELinux should work OOTB. Browse Fedora Magazine for the quirks you need to know how to handle.
4. I have no experience with ARC GPUs but Fedora might have better support as it tracks the latest kernel release = latest driver (depends on what was actually the issue, of course)

Concerning you RAID, just make sure the installer doesn’t touch it and mount it afterwards. You might have to do some kind of “restore” to give the files the needed SELinux metadata. The Discourse forum would probably be a good place to ask.

Now, a bit about DNF vs RPM-OSTree. Fedora with DNF is the standard distro much like most other distros. Use this if the next part doesn’t sound useful to you.

RPM-OSTree is used in a new family of distro that work a bit like git for your OS.
Your system runs off an “atomic” image. Atomic means unsplittable in Greek. Everything you change on your system is applied to your atomic image, like a file is added or removed from a git repo.
This is nice because upgrading to the next major version becomes a simple matter of rebasing you changes on top of the new version, and likewise, rolling back (in case of issues) becomes a single command and a reboot.

Fedora IoT is the “Server” edition of the Atomic desktops. Fedora CoreOS is a more “immutable” approach.

Feel free to ask more questions if something doesn’t make sense.

No problem!

I hacked this together instead of going to sleep, so it might make your deck explode, but maybe it’s a starting point for you or someone else:

# home-deck-mounts.mount
#
# Mount units must be named after the destination path, this / replaced by -, like above
#
# This is a template unit.
# That's explained here: https://fedoramagazine.org/systemd-template-unit-files/
# TL;DR: run it like this `netmount@linuxisos.mount` if you want to mount the subdirectory "linuxisos" from SHARE_PATH
[Unit]
Description=NetMount %I
After=graphical.target
# This is commented out, because it is implicit for network mounts https://www.freedesktop.org/software/systemd/man/latest/systemd.mount.html#Default%20Dependencies
# I keep it here as an example
#After=network-online.target
#Requires=network-online.target

[Mount]
# %i expands to what ever you put after the @ when starting/activating the service
What=10.10.10.99:/mnt/user/%i
Where=/home/deck/mounts/%i
Type=nfs
Options=exec

[Install]
WantedBy=default.target

I couldn’t confirm if mount units are allowed to be template units, but if not, just duplicate the service for each path and replace %i.

Say the word if you run into issues!

Don’t put yourself down! Using systemd wouldn’t make it work “better”, it’s just more “proper” (and a great tool to know in general!)

Great job and keep going!

This is really cool!

Where did you put the service file?

I don’t mean this as critique, but as possible next project, since your solution works perfectly fine. Systemd has some cool features that could make this project have a bit fewer moving parts:

• a .mount file could replace the mount and unmount script, and handle logging too! (I am pretty sure you would need separate files per mount, though, so “fewer moving parts” might be a bit of a lie, depending on your interpretation)
• that “After=” setting you used, can also be used to check for network connectivity. IIRC it’s “networking.target” on Fedora, at least. You might want to double check the systemd docs if After is the right one for this, as I have a hard remembering the systemd dependency intricacies.

That way you would end up with a .mount file per mounted directory, with logging using journald, and no external scripts.

I really like systemd as it can be a great tool, when you start to break down the complexity of it.

I hope you get well soon and get the best you can from this time.

Grounded danish plugs don’t fit Schuko sockets, but Schuko plugs fit danish sockets (but aren’t grounded).

This leads to a staggering amount of ungrounded devices in Denmark, as most are imported and making a variant for such a tiny country isn’t profitable.

Fun fact: the danish power plug was created by Lauritz Knudsen, a Danish company who had a monopoly. They are the reason Denmark uses this plug as the only country in the world, and Schuko only became legal to install in houses quite recently, so 99% of houses still use their standard.

LK has since been bought out by Schneider Electric but we are still stuck with our special plug and most imported devices are still ungrounded.

Thanks for listening to my Ted Talk.

I run the built-in automatic rpm-ostree upgrade service every 6 hours.

If you think that’s too inefficient, maybe read the docs for shutdown.target and see if you can use that to run an upgrade service before shutdown?

I’m not too experienced with that part of systemd but it seems like it could be a “proper” way to run things on shutdown?

Use a passphrase (not a password) and a physical security key, like a yubikey. It also supports TOTP or whatever 2fa Proton uses, you just connect it with a laptop or phone and it gives you a key.

A physical key is much more secure than 2fa from a password manager (although both are probably fine)

No problem! I’m glad you got it working!

I would just pull the first filament away from the bed and the rest usually follows along and you get a little birds nest.

I barely use a calculator, but you could try SageMath if you like the thought of writing you math in Python.