Benjamin,
Regarding the umask you mentioned, this is a simple command to run. As
root, enter the following in an xterm:
chmod -u /usr/11R6/bin/wine
or whatever the correct path is to wine on your system.
The umask is a way of forcing a program to run as a specific user, no
matter who is actually running it. By using the above command as root, you
have now caused wine to run as user root, no matter if you actually call
it as user benjamin or anyone else.
This is, of course, a security risk, since anyone who runs this program
now has some sort of root access to the system, even if limited. And if
there is a buffer overflow or other security bug in wine, setting umask to
root may allow a user to even crack the system and get a root terminal!
Bad news. But if your system is primarily for just yourself, or your
family, then the security hazard is much less.
Hope this helps,
Dave
On Monday 21 May 2001 04:01, thus spake Benjamin Sher:
> Dear friends:
[snip]
> Checking again the documentation on Codeweavers' page, I learned that
> you need to run wine as "root" for Windows applications to work in
> Linux. Actually, the User's Guide lists three workaround, including one
> tactic involving a "root-file" in the user directory (which I tried but
> in vain) and another having to do with "umask" (which I did not
> understand) and something else that has to do with "shadowing".
--
"...[W]e preach Christ crucified: a stumbling block to Jews and
foolishness to Gentiles, but to those whom God has called, both Jews
and Greeks, Christ the power of God and the wisdom of God."
(1 Cor 1:23-24)
