steve1977 3 hours ago

> sudo makes sense as a name

It doesn't though. There is no concept of a singular superuser like there is on UNIX. On Windows you have Administrator, but that is a role that can be assigned to any user.

And Administrators do not have full power, that would be the SYSTEM user. Which you cannot switch to with Sudo for Windows however - but you can with the runas tool, which has been around for decades.

▲

vbezhenar 2 hours ago | parent [-]

Minor nitpick, but there's not necessarily a single super user in UNIX. You can create multiple users with uid=0 and they all will be super users.

▲

steve1977 an hour ago | parent | next [-]

See sibling reply. The uid is what defines the user, the name is just a convenient alias.

▲

vbezhenar an hour ago | parent [-]

Not really. You can have separate users with separate $HOME, separate passwords, separate groups, separate everything.

User is user. Uid is uid. It's not the same. Uid is used for file permissions, that's true.

	▲	ButlerianJihad 18 minutes ago \| parent [-]
		If you try and set up "separate users" with "separate $HOME" that map to the same UID, all those "users" will "own" all those same files, and all processes started by one another. They would be able to kill processes, delete/modify/add files, impersonate one another. Because they are the same user. You would be unable to enforce quotas or privacy for any of them. Whatever they did on the system would be indistinguishable, because their process UIDs would be identical. Any files they created would be owned the same. Sure, set them up with unique lists of GIDs; it really doesn't matter in the end. I have no idea what you mean "User is user", but you are right: UID is not the same as a username. The username exists only in the passwd(5) database, and not in the kernel, like at all. The kernel has no idea what usernames are, and that's why they're irrelevant to user administration.

▲

ButlerianJihad 2 hours ago | parent | prev [-]

But they all have the same UID, and are technically "the same user", even if you foolishly confer disparate usernames and passwords on them. When the system reverse-maps their UID it will display "root" because there is, ultimately, only one superuser on Unix.

The situation is the same for any userid and any groupid. If you try creating three ordinary users with a UID of 3005, they will be, essentially, the same user. There is no way at the system level to differentiate them, after they have authenticated. Because their files and processes are owned by the same UID.

This sharing of UIDs is generally discouraged and quite undesirable. It makes systems administration a real mess.