Talk:Multi-user software

Add topic
Active discussions
WikiProject Computing (Rated Stub-class)
WikiProject iconThis article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Stub This article has been rated as Stub-Class on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
Note icon
This article has been automatically rated by a bot or other tool as Stub-Class because it uses a stub template. Please ensure the assessment is correct before removing the |auto= parameter.

Bogus external link deletedEdit

I deleted the erides link do to pornografic content — Preceding unsigned comment added by Mateia (talkcontribs) 14:25, 11 August 2006‎ (UTC)

And, from the description of the link, it didn't look at all relevant to this page in any case. Guy Harris (talk) 18:18, 25 February 2013 (UTC)

Multiuser vs. multisessionEdit

Some multi-user operating systems such as Windows versions from the Windows NT family support simultaneous access by multiple users... Isn't this called "multisession"? — Preceding unsigned comment added by (talk) 12:40, 22 February 2013 (UTC)

That may be what some people call it, but, as it "allows access by multiple users of a computer", it qualifies as "multi-user" by the definition of "multi-user" on this page. As it notes, you can have multiple users logged into a computer running (later versions of) an NT-family OS using Remote Desktop Services. Yes, each user gets a session, but that's the case with most if not all multi-user OSes. Guy Harris (talk) 18:11, 25 February 2013 (UTC)

Windows is not a true multi-user operating systemEdit

It never has been and it never will be, changes made by users in Windows operating systems often have wide ranging system wide effects. There is very little user space isolation in Windows. At best it could be described as a single user operating system with multiple sessions running on top of it. -- (talk) 09:44, 26 July 2014 (UTC)

Presumably meaning changes made by ordinary users often have wide-ranging system-wide effects, even if the user only wants to modify their own session. (Changes made by the super-user on a UN*X system can easily have wide-ranging system-wide effects.) What are some examples of this? Guy Harris (talk) 10:05, 26 July 2014 (UTC)
Yes correct, changes made to applications and setting in Windows by ordinary users can have system wide ranging system effects. Of course super users are different again. Unix based systems have user specific individual libraries, settings, apps and directories that effect a standard user, but are not system wide.
A part of the reason besides disk space usage as to why systems administrators lock down Windows systems and prevent standard users from installing apps is because of the fact that Windows does not manage libraries within its specific user space as a Unix system does, rather changes to libraries often occur in system wide directories such as C:/Windows/Sytem and C:/Windows/System32. Rather than the Unix alternative of /userspace/libraries and that's just one example -- (talk) 10:11, 26 July 2014 (UTC)
If there is no further discussion on the matter then I'm guessing the issue is resolved in Windows NOT being a multi-user OS and I'll do some tidying up? -- (talk) 11:43, 10 August 2014 (UTC)

I think for an operating system to be multi-user it isn't enough to have usernames and passwords, owner-group-world permissions on files, or even the memory management and task scheduler to allow two arbitary programs started by different people concurrently on different screens... even DRDOS 7 allowed that; a multi-user system needs to allow two or more people to use the system at the same time essentially as if they have the machine to themselves, so (apart from going a bit slower and having less RAM for themselves) they all should be able to run all the normal programs. A system that allows one user to run any software (e.g. GUI-based) and other users to only be able to do command-line stuff or anything as restricted as that, is not normally considered a multi-user system (but a single-user system with some multi-tasking - or some lesser definition like that) Maitchy (talk) 07:50, 12 April 2015 (UTC)

"A system that allows one user to run any software (e.g. GUI-based) and other users to only be able to do command-line stuff or anything as restricted as that, is not normally considered a multi-user system" Considered by whom? Citations? Guy Harris (talk) 09:13, 15 April 2015 (UTC)