I recently did so, on my PC and my dad’s.
The instructions are here: https://en.opensuse.org/openSUSE:Slowroll
Someone recently updated that page and it’s a bit confusing now. I’m guessing, in the “Use” section, it’s missing a blurb that for side-grading you should then do the steps with the root session and so forth.
These are the instructions that I followed: https://en.opensuse.org/index.php?title=openSUSE:Slowroll&oldid=186653
I’m not using Ansible myself, but I do use kreadconfig and kwriteconfig, and well, it does just have 4 parameters to identify a setting and its value, so that Ansible module does look like it’s sufficient for that.
One tip I have, is that you can figure out which GUI setting corresponds to which config file change, by setting up a Git repo in ~/.config and looking at the diff. So, basically:
cd ~/.config
git init
git add .
git commit -m "original config"
# now change setting in UI
git diff
When you’re done transferring that into Ansible, you can commit or stage the changes and tweak another UI setting, or if you’re completely done, then just rm ~/.config/.git/.
I guess, you could also use this Git repo to roll back all the settings and see if your Ansible automation works as expected.
As a German, well, I don’t understand enough about the US side of things to answer to this, but I do always get spooked when I see nations pulling shit like that.
And, by the way, I do hope the USA finally get 9/11 under wraps this year: https://www.whitehouse.gov/briefing-room/presidential-actions/2023/09/07/notice-on-the-continuation-of-the-national-emergency-with-respect-to-certain-terrorist-attacks-3/
I mean, these communities do get created when someone feels like there’s a reason to. There’s just no council or whatever regulating when and where a community gets to be created, so any user on any instance can decide to open up and promote their community.
And frankly, I have no idea what the precise effects are. When you subscribe to all of these, it won’t really be much different from just one big community in that sense. It may mean, though, that someone new accidentally joining only one of the communities will not be presented all the content they want, yeah.
On the flip side, having it split is kind of cool, because you can decide to only subscribe to 2 out of 4 communities, if you only want half as much of this content in your feed. Or you can decide to subscribe to all of these, but not to the one on angry-instance.net, because you don’t like the tone of the discussions in that one.
Yeah, it’s federated, meaning you can subscribe to each of them and post to whichever one you fancy. If you want to post to multiple, it’s a good idea to use the cross-post feature.
Having only one singular official community would be rather bad, as then the respective server owners and moderators would have central control like on Reddit.
Hmm, yeah, it is a bit surprising to me, too, especially for an audio issue, but it’s always possible that you had some weird configuration values in about:config for historic reasons and now some new code, that came in with a Firefox update, isn’t working with that configuration.
Either way, it happens often enough that Mozilla has a troubleshooting routine for it, too, namely refreshing your profile.
If I remember correctly, it places your old profile data into a folder in your Desktop folder. But you can also separately backup your profile by closing Firefox and then copying ~/.mozilla/firefox/ onto an external hard drive or such.
Does it also still happen in fresh profile? It will be like a factory-reset Firefox (except that you can go back to your current profile), so then it definitely wouldn’t have anything to do with your Firefox configuration.
Does the problem still happen in Troubleshoot Mode?
Well, if you’re self-hosting GitLab, there might not be much of a difference. Codeberg is hosted by a non-profit organization, so you don’t have to self-host it.
The open-source software that it uses, Forgejo, is also more so developed by the community, rather than just one corporation, who could change the license for future updates at any point.
Huh, so Tony Hoare invented null and then Graydon Hoare invented Rust, immediately terminating the existence of which does not have a traditional nullnull value.
Yeah, that is my understanding, too. Otherwise you’d only want to generate them on the database host, as even with NTP there will be small differences. This would kind of defeat the purpose of UUIDs.
If you’re saying that even without NTP, just by manually setting the time, things will be fine. I mean, maybe. But I’ve seen it far too many times already that some host shows up with 1970-01-01…
For others wondering what’s wrong with UUIDv4:
UUID versions that are not time ordered, such as UUIDv4, have poor database-index locality. This means that new values created in succession are not close to each other in the index; thus, they require inserts to be performed at random locations. The resulting negative performance effects on the common structures used for this (B-tree and its variants) can be dramatic.
I guess, this means with these new UUIDs, ideally you only create UUIDs on systems that are hooked up to NTP, though I guess, it won’t really be worse than UUIDv4 either way.
We’ve been using Leptos at work, which is a similar framework (and probably shares half the stack with Dioxus).
And yeah, it’s really good. My favorite thing about using Rust for the UI is algebraic data types.
So, in Rust when you call a function which can fail, there isn’t an exception being thrown, but rather you get a Result-type as return value.
This Result can either contain an Ok with the actual return value inside. Or it can contain an Err with an error message inside.
So, in your UI code, you just hand this Result all the way to your display code and there you either display the value or you display the error.
No more uninitialized variables, no more separate booleans to indicate that the variable is uninitialized, no more unreadable multi-line ternaries.
It just becomes so much simpler to load something from the backend and display it, which is kind of important in frontend code.
It’s not a dual-language platform, though. You write the backend and the frontend in Rust. The frontend code is compiled to WASM to serve it to the browser.
Excuse me, Windows is the cheap copy of KDE.
This looks like one of the color blindness filters got activated. Here on Plasma 6, it’s a Desktop Effect in the System Settings. Not quite sure, if that was also already the case in Plasma 5, but if you just type “blind” into the search bar of the System Settings, then it should show up and you can disable it.
But that is what I mean with it needing an extension of the language.
So, I’m not saying you could just build a library that calls existing PHP functions to make it all work. Rather I’m saying there’s certain machine code instructions, which just cannot be expressed in PHP. And we need those machine code instructions for actually managing memory. So, I am talking about reading/writing to memory not being possible, unless we resort to horrible hacks.
Since we are building our own compiler anyways, we could add our own function-stubs and tell our compiler to translate them to those missing machine code instructions. But then that is a superset of PHP. It wouldn’t be possible in PHP itself.
Again, I’m not entirely sure about the above, but my web search skills couldn’t uncover any way to actually just read from a memory address in PHP.
I mean, I’m a bit out of my water there, both in terms of the featureset of PHP and what’s actually needed for a kernel, but I’m still gonna go with no.
For one, PHP uses reference counting + garbage collection for memory management. That’s normally done by the language runtime, which you won’t have when running baremetal.
Maybe you could implement a kernel, which does as few allocations as possible (generally a good idea for a kernel, but no idea, if it’s possible with PHP), and then basically just let it memory leak until everything crashes.
Then again, the kernel is responsible for making processes crash when they have a memory leak. Presumably, our PHP kernel would just start overwriting data from running processes and eventually overwrite itself in memory(?). Either way, it would be horrendous.
Maybe you could also try to implement some basic reference counting into your own PHP code, so that your own code keeps track of how often you’ve used an object in your own code. Certainly doesn’t sound like fun, though.
Well, and secondly, I imagine, you’d also still need an extension of the language, to be able to address actual memory locations and do various operations with them.
I know from Rust, that they’ve got specific functions in the stdlib for that, see for example: https://doc.rust-lang.org/stable/std/ptr/index.html#functions
Presumably, PHP does not have such functions, because its users aren’t normally concerned with that.
How? You’d need to compile it down to machine code somehow, for the processor to have any clue how to run it. And you’d need some custom library with custom compile instructions, to be able to control memory allocations, memory addresses etc…
I did a quick search and found two operating systems written in JS, both of which cop out when it comes to the kernel. Did you maybe mix it up with those?
Recently switched from Tumbleweed. Giving up on Plasma 6.1 was a bit of a bummer, although presumably that should arrive in 5 days.
But yeah, I’m currently not really using my personal laptop except on the weekend, so not having a big update waiting every weekend is going to be nice.