-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (Ref: original "Cygwin permissions problem" and related threads)
FYI: I managed to resolve my issue by completely re-installing Cygwin from scratch after having added (and allowing to propagate) the "Everyone" group (Read and Execute only) to my set of permissions [for all of my partitions]. What I find odd(?) about this whole episode is that the "Everyone" group should apparently be required [by Cygwin] like that. Could someone explain that to me? The reason I personally find it to be somewhat "odd" is simply because my Windows system behaves perfectly (just fine) without it. Now I know that Cygwin (i.e. *nix) is NOT Windows and vice versa, but why does Cygwin (*nix?) apparently choke whenever none of the (its?) files are given any type of "public" access? (Which is what the "Everyone" group is for, yes?) It seems to me one *should* be able to do what I was doing (i.e. only assigning explicit "private" (i.e. no public) permissions/access to all of my files/folders) without any serious side effects, but apparently not. Could some kind soul out there help me to understand why *SOME* type of "public" permissions set is [apparently] required by Cygwin? (*nix?) Thanks. - -- "Fish" (David B. Trout) [EMAIL PROTECTED] Fight Spam! Join CAUCE! http://www.cauce.org/ -----BEGIN PGP SIGNATURE----- Version: PGP 7.0.4 iQA/AwUBQRmCH0j11/TE7j4qEQLOdgCgoCK23ryFYDroeJp2+s2UKpxjaFEAnjw/ hN0FHEwvNjIuCd8fnQNT2zmh =HGSo -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/