β² 60 βΌ Inspired by recent events (imgflip.com) submitted 1 year ago by amorpheus@lemmy.world to c/linuxmemes@lemmy.world 10 comments fedilink hide all child comments
[β] RustyNova@lemmy.world 8 points 1 year ago (3 children) I don't get it permalink fedilink source hideshow 6 child comments replies: [β] tiramichu@lemm.ee 33 points 1 year ago* (last edited 1 year ago) Read/write/execute file permissions. Having them set incorrectly can cause problems, such as creating a file as root then leaving you unable to modify it as user, being unable to execute a script because execute is not set, or being unable to use your SSH keyfile because you left the permissions too open. It's more actually like "Why is it, when something doesn't happen, is it always you three" permalink fedilink source parent [β] tofu@lemmy.nocturnal.garden 8 points 1 year ago It's the Linux file permissions. If something doesn't work properly, it's often due to wrong permissions because the app can't save/read it's stuff permalink fedilink source parent [β] nerdovic@discuss.tchncs.de 6 points 1 year ago (1 child) Maybe the recent events had something to do with ye good olde chmod 777 permalink fedilink source parent hideshow 2 child comments replies: [β] amorpheus@lemmy.world [S] 3 points 1 year ago (1 child) Was 700, should have been 755... 777 is more like the "just put sudo in front of the command" nuclear option. permalink fedilink source parent hideshow 2 child comments replies: [β] nerdovic@discuss.tchncs.de 2 points 1 year ago I had a fuckup by qualys recently that basically did what you described on many of our RHEL machines, broke a few things. permalink fedilink source parent
[β] tiramichu@lemm.ee 33 points 1 year ago* (last edited 1 year ago) Read/write/execute file permissions. Having them set incorrectly can cause problems, such as creating a file as root then leaving you unable to modify it as user, being unable to execute a script because execute is not set, or being unable to use your SSH keyfile because you left the permissions too open. It's more actually like "Why is it, when something doesn't happen, is it always you three" permalink fedilink source parent
[β] tofu@lemmy.nocturnal.garden 8 points 1 year ago It's the Linux file permissions. If something doesn't work properly, it's often due to wrong permissions because the app can't save/read it's stuff permalink fedilink source parent
[β] nerdovic@discuss.tchncs.de 6 points 1 year ago (1 child) Maybe the recent events had something to do with ye good olde chmod 777 permalink fedilink source parent hideshow 2 child comments replies: [β] amorpheus@lemmy.world [S] 3 points 1 year ago (1 child) Was 700, should have been 755... 777 is more like the "just put sudo in front of the command" nuclear option. permalink fedilink source parent hideshow 2 child comments replies: [β] nerdovic@discuss.tchncs.de 2 points 1 year ago I had a fuckup by qualys recently that basically did what you described on many of our RHEL machines, broke a few things. permalink fedilink source parent
[β] amorpheus@lemmy.world [S] 3 points 1 year ago (1 child) Was 700, should have been 755... 777 is more like the "just put sudo in front of the command" nuclear option. permalink fedilink source parent hideshow 2 child comments replies: [β] nerdovic@discuss.tchncs.de 2 points 1 year ago I had a fuckup by qualys recently that basically did what you described on many of our RHEL machines, broke a few things. permalink fedilink source parent
[β] nerdovic@discuss.tchncs.de 2 points 1 year ago I had a fuckup by qualys recently that basically did what you described on many of our RHEL machines, broke a few things. permalink fedilink source parent