• nixcamic@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    I think it’s systemd not the kernel. If only Linux had “repair permissions” like vintage MacOS.

    • palordrolap@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Recursive chmod (or chown) has been breaking things since before systemd was a thing, so even if systemd is now responsible for stopping things from working, it can’t have been that previously, especially at the time I might have done something silly.

      As for repairing permissions only, I suppose it would be possible, assuming the system still works (or can somehow be encouraged to do so) to copy only the permissions (or at least infer them) from a backup or something rather than the whole files.

      • nixcamic@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Probably init before that then. I don’t think the kernel cares unless explicitly told to care, I’ve seen some embedded Linux with interesting permissions.

    • Synthead@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      You don’t typically have permissions “become defective” or need them to be “repaired” in a Linux system. Nearly all system files, with their permissions, are included in packages. Everything else should be considered user data.

      If you logged in as root and did something dumb, you could attempt to fix the permissions by reinstating packages.