▲ 684 ▼ You can't cd or ls in a folder if you have no +x permissions on it. That is all. I wasted 3 hours of my life. (szmer.info) submitted 2 years ago by unsaid0415@szmer.info to c/linux@lemmy.ml 122 comments fedilink hide all child comments
[–] nixcamic@lemmy.world 2 points 2 years ago (2 children) I think it's systemd not the kernel. If only Linux had "repair permissions" like vintage MacOS. permalink fedilink source parent hideshow 4 child comments replies: [–] palordrolap@kbin.social 1 point 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] nixcamic@lemmy.world 1 point 2 years 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. permalink fedilink source parent [–] Synthead@lemmy.world 1 point 2 years 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. permalink fedilink source parent
[–] palordrolap@kbin.social 1 point 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] nixcamic@lemmy.world 1 point 2 years 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. permalink fedilink source parent
[–] nixcamic@lemmy.world 1 point 2 years 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. permalink fedilink source parent
[–] Synthead@lemmy.world 1 point 2 years 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. permalink fedilink source parent