Today I released sys-win32etc. The major change is that you can do lookups against a remote server instead of a local machine. Unfortunately, I have no way to test this - help wanted.
About the only *bad* news is that the memory leaks have gotten worse. I have no idea why. Not to panic, though - it doesn't matter unless you plan on calling these functions in a continuous loop (for whatever odd reason). Still, I'd like to nail them down.
Another issue - Ruby's Etc module doesn't support the 'set' side of the house (setgrent, sethostent, etc). But I really have to wonder how often anyone uses these functions anyway. I have *never* seen them used anywhere, and I suspect most admins would rather perform their functionality manually rather than programatically. That being said, they *could* be supported on Win32 as well.