Thank you for posting those. I have never used any of them that I recall; Sticky Bit, SGID, and SUID. I read both links and the man pages for chmod and chown. All of this prompts learning and better understanding on my part. I am still a little unclear on Sticky Bit because of this in the second link
Setting the sticky bit tells Unix that once the concerned application is executed, it should remain in memory. Remember that Unix is a multi-user OS and was mainly designed so that multiple users can work simultaneously. Thus the logic used is that a program that exists in memory requires lesser time to start when a new user requests for the same program. Thus when one user has just used a program and then a new user wants to use the same program, the second user doesn't have to face a time delay for the program to initialize itself. It would be readily available to him.
So I understand Sticky Bit preventing any but the file owner from deleting the file and it improving performance if multiple users are logged in with it keeping the file in memory. Also that SGID and SUID would allow others access to the files depending on the chmod permission options he set.
Since Drew did not mention problems relating to a Multi-User environment but having to reset permissions after each reboot, as long as he prefaced the chmod command with sudo
and added 777 (rwx for user, group, and others) in the command, would it have accomplished all he needed?