loader: more stringent sanity check

[Christopher Buck]

Strictly speaking, running as root is a OS level issue, not a wine
issue.   That being said, wine is being friendly if it notes the
possible issues with running as root.  That being said, letting the
user know the bypass switch or  when wine doesn't start up right away
is also friendly.

Perhaps we should be telling newbies how run "not as root", but that's
even further into the "it's not a wine issue" territory.

-Buck

On Thu, Mar 20, 2008 at 5:04 PM, Dan Kegel <dank at kegel.com> wrote:
> On Thu, Mar 20, 2008 at 3:55 PM, Michael Stefaniuc <mstefani at redhat.com> wrote:
>  >  >>  If we really need to have something then it should be at most a one-time
>  >  >>  warning (in a message box so people have a chance to see it) at
>  >  >>  wineprefixcreate time, with an easy way to disable it.
>  >  >
>  >  > Then the newbies will just click past it.
>  >
>  >  Put in a timer forcing the people to read it for 10 to 20 seconds. If
>  >  they click past that and still go on ... *shrug*. Welcome to the real
>  >  world: they are screwed already so let them screw them self up a little
>  >  bit more if they want.
>
>  We want to minimize power user annoyance
>  while also minimizing newbie system damage
>  and number of posts in wine-users saying "never run wine as root".
>
>  Four ideas are on the table:
>  - do nothing (but then wine-users is intolerable)
>  - just tell people in wine-users "don't tell people to not run wine as
>  root" (but that's poor practice)
>  - have wine abort (possibly with a gui warning) if run as root without
>  --nosanitycheck (but that might annoy power users)
>  - same, but put the check in wineprefixcreate (but newbies might bypass this)
>
>  Although I suspect users will just bypass the check if it's
>  only in wineprefixcreate, I'll code up that approach, it's
>  better than nothing, and Alexandre might go for it.
>  - Dan
>
>
>