It is because you don't really know or control what Windows is writing to.
You may know what you are doing, but you don't know what Windows is doing.
Win4Lin shares certain read-only files, and depends on them not getting
corrupted. It uses the normal Linux file ownership and permissions to
protect them from being written.
If you ran Windows as root, then there is the possiblity of it corrupting
these shared "read-only" files. In the early days of geting Windows95
to work this happened, so now it is not allowed.
Personally, the idea of letting Windows loose as root on my system is
just too horrible to imagine. You can though run a DOS session as root
if you like living dangerously.
-David
Bill Hayles wrote:
>
> Hi, Brandon Darbro,
>
> On 29 Mar 2001 06:51:25 -0800 you said:
>
> > You don't want to run it as root. You shouldn't be running anything as
> > root unless it requires it... and then you should be darn well aware of
> > what its doing before you do.
>
> We all know that. But everything else about Linux assumes that root
> knows what they're doing.
>
> I wouldn't run as root by default, but I'd like the option to, if
> necessary. It should me MY decision, on a single user machine.
>
> Bill Hayles
> [EMAIL PROTECTED]
> _______________________________________________
> Win4Lin-users mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-users
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
