UNIX Interop in Vista Beta 2 and Longhorn Server - Port 25: The Open Source Community at Microsoft
< Back to Blogs
UNIX Interop in Vista Beta 2 and Longhorn Server by jcannon on July 06, 2006 03:06PM

Another guest blog this week from Identity Management Program Manager, Shamit Patel:
---------------------------------------------

Hi,
Last week, we released two new utilities to help customers achieve UNIX / Windows Interop. The first is a set of utilities and the SDK for the Subsystem for UNIX Architecture (SUA) in Vista Beta 2 & Longhorn. For those unaware, SUA is a native subsystem residing on top of the Windows kernel, just like the Win32 subsystem. It provides the basic infrastructure to run UNIX-based applications and scripts on Windows Vista (Ultimate and Enterprise) and Longhorn Server.

We've also released the UNIX-side components for Identity Management with UNIX. This essentially provides the utilities which enable password sync between Windows and UNIX environments. These are the UNIX-based utilities to enable successful synchronization.

I realize many of you may not be testing Vista or Longhorn, but for those who are, or have corporate testing, we would love to hear your feedback on the product, scripts and documentation.

Thanks all,
Shamit

Comments RSS
  1. cronos said:

    "For those unaware, SUA is a native subsystem residing on top of the Windows kernel, just like the Win32 subsystem. It provides the basic infrastructure to run UNIX-based applications and scripts on Windows Vista (Ultimate and Enterprise) and Longhorn Server".

    What is the meaning of running UNIX-based applications? Can I execute a binary of UNIX? There is a lot of versions of UNIX, and there is a lot of libraries needed for dinamically-linked software.

    posted at 12:40PM 07/07/2006
  2. Yogesh said:

    Just wanted to Add something to the Unix Interop story here with the presence of many more things in Vista Beta2 which actually talk Interop with Unix.

    - Service for NFS (NFS Client & Administration)

    - Telnet Client

    - Telnet Server

    - TFTP Client

    All available in

    "Control Panel -> Programs -> Windows Features"

    posted at 02:11PM 07/11/2006
  3. fluke said:

    Why is the ID Management code for Unix (PAM and ssod) not under the MS Shared Source license?

    The ssod code runs completely as root, listens for data from the network, and never calls chroot or drops it's priviledges for running sections of code that does not require root access.  Also, the binaries provided for RedHat are for versions that reached end of life in spring of 2004.  It would be nice to have permission to create RPMs for currently supported distributions.

    posted at 04:39PM 07/13/2006
  4. jdzions said:

    Cronos asks if SUA is capable of running UNIX binaries. The answer is "no"; SUA is a source-code compatible environment. If you have the source for the app (or the .so) you can recompile and relink under SUA.

    Jason

    posted at 06:21PM 07/18/2006
  5. jdzions said:

    Fluke asks a really good question about the license under which the PAM plug-in module (for intercepting password changes and forwarding them to AD) and the ssod daemon (for receiving password change notifications from AD) made available under the Microsoft Shared Source license.

    The easy answer: those components were originally developed before the Shared Source program existed in Microsoft, and the decisions about licensing for them haven't been examined since. (I didn't say it was a good answer, just easy.)

    I can't think of any good reason off-hand, myself, so I'll bring it up with the product team and see if I can convince'em to do so. Thanks for the suggestion.

    Jason

    posted at 06:25PM 07/18/2006
  6. posted at 01:08AM 08/26/2006
Post a Comment
*
*