|
A lot going on in this question.
One is concurrency, I think this is what you are really driving at. There are kind of two ways they handle this. One is to lock files on open to other users. Two is to reflect changes across all users that have file open.
Samba handles concurrency well for most tasks. CICS is an old way to handle this. That really isn't part of the title. Reply 2 addresses the question of why unique root. Generally no standard or limited user should have write access to / root. I think this part is outside of your requested use.
Linux by design could present almost any set of parameters to users. The file structure and ability to access filesystem and other user permissions can be configured.
Linux almost never changes how /root is. One could use any number off boot choices and even password boot access to construct a unique system at boot.
Look at concurrency means manage this issue. The other may be a dedicated software that does this much like some office products could present a file across a number of users.
|
