Make POSIX.py work under Cygwin

[dclark]

On Cygwin, there is no "root" or "UID 0" user, because the users are all taken from the Windows system. I believe the only constant is the "SYSTEM" account; I don't think the UID of "SYSTEM" is consistent however. For groups, there are both "SYSTEM" and "root"; I'm not sure which would be better to use, SYSTEM I'd guess for consistency.

I'm thinking maybe I should rollback my uid/gid normalization stuff and just make the default uid/gid hard-coded platform-specific; so the client would detect what system it's on, and do this:

OS	Default User	Default Group
AIX	root	system
Cygwin	SYSTEM	SYSTEM
Anything else	root	root

Thoughts? This would be client-side-only, unlike the current solution.

Other than this Bcfg2 seems to work fine under Cygwin (Python 2.5.1, m2crypto 0.17 build from source, bcfg2 0.9.5pre1). Of course only "Action" and "POSIX" client tools show up.

[solj]

I have figured out a way to accomplish different default permissions using per-plugin info.xml files. I have an example working for Cfg (but it doesn't yet use the FileMonitor? code). Once it does, I think this is the best way to handle differing architectures.

[solj]

Replying to solj:

I have figured out a way to accomplish different default permissions using per-plugin info.xml files. I have an example working for Cfg (but it doesn't yet use the FileMonitor? code). Once it does, I think this is the best way to handle differing architectures.

I'm still planning on integrating this, but the preferred way to handle different architectures is via dynamic groups using Probes. This will allow you to set differing permissions based on groups in info.xml files.

[solj]

I have also tested that bcfg2 works fine under Cygwin using the latest python (2.6.5) along with the built-in ssl module. All POSIX entries types, with the exception of device work as expected.