On Friday 29 June 2001 16:25, you wrote:
> 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 unfortunately Windows is not to be trusted
> to not do something outside of your notice and screw things up.
>
> -David
>
David,
Thank you for a lucid explanation of why Netraverse has chosen to enforce the
no root operation. I did not realize the windows spaghetti code wasn't smart
enough to protect itself from itself. I will rethink my win4lin modus
operandi and come up with a another solution I can live with without mass
duplication of data on my hard drive. I have already attempted linking files
via the \mydata link to Linux to mixed reviews when operating in a
bi-directional mode. Unilateral mode works well.
Thanks for your input David. I'm a Physicist not a programmer.
Keep up the good work. Win4lin has been found by us to be a superior product
in many situations when compared to Vmware, which I also own.
Harry
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
