Timeline for Why is execute permission denied for bin file I created?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 25, 2020 at 12:42 | comment | added | Paul_Pedant | Typically, the project (editable) version of the script would have an extension like .bash or .sh. Your make install for echo-title would copy it into some bin directory, rename it without the extension, and chmod +x it. You can create a make rule to do those things for all your scripts, as part of an install or release target.. | |
| Dec 20, 2019 at 17:54 | history | edited | jesse_b | CC BY-SA 4.0 | added 78 characters in body |
| Dec 20, 2019 at 17:50 | comment | added | JdeBP | Not quite right. The umask masks whatever permissions the process supplies when creating the file. It is not required that applications use 0666 or 0777. That is merely common. | |
| Dec 20, 2019 at 17:39 | vote | accept | Chloé | ||
| Dec 20, 2019 at 17:39 | comment | added | Chloé | Thanks for these explanations (and for the resources)! I've just run the command and indeed, my umask value is 002. I'm guessing then that at work it's not the same. I'll run umask there to confirm that. | |
| Dec 20, 2019 at 17:36 | history | edited | jesse_b | CC BY-SA 4.0 | added 444 characters in body |
| Dec 20, 2019 at 17:29 | history | answered | jesse_b | CC BY-SA 4.0 |