nope, that would make the experience way worse with federation not working well with communities. like for example I've made a community over on lemmy.world and it has a couple of members and a few posts in it, but I can't see it from any other lemmy instances I've tried (unless it doesn't work if you're not logged in). you can kinda make kbin see it but to make posts appear you have to search for them and if you search for them before you search for the community, they appear in a random magazine and then when the magazine for that community is created the posts that were put in random stay there and never return... so yeah...
No, but I had no major problem gaming with an Nvidia card on Tumbleweed. Just followed the wiki guide and added it to the zypper repos and everything was fine.
I run everything in rootless containers using systemd service files generated with podman generate systemd.
Podman Compose is a “community effort”, and Red Hat seems to be less focused on its development (here is their post about it).
There are ways to get it working but I find it easier to go with podman containers and pods through systemd because the majority of documentation (both official and unofficial) leans in that direction.
I don’t know how much you already know, so here is just a summary of things that worked for me for anyone reading.
Podman uses the concept of “Pods” to link together associated containers and manage name spaces, networking, etc. The high level summary for running podman pods through systemd:
Create an empty pod podman pod create --name=<mypod>.
Start containers using podman run --pod=<mypod> … and reconfigure until containers are working within the same pod as desired.
Use podman generate systemd to create a set of systemd unit files. Be sure to read through the options in that man page. – this is more reliable than creating systemd unit files by hand because it creates unit files optimized for the podman workflow.
place the generated systemd unit files in the right place (user vs. system) and then it can be started, enabled, and disabled as with other systemd unit files.
Note: for standalone containers that are not linked or reliant on other containers, you can should skip creating the empty pod and can skip the –pod=<mypod> when starting containers. This should result in a single service file generated and that container will operate independently.
The Red Hat Enterprise Linux docs have a good amount of info, as well as their “sysadmin” series of posts.
Here are some harder to find things I’ve had to hunt down that might help with troubleshooting:
Important: be sure to enable loginctl enable-linger <username> or else rootless pods/containers will stop when you log out of that session.
If you want it to run a container or pod at system startup you will need to specify the right parameters in the [Install] section of the systemd file, see this doc page. Podman generate systemd should take care of this.
If you are using SELinux there is a package called container-selinux that has some useful booleans that can help with specific policies (container-use-devices is a good one if your container needs access to a GPU or similar). Link to repo
However, if you have one monster thread running, clicking on any notification will clear all of the notifications from that thread but not any others. So you do at least have a quick way to get rid of them and you won’t miss anything you care about.
The first alias actually gave me some ideas, thanks for that. But I don’t understand how is what you did is really different from alias ein=‘sudo emerge -av’. I think the only thing that is different is the way you do it ein abc def will be the same as ein abc, but why would you want this?
I did not play EA, and overall I am enjoying it. The issues I have are the random mechanics that are thrown in as one time things like chase scenes and a stealth sections. Those are plain not fun, and could have been something else entirely.
Potential spoilers for the main story ahead!
spoilerThe portrayal of the Sea People seems very Chinese caricature at a few points. Plus the quests they give are kind of not fun. I could do without them altogether honestly.
Why would an instance annex another instance? I can’t imagine the pain in trying to merge two databases like that, then handling the changing of the address.
If anything, I expect a single or a collection of larger instances could choose to defederate from the larger federation.
It is basically like when a person goes to a webpage. If anything, it is more likely that a group of smaller instances to take down a big instance hosting tons of communities.
kbin.life
Top