(In reply to comment #8)
> Dear Vitality,
>
> Now I have a question for you: If I look into the wine directory, there is c:
> and z:. Unfortunately I have many temp files ending in z:\temp (java classes
> or OLE files that I can't access even if I am the owner because the .NET
> reverted the rights). Now the z: does belong to root and there is thus no way
> that wine can access to the z: because c: is yolande and z: is root. How do you
> solve that then? Do you have a sudo for z: in the middle of an installation
> procedure (please note that z:\temp does also belong to root).
>
rm -rf ~/.wine
Clearly it's screwed up. Don't f** with something you have no concepts about. Still don't see a bug here. So far you've been talking about how badly you managed to break your setup.
(In reply to comment #12)
> @Vitaliy: For those "smart" users running wine through sudo, I have written a
> patch which was rejected - maybe it gets its revival here.
Ask Julliard, not me.
(In reply to comment #11)
> Temp files should go under c: somewhere, if they go in z:\temp there's
> something wrong with your setup. In any case it's unrelated to this bug.
>
> Still, the actual problem that my hack was fixing could be fixed a better way,
> so this bug should remain open.
>
Hack what hack? I thought those not allowed in.
(In reply to comment #13)
> Do we want to support multiple users sharing the same prefix? I haven't seen
> too much about this lately, though I know in the past you could share a drive
> c, dosdevices and system.reg, but that the user.reg and userdef.reg had to be
> unique to the user. Is that still the case? If so, we could only check that
> user/userdef.reg are user owned/writable, but on the others, check that we have
> the correct permission, not ownership.
>
No, this can not be supported. Wineserver does not sync with registry on the disk. It only writes there on exit or periodically (if configured). So you'll loose someone's changes.
(In reply to comment #8)
> Dear Vitality,
>
> Now I have a question for you: If I look into the wine directory, there is c:
> and z:. Unfortunately I have many temp files ending in z:\temp (java classes
> or OLE files that I can't access even if I am the owner because the .NET
> reverted the rights). Now the z: does belong to root and there is thus no way
> that wine can access to the z: because c: is yolande and z: is root. How do you
> solve that then? Do you have a sudo for z: in the middle of an installation
> procedure (please note that z:\temp does also belong to root).
>
rm -rf ~/.wine
Clearly it's screwed up. Don't f** with something you have no concepts about. Still don't see a bug here. So far you've been talking about how badly you managed to break your setup.
(In reply to comment #12)
> @Vitaliy: For those "smart" users running wine through sudo, I have written a
> patch which was rejected - maybe it gets its revival here.
Ask Julliard, not me.
(In reply to comment #11)
> Temp files should go under c: somewhere, if they go in z:\temp there's
> something wrong with your setup. In any case it's unrelated to this bug.
>
> Still, the actual problem that my hack was fixing could be fixed a better way,
> so this bug should remain open.
>
Hack what hack? I thought those not allowed in.
(In reply to comment #13)
> Do we want to support multiple users sharing the same prefix? I haven't seen
> too much about this lately, though I know in the past you could share a drive
> c, dosdevices and system.reg, but that the user.reg and userdef.reg had to be
> unique to the user. Is that still the case? If so, we could only check that
> user/userdef.reg are user owned/writable, but on the others, check that we have
> the correct permission, not ownership.
>
No, this can not be supported. Wineserver does not sync with registry on the disk. It only writes there on exit or periodically (if configured). So you'll loose someone's changes.