• Dark Arc@social.packetloss.gg
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        7 months ago

        Yeah this one is ridiculous. There are some systems that have bounced my password … literally the one stored in a password manager … and gaslite me that I “must have forgotten my password.”

  • drspod@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    If you want to add an existing user to an existing group, use:

    usermod -a -G <group> <user>

  • FizzyOrange@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    Even if “isn’t that bad” were true, it’s hardly a stunning endorsement. I wish Linux aimed higher than “not that bad”, but it always seems to hit “only some bits are broken”.

  • fortified_banana@beehaw.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    7 months ago

    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

    • frezik@midwest.social
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      7 months ago

      Why can’t we keep system config things in /etc? It’s a method that works in unsurprising ways.

    • jkrtn@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      7 months ago

      Is etc the mutable part? Would you have to do this again to add more users after a reboot?

      • fortified_banana@beehaw.org
        link
        fedilink
        English
        arrow-up
        0
        ·
        7 months ago

        /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.

    • Artyom@lemm.ee
      link
      fedilink
      arrow-up
      0
      ·
      7 months ago

      Is that considered a feature for some reason? That seems objectively terrible.

    • KindaABigDyl@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      7 months ago

      It’s like when I run into some issue with how I’ve set up my system in NixOS and have to explain to a non-Linux user that it isn’t Linux that’s the issue but how I’m using an especially weird Linux lol

  • marcos@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    I’ve had this one recently.

    It gives you an error message, but creates the group anyway.

    • haui@lemmy.giftedmc.com
      link
      fedilink
      arrow-up
      0
      ·
      7 months ago

      (some!) FOSS developers when you open an issue about it: works for me. Closed

      (Disclaimer: I know not all foss devs are like this. Especially kde devs are awesome.)