A lot of times you will see the format string for the fedora version in the .repo file. This means its probably looking for f41. Since fedora updates fast, third party repos are usually slow to move to the next version and this repo probably doesnt exist causing dnf to fail. You can try and change the format string to the last available version. It usually works without issue, and updates aren’t disabled as long as the vendor updates that version

Start with 10 and subtract 2 for every step

Companies have until January 1, 2026, to create memory safety roadmaps.

Not really the same as dropping entirely

So this isn’t really an answer on how to migrate but this solution has worked well for me.

I define the toolboxes config with it, and if it gets destroyed, recreating it is as simple as creating a new one with the same name. You could upgrade or downgrade by just creating a new toolbox with the version you want.

I was going to say this too, but I’ve never cross compiled a cmake project so I wasn’t sure how much overhead there would be

You can compile on a big pi and copy the binary to your zeros. No need to compile on a zero lol

For me, setting up colored man pages is essential. I was hoping to see that in this article, because my methods aren’t ideal.

I’m either holding most back a couple versions, using a personal version of gentoos man pager that relies on texinfo and breaks on fedora, or using vim which is not my favorite.

I found this. I didn’t look at the code at all but the Readme mentions another project that might help.

https://github.com/ipatix/libvirt-usb-hotplug

I just did the same thing with llama and got the same thing

it still mounts and at first glance seems to be working

What makes you say that?

Show us the output of things like lsblk, mount and cat /etc/fstab to give us a fuller picture

I use privatebin. Has some good features but I dont think it has login

I like to put mine in /var/local/movies etc. to keep the root standard and uncluttered.

Of course it’s just personal preference

Where’s the source code? Seriously, the only thing I can find for drive & calander are repos that were archived in 2021

I think that it’s definitely a good case for overlaying with install. They say to use it sparingly because it increases the chances of something breaking, but that doesn’t mean it will. Something like a VPN usually needs liw level access that container isolation makes difficult.

I’ve only had 1 issue on silverblue years ago where I couldn’t update because I had vim overlayed and they fixed it within a day or two.

So it’s windows emulating linux emulating android emulating linux?

I’m interested to hear how that works out for you

You can set up multiple remotes for a repo and push to a local git server and github at the same time

Try running docker logs for the tailscale container to see if it gives any more info

Bash is my login shell, but I have fish set as the default shell for alacritty

If you’re making backups of things you care about and not running sudo rm -rf the command isn’t really dangerous.

But +1 for having it in /tmp I have a bash function I call tempd that is basically cd $(mktemp -d) I use it so much for stuff I dont really care to keep.

Tailscale keeps the private keys locally, . It just facillitates setting up wireguard. They could steal your private keys, as could any program you install with root access. But it would comepletely destroy their business, and it’s open source. I really dont think they have anything to gain by tricking everyone