The impending release of version 3.0 of Microsoft's Services for Unix (SFU) has me thinking about how there is more than one way to go about enhancing the interoperability of Windows and Unix systems. The irony is that while Microsoft has come up with a package to help Windows systems look like and act as peers on a Unix network, the Unix crowd has come up with Samba, which makes Unix systems play by the rules of Windows networks. Although interesting, the irony isn't all that important; each approach is useful to different sets of needs. And there are other options as well: third parties like Attachmate, Hummingbird, and others have interoperability solutions.
Interoperability means many different things. Consider Samba, which lets Unix, Linux, and Windows systems interoperate on Windows-oriented SMB networks. Microsoft's SFU 3.0, originally based on products from a company called Softway that Microsoft bought, includes an NFS server to let Windows systems share files on Unix networks, and services to synchronise passwords between Unix networks and Windows domains. SFUalso includes Windows implementations of a variety of standard Unix utilities, like cron for scheduling jobs.
I would even look at terminal-based solutions as a potentially adequate interoperability solution. Need to access Unix applications from Windows? Use an X server. Need to access Windows applications from Unix? Use Citrix Multiuser. In fact, you can use Citrix on either end: they sell a Unix version of their Citrix Multiuser product. Because Citrix's ICA protocol is so much more efficient than X, it may be a better solution for sharing Unix applications, especially those accessed over slower links.
But the really interesting part of SFU is how it helps to port Unix programming to Windows. It was Microsoft that provided a lot of the original funding to ActiveState, the company that implemented Perl on Windows and is now a major core contributor to Perl. The ActiveState implementationof Perl, which allows the development of cross-platform scripts, is a major success and is included in SFU 3.0, which is only a minor convenience since it's also downloadable for free from ActiveState.
Of course there are similar products to assist in the porting of Window applications to Unix. Consider Mainsoft, which sells proprietary tools and libraries. And, if you've written your applications in a system like Java or Perl that creates cross-platform code, the whole issue is less of a problem for you, although it's not as cut and dried as it's often made out to be. SFU also attempts to let you run Unix scripts (sh, ksh and csh) on Windows. Mainsoft claims a very high level of support, although there are certainly things that wont work without some additional porting work (such as referring to specific directories such as /usr/local or c:winnt).
If you're running directory services, SFU comes with another tempting feature: The ability to synchronise between NIS and Active Directory. SFU includes tools to merge the NIS database into AD, which then operates as a NIS master.
For the actual interoperability requirements of a large enterprise, it seems to me that SFU goes further than the alternatives, but obviously Samba is free. This certainly can count for a lot since SFU 3.0 is priced at US$62-$99 per system, depending on your license agreement. And remember, you'll need a Windows server client license for any Unix systems that you run as clients of a Windows server.
Interoperability between Windows and Unix is a pretty mature market, but the market implications of that aren't so obvious. Does the availability of so many technologies mean that both platforms are entrenched, or does it mean that it's easier for customers to wean themselves off one platform or the other? The answer may depend on where you want to take your company.
3%
2%
Regards running UNIX apps on top of Windows and the comment:
"SFU also attempts to let you run Unix scripts (sh, ksh and csh) on Windows. Mainsoft claims a very high level of support, although there are certainly things that wont work without some additional porting work (such as referring to specific directories such as /usr/local or c:winnt)."
There is an open source UNIX environment for Windows called Cygwin.
It consists of two parts:
A DLL (cygwin1.dll) which acts as a UNIX emulation layer providing substantial UNIX API functionality.
A collection of tools, ported from UNIX, which provide UNIX/Linux look and feel.
The Cygwin DLL works with all non-beta, ix86 versions of Windows since Windows 95, (including XP) with the exception of Windows CE.
With Cygwin you can run multiple shells, scripts, cron, all the usual UNIX utilities, even X Windows using the Xfree86 port provided. You can access all Windows folders and mapped network drives, just as though they are other UNIX mounted filesystems/directories.
Best of all it really does work, and there is no need to install Linux, partition disks etc. The setup and installation is very easy, the setup application can run directly off the Cygwin web site; and you selectively install as much or as few of the packages you need.
For people who need interoperability, it's worth a look.
Rob.