Could it run suid or similar then?
Regards,
Nigel
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> David Peet
> Sent: Saturday, 30 June 2001 06:25
> To: [EMAIL PROTECTED]
> Subject: Re: [Win4Lin-users] Win4Lin root operation
>
>
> The reason is that for sane operation Win4Lin relies on some
> read-only
> shared files really being read-only and thus staying uncorrupted.
> In the early days when we were just getting Windows support
> implemented,
> if we ran Windows as root, it would occasionally write to one
> of these
> files it was not supposed to be writing to and thus causing odd and
> hard-to-diagnose problems. So it is very important to enforce the
> UNIX/Linux file permissions when Windows has access to your
> filesystem.
>
> Win4Lin acts the same was as Merge has, and has from the very
> first version
> that supported Windows. Basically Windows cannot be trusted
> to not hose
> your system. You as superuser can be trusted to use the system wisely
> when you are in that mode, but unfortunatly Windows is not to
> be trusted
> to not do something outside of your notice and screw things up.
>
> -David
>
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
