@fortified_banana@beehaw.org cover
@fortified_banana@beehaw.org avatar

fortified_banana

@fortified_banana@beehaw.org

This profile is from a federated server and may be incomplete. For a complete list of posts, browse on the original instance.

fortified_banana OP ,
@fortified_banana@beehaw.org avatar

Yeah, I've always found terms like "content" (and by extension "content creator") to be degrading and corporate-focused. It's weird to me that it's such a common way to refer to the work of artists and entertainers online. I don't do anything of the sort, but it's got to be rough being pushed so hard into chasing the algorithms to stay relevant.

I've yet to be disappointed in anything TWRP's put out.

fortified_banana ,
@fortified_banana@beehaw.org avatar

Looks like you're on Fedora Silverblue (or other Atomic version). This is happening because the system groups are in /usr/lib/group rather than /etc/group and this causes the issue you're seeing here. You can work around it by getting into a root shell with something like

sudo -i

and then getting the group added to /etc/group with

grep -E '^dialout' /usr/lib/group >> /etc/group

after that, you'll be able to add your user to the group with

usermod -aG dialout pipe

fortified_banana ,
@fortified_banana@beehaw.org avatar

/etc is writable, so no reboots are required. That said, /etc is treated in a special way and each deployment will have its own /etc, based on the previous one.

So if you make changes to /etc then revert to a previous deployment, your changes will be reverted as well. But if you make changes and upgrade (or do whatever to create a new deployment), your changes will bu preserved.

fortified_banana ,
@fortified_banana@beehaw.org avatar

No, it's a side effect of how everything's handled by rpm-ostree currently, and it's on the list of issues to be fixed.

See Here for more info

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • test
  • worldmews
  • mews
  • All magazines