In Slackware by default the only group which gives the access to some media devices is the disk group. I can imagine that some other distros use the same way. Of course this is partially the problem of users like - later I've created cdrom, floppy, etc. groups, but forget to remove myself from disc group. But I also think Wine should not touch places like MBR. Very rarely we even need to run some applications as root, so it would be a very bad practice if every of those apps just try to access MBR, when actually no need to do that.
------- Original message ------- From: Peter Beutner p.beutner@gmx.net To: wino@piments.com Subject: Re: Fwd: Re: Fwd: MBR was destroyed Date: Sunday 20 November 2005 23:24
wino@piments.com schrieb:
So is the conclusion that users need to set up a special new user with super restrictive rights to protect the system from bugs in wine?! My confidence in wine has just taken a knock.
It's the other way around. This never would have been possible with a normal user account. But if somebody "creates a special user" by extending his rights and putting him into the disks group, he should be aware of the implications. I don't think there is a "documentation bug".
Of course that is _not_ an excuse why wine wants to write to the MBR ;)