aberrate_junior_beatnik (he/him) @ aberrate_junior_beatnik @midwest.social

Posts

2

Comments

335

Joined

2 yr. ago

know their game is more expensive on switch than on pc, but it’s well within your budget and you want to give them extra coin

With the (probably doesn't need to be stated but here I go anyway) caveat: how much of that coin is going to the dev, and how much is going to Nintendo? The game might be cheaper on (for instance) Epic, but Epic takes a smaller cut.

Absolutely, I am a complete idiot. I pointed out to you that a simple & obvious search results in multiple definitions & examples of how meat is processed. I thought that would result in you understanding that meat is, in fact, processed. In hindsight, that was extremely stupid of me and I feel very dumb.

shaun did an excellent video on exactly this. TL;DW: stereotype threat & harassment.

You were responding to:

We also pay for their bailouts and subsidies. Piracy is ethical.

There was nothing in this statement to suggest the motive behind piracy had anything to do whether or not it is ethical. There was nothing in this statement to indicate that the author was engaging in piracy for purely altruistic reasons.

I don't see how the author was "making excuses to pretend [they] don't" "want free stuff." And I don't see how arguing that piracy is ethical is implicitly arguing that you only do it for altruistic reasons. I think bringing up the selfish motives behind piracy without prompting is an implicit admission that there is a connection between selfish motives and the ethics of piracy. And finally, I think parsimony is effective.

There is always unwillingness by piracy advocates to acknowledge that some people do it just because they want free shit.

Some people do it just because they want free shit. I don't care. It's still good.

Yes, but it's 70% off

https://is.gd/bVN2Op

Unfortunately, they do not care. They don't want people watching youtube, they want people watching ads.

I'm trying to find where you can support the authors of blocklists. So far I've only found Peter Lowe's Patreon.

[Edit: upon reflection, this post went too far. To any who saw it, I apologize.]

Wow it must be an extremely novel experience for an iOS programmer to have a company arbitrarily make decisions about what you can and cannot do on their platform

Yeah, unlike the totally non-disgusting way meat is processed

I don't disagree with you factually, but why bring this up? This is essentially the same as pointing out that women have it worse elsewhere in the world anytime we talk about patriarchy in the US.

Love too live in a society with a free press

I didn't come from reddit

I'm not going to

No I didn't

It's not hard

How does one do this? I can block users & communities, but not instances.

Ok, so I did some testing locally.

Assuming podman is running as user user, which has a primary group gid 1000, the default /etc/subgid will look like:

    
...
user:100000:65536
...

  

Running podman run --rm -it busybox cat /proc/self/gid_map with this /etc/subgid the output is going to look like:

    
0       1000          1
1     100000      65536 

  

Which means that if you bind mount a volume in and create a file with gid 0, it will have gid 1000 on the host. Subsequent gids will map to 100000,100001, etc. The group video, which should be gid 44, will map to 100043. So one option you have would be to add 100043 (or whatever gid 44 gets mapped to, if your /etc/subgid is different) to the acl of /dev/dri/cardX. Then if your plex user has group video in the container, you should be golden. No need to even have --group-add=keep-groups. Even the user running podman wouldn't need to be in group video on the host.

This is probably what you should do, because the following will change the behavior of every other container the user runs. But since I spent time hunting it down, I'm going to post the rest of this anyway:

As it stands, your container will only have access to the mapped gids above. If you want to get group 44 in your container to map to group 44 on the host, some trickery will be necessary. First, you will have to change /etc/subgid from the above to

    
...
user:44:1
user:100000:65535
...

  

Changing the count on the second line (65536->65535) isn't strictly necessary, but in my testing podman did not like having uneven numbers of gids and uids. Also, the order doesn't matter, you could switch the order of the lines, but podman is always going to interpret it in the order of the host gids. Finally, I had to reboot for the change here to register. There's probably a way to do it otherwise, but logging out & back in didn't do it, and neither did systemctl daemon-reload, so ¯(ツ)/¯

After this change, podman run --rm -it busybox cat /proc/self/gid_map will output something like:

    
0       1000          1
1         44          1
2     100000      65535

  

Ok, so now we have access to the host's group 44, but it's mapped to the container's group 1. That's not very useful, since gid 1 is traditionally the daemon group, which is used for other stuff. So here's where --gidmap enters the picture and it gets confusing. With rootless podman, --gidmap does not take the format {container-id}:{host-id}:{count}. It takes the format {final-id}:{initial-id}:{count}. So if we want to map to the host's id 44, we actually need to map to id 1, which then gets mapped to 44. So here's the command:

podman run --gidmap 0:0:1 --gidmap 44:1:1 --gidmap 1:2:43 --gidmap 45:45:65492 --rm -it busybox cat /proc/self/gid_map

Which then should output:

    
 0          0          1
44          1          1
 1          2         43
45         45      65492

  

Makes perfect sense, right? Well, it does make sense, but it's (at least to me) confusing. What podman does is create a second, nested user namespace, and uses that to make the map. So nested 0 maps to initial 0 which maps to host 1000. Nested 44 maps to initial 1 which maps to host 44. Nested 1 maps to initial 2 which maps to host 100000. Nested 45 maps to initial 45 which maps to host 100044. And so on. So now you should be able to do

    
rm -f fake-dri; touch fake-dri; chgrp video fake-dri; chmod 660 fake-dri
podman run --gidmap 0:0:1 --gidmap 44:1:1 --gidmap 1:2:43 --gidmap 45:45:65492 --mount type=bind,src=$(pwd)/fake-dri,dst=/dev/dri --rm -it busybox sh -c 'echo I can write to /dev/dri > /dev/dri'
cat fake-dri

  

And it should output I can write to /dev/dri. I didn't actually test it with plex, but if the issue really is permissions on /dev/dri/cardX, this should work.