

postmaster@domain
is always fun
postmaster@domain
is always fun
Das endet dann für alle beschissen, siehe Newag.
I think I remember some weird power bugs in the 2700x, though I never encountered them myself. The best thing I could find was this reddit thread https://www.reddit.com/r/Amd/comments/apw8im/ryzen_freezes_in_linux_even_if_linux_is_in_vm/
Do you still have the live iso you used to install arch? Does it work? Do other distros work (just the live systems are enough)?
Edit:
Some more things: Did you try disconnecting the pc from mains, pressing the power button (to discharge all capacitors) and reconnecting. Reseat the button cell for the bios?
There are good April’s fools jokes and there is this. Some things you just don’t joke about.
I’m still of the opinion, that your GUI sucks if it needs documentation.
Docker container can’t read a bind mount. Permission issue? No, it’s SELinux, again. And I didn’t even install it explicitly, it just got pulled in by another package.
And to be clear, the issue isn’t SELinux really, but unexpected non standard behaviour which I never asked for (never explicitly installed it).
It’s really only downloading the executable and java, starting it and opening the required port. See the official documentation for instructions.
If you want to get more involved there are some convenient docker containers which automate some stuff:
Ah got it, yes, that would be insanely useful.
You are talking about funkwhale. I never tried it, so I can’t speak to the part about integrating it with different clients, but that surely is possible, if it doesn’t already work.
Also, one big problem with this is copyright (however you might feel about it).
Edit:
Just don’t bring any device to a protest if you consider bringing a burner device.
Well, I was hoping they would take care of that themselves
Looks good, I use a lot of the stuff you plan to host.
Don’t forget about enabling infrastructure. Nearly everything needs a database, so get that figured out early on. An LDAP server is also helpful, even though you can just use the file backend of Authelia. Decide if you want to enable access from outside and choose a suitable reverse proxy with a solution for certificates, if you did not already do that.
Hosting Grafana on the same host as all other services will give you no benefit if the host goes offline. If you plan to monitor that too.
I’d get the LDAP server, the database and the reverse proxy running first. Afterwards configure Authelia and and try to implement authentication for the first project. Gitea/Forgejo is a good first one, you can setup OIDC or Remote-User authentication with it. If you’ve got this down, the other projects are a breeze to set up.
Best of luck with your migration.
I already did that. It doesn’t change the fact, that a normal user will not do that and google will just not tell you straight up.
I have used the page linked to in the comments. But that just said that they received my request - no indication if I had an affected device or not. Also for my jurisdiction I cannot get the free battery replacement, just the money or store credit.
I still have to hear back from them.
Seems like I have an affected device. No thanks to google for helping me figure that out. Their useless page shows no information regarding that. Had to look at the serial number of the battery: sudo cat /sys/class/power_supply/battery/serial_number
. Which contains the string from the mastodon post.
Now, I have a custom ROM, so that means I won’t suffer degraded battery capacity, it just might be dangerous to continue to use my phone.
efibootmgr
is your friend. Boot into linux and use it to set the boot records as you want, in the order that you want them.
Also, I have heard from a bunch of people, that this can be mitigated by having separate EFI partitions for Linux and Windows. That means one EFI partition per physical drive. You can go as far as having the EFI partition on different media than the Linux install.
I just keep my history file around and have set it up to never truncate. Then grep
or ^R
.
The whole deployment is done via ansible, so the ansible source is my documentation.