And I noticed that they are different on Servers and Desktops
I had no idea they would be different.
On the server one of the permissions that stands out for me is the CREATOR OWNER (full control / subfolders and files only.
From what I can tell, when a user creates a folder on the root drive, that person will be given the permission of full control of that folder only and then CREATOR OWNER on that folder is also added with full control of subfolders and files only.
But for the desktop, on the root drive you are not given any full control of that folder.
@IRJ You are passionate about computers, you love to write code. Well, what's more exciting than being able to create your own plugins.
When you know that WordPress is today one of the most used CMS on the web, it would be really interesting to see how a plugin is made and to be able to create it yourself. [Check it here] (http://bit.ly/2KxPChJ)
To me a group is a collection of a certain type of user and is then used to streamline permissions to certain resources. EG Instead of giving read permission to Cathy, Joan and Frank, you can just create a group with them in it, and give that group read permission thereby simplifying your job.
I cannot for the life of me think why you would want a single user group with the same name as the user in it. Are there permissions that can only be assigned to a group rather than directly to the user?
What am I missing here?
Setgid creates group specific permissions for files in the directory with setgid turned on.
Having a group id also lets you do things like have root own a file and be able to modify it but let apache and only apache read it.
Edit: I see Romo beat me to it with the links. I didn't read them until just now.
This machine is part of our parent company's domain which I am not administering. What I got from their team is it might be due to SEP policies! Even though I disabled SEP on my machine, it still is the same issue. I am member of local admin group as well.