> 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
Exactly what permissions are these files?
Off hand I don't recall any unix version where root can write
to a file with no write permission at all.
> hard-to-diagnose problems. So it is very important to enforce the
> UNIX/Linux file permissions when Windows has access to your filesystem.
--
Mark Evans
St. Peter's CofE High School
Phone: +44 1392 204764 X109
Fax: +44 1392 204763
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
