Craig73 wrote:a) I assume that multiple prefixes can be run in Wine because it is popular to install apps into seperate wineprefixes to isolate them... so I assume I can run these two apps at the same time with no risk of corruption? [Is this correct?]
Yes.
Craig73 wrote:b) So if I've copied my .wine folder to some shared read-only location, then symlinked to my local .folder all the read-only shared stuff, and the files that need to be modified (specifically profile/username, user.reg, and perhaps temp) are located in my local .wine folder, then why would I expect any corruption? [Note: I was wondering if MSOCache, DLLCache, Spool need to be local and user modifiable as well. I'm not sure why the userdef.reg the default user needs to be user modifiable.]
Depends on what m$ does with them. I would imagine some stuff checks if files needs to be upgraded by checking the files. But also all m$' patches modify registry. So you might endup with "half-installed" patch. But you talking about read-write access to files not read-only.
AlienWolf wrote:What about making a dedicated wine user with wine installed in its home directory
eg /home/wine/.wine
Then when a user wants to use wine they can start up wine or winefile by running the program as that user like:
sudo -u wine winefile
This way everybody will be running as the same user and it might also allow multiple users to run wine at the same time without coruption because they (might) be all using the same wineserver.
Just a guess, can't try it at work because we are being forced to use windoze
~ Alien Wolf
That's an idea...
For Wine itself to simply support multiple users' seperate application settings AND global ones, could it be an idea to have a special location on the disk to which all members of the "wine" group can read/write and have Wine itself have that directory considered the "all users" directory for applications, or something like that? This could enable the whole "install for all users" thing in certain applications to work correctly.
What about making a dedicated wine user with wine installed in its home directory
eg /home/wine/.wine
Then when a user wants to use wine they can start up wine or winefile by running the program as that user like:
sudo -u wine winefile
This way everybody will be running as the same user and it might also allow multiple users to run wine at the same time without coruption because they (might) be all using the same wineserver.
Just a guess, can't try it at work because we are being forced to use windoze
~ Alien Wolf
That's an idea...
For Wine itself to simply support multiple users' seperate application settings AND global ones, could it be an idea to have a special location on the disk to which all members of the "wine" group can read/write and have Wine itself have that directory considered the "all users" directory for applications, or something like that? This could enable the whole "install for all users" thing in certain applications to work correctly.
The problem is that wineserver has some race condtions and isn't yet
safe for multiple users. It's a low priority to fix, as there are much
more interesting/pressing bugs to fix.
