*** What You Need to Know About Windows Services for UNIX 3.5 http://www.windowsitpro.com/Windows/Article/ArticleID/42265/42265.html
In January, Microsoft released the latest version of its UNIX interoperability tool, Windows Services for UNIX (SFU) 3.5. This version of SFU adds support for Windows Server 2003 (and, consequently, drops support for Windows NT 4.0), extends the Interix execution environment to support more complex applications, and includes a few interesting new features and licensing terms. Here's what you need to know about SFU 3.5. Why and Where Microsoft first introduced SFU to answer complaints that it lacked an interoperability strategy in this increasingly cross-platform world, and it wanted to help enterprises move legacy UNIX applications to more easily managed Windows machines. SFU offers a full UNIX execution environment that gives UNIX administrators, developers, and IT pros the tools they want. SFU includes directory and file-system integration, so for example, you can link UNIX logons to Active Directory (AD) logons and perform other basic integration tasks. Also, developers can use SFU to integrate UNIX solutions into COM objects, Web services, Microsoft .NET applications, and other programs. New Features Microsoft has significantly enhanced and tuned NFS, Network Information Service (NIS), and the Interix subsystem to perform more quickly. The Interix execution environment now supports the UNIX P-Thread multithreading system, which lets developers port over more complex custom applications than they could in earlier versions. The company has also improved SFU POSIX support. And in addition to the latest version of the X Window System, X11R6.6, SFU 3.5 includes the latest version of many popular UNIX command-line tools. The best feature of SFU 3.5, however, is its licensing cost-there is none! The product is available for free to users of Windows 2003, Windows XP Professional Edition, Windows 2000 Server, and Win2K Professional. Previous licensing terms required a $99 fee per client or workstation. Recommendations SFU 3.5 is an excellent solution for anyone migrating UNIX applications to Windows or trying to interoperate between UNIX and Windows systems. Cynics will note that Microsoft's new pricing strategy was influenced by the free nature of Linux, but who cares? I highly recommend SFU 3.5. *** Microsoft Windows Services for UNIX (SFU) 3.5 (now free) (BLOG) http://www.oreillynet.com/pub/wlg/4201 My work is in a decidely duo-culture OS world: Microsoft Windows and Linux. I had heard about Microsoft Windows Services for UNIX but never took a close look at it. Microsoft released a new version (3.5) and lowered the price (from $99 to FREE) this week. This (no cost) prompted me to take a closer look at it. You can read a detailed introduction white paper about SFU at http://www.microsoft.com/windows/sfu/techinfo/overview/sfuwp.asp or the reviewer's guide at Interop Systems. Here's a much truncated summary of the items that interested me: * SFU runs on both Windows workstations (2000 or XP with appropriate Service Packs) and Windows servers (2000 or 2003 with appropriate Service Packs) * Client, server, and gateway for NFS * Telnet client and server * C-Shell and Korn Shell plus more than 350 other utilities * Symbolic and hard links on NTFS and NFS file systems * Password synchronization between Windows and Linux One ironic note: As I said I split my time between Windows XP and Red Hat Linux boxes. I happened to be on my Linux workstation while investigating this new SFU release. I downloaded both the white paper and reviewer's guide to read in OpenOffice 1.1. OpenOffice crashed while reading the reviewer's guide. However, I restarted OpenOffice, opened the reviewers guide again and was able to read it all the way through on the second try *** Windows Services for UNIX 3.5 Product Overview http://www.microsoft.com/windows/sfu/productinfo/overview/default.asp Windows Services for UNIX 3.5 provides a full range of cross-platform services for blending Windows and UNIX-based environments. With Windows Services for UNIX 3.5, IT professionals can transfer UNIX-based tools and utilities they are already familiar with to the Windows platform and extend the value of their UNIX applications. UNIX on Windows The Interix subsystem technology provides a universal environment that can run both Windows and UNIX applications on a single system. Through Interix, you can reduce development time while making use of existing employee skill sets. Interix technology provides a UNIX environment that runs on top the Windows kernel, enabling UNIX application and scripts to run natively on the Windows platform alongside Windows applications. With this capability, you can continue to get value out of your UNIX scripts and applications by reusing them on Windows. Windows Services for UNIX 3.5 also includes more than 300 UNIX utilities and tools that behave as they would on UNIX systems, plus a software development kit (SDK) that supports more than 1,900 UNIX APIs and migration tools, including make, rcs, yacc, lex, cc, c89, nm, strip, gbd, as well as the gcc, g++, and g77 compilers. *** Windows Services for Unix 3.5 (REVIEW ZDNET) http://reviews.zdnet.co.uk/software/os/0,39024175,39150908,00.htm Microsoft wants people to use its operating systems and applications rather than anyone else's. No surprise there. Providing a toolkit to help users migrate from other platforms to Microsoft's own isn't exactly unprecedented either. But to provide a toolkit that makes Windows behave like Unix may sound a little far fetched, especially when it contains open-source software. When you consider that all this is given away, it sounds too good to be true. Unfortunately, in some respects this is the case. Windows Services for Unix (SFU) is a toolkit designed to allow Unix users to integrate with and migrate to a Windows environment without having to throw away applications, scripts and other familiar tools. This typically includes shell scripts to automate various tasks, but can include running applications written for Unix on a Windows machine. Previous versions of SFU have been available, but none is as comprehensive as version 3.5. They've also previously been charged for: version 3.5 is a free download, or a minimal-cost CD-ROM. What you get SFU 3.5 consists of a POSIX-compliant subsystem, a server and a client for NFS, a Windows-to-POSIX name mapping system, an NIS server and a telnet server for those versions of Windows that don't already come with one. The POSIX subsystem is meant to be a complete replacement for a Unix environment, and includes the GNU C compiler and libraries. The other components allow the two environments to interoperate if necessary, although if you're happy treating them as entirely separate systems, you can get away with installing few, if any, of these other components. Name mapping The name mapping service manages the relationship between Windows user names and the Unix user names used for the other services provided. This is necessary because of the different models used for user names in the two systems. The service allows one-to-one or many-to-one mapping of users, so that lots of different Windows users can be mapped to the same Unix user. This service underpins all the other Unix-like services provided as part of SFU, and will need installing on most machines on which you want to use SFU if you want to use a single set of credentials for both environments. NIS server The NIS server allows the Windows machine on which you've installed SFU to act as the NIS master for all the Unix systems on your network. This isn't the same as participating in an NIS domain using the name mapping service. Instead this uses a Windows Domain controller as the NIS domain master. You need to be using Active Directory to use the NIS server, since an AD container object is used to manage the NIS domain. NIS server supports Unix machines as backup NIS domain servers, but the Windows system has to be in charge. If you do choose to move across to the NIS server, a migration wizard is provided to move your existing user accounts across to Active Directory. NFS client The NFS client and server allows Windows and Unix systems to share files with natively. The server allows you to store files that were previously stored on a Unix host on a Window server without needing to install extra software on any Unix clients that need to access those files. Equally, you can use the client service to access files stored on a Unix server. There is also an NFS gateway in SFU, which allows a Windows server to serve files held on an NFS server to native Windows clients. However, you can achieve the same end either by installing the NFS client on users' machines if there aren't many of them, or, for more users, by migrating the files to a Windows server and installing the NFS server. One oddity of the NFS client is that since this is a Windows component, the mount command isn't available under the POSIX subsystem, only the Windows command line. This could possibly cause some problems if your scripts involve mounting NFS volumes -- you'll have to mount the volumes manually before running the scripts, or invoke a separate Windows batch file to do it. Either way you'll have to rewrite your script. All the services in SFU can be administered using the Windows management console or via the Windows command line. This latter option allows you to administer the services remotely through the telnet server supplied with SFU (or the one supplied with later versions of Windows). It will also allow automated provisioning of these services on multiple machines -- you can run a batch file to install whatever components you want. POSIX subsystem The POSIX subsystem is a third-party product from Interop Systems, called Interix. As standard you're supplied with Korn and C shells, the GNU C compiler and libraries. Most standard Unix utilities -- grep, awk, sed, for example -- are included with Interix. However, there's a strange mix of GNU tools, and some provided by Interop Systems, which appear to be versions of BSD tools ported to Interix. This hybrid GNU/BSD environment causes a few minor problems. For instance, the version of tar installed doesn't read some tar files created in other versions properly, resulting in an error, despite all the files in the archive having been unpacked correctly. This initially caused us some problems when trying to install some pre-packaged applications, but installing the GNU tar program solves this -- another alternative you have is to use a Windows archive application that understands gzipped tar files to unpack the archive. The shells run as Windows console mode applications. They don't have QuickEdit mode enabled by default, so if you want more Unix-like copy and paste operations, you'll need to alter the program properties for each shell or command-line application you use. Despite the libraries for X Windows applications being provided as part of Interix, there isn't an X Server for Windows supplied with SFU. Microsoft points out the large number of free and commercial X Servers already available, and says that if you need to run X applications locally you should obtain one of them. Filesystem Interix emulates a single-rooted filesystem, which supports hard and symbolic links. The root of the emulated filesystem is the SFU install directory, with Windows drives being represented as devices, so that, for instance, D: is /dev/fs/D -- if you need files from separate Windows volumes to appear at more convenient points in the Interix filesystem, you'll have to link them manually. There are some issues with paths and file names containing spaces, in that some Unix programs aren't able to read some paths properly, even though spaces are generally allowed in Unix filenames, and the shells provided are able to work with them. Perl is the only scripting language supplied with SFU. You can install Perl under the Unix environment, and ActiveState Perl for Windows is also provided, so you can run Perl programs in either system. However, the two don't really interoperate, so that libraries installed in one environment aren't necessarily available in the other. Some clever tweaking of symbolic links will make this possible, but it's not the default configuration. Interix is claimed to be fully POSIX compliant, and we can't challenge that claim. However, it seems that this may not be enough to make it easy to move applications from your existing Unix platform to Interix. In our tests, GNU applications don't necessarily configure, compile and install without tweaking. We couldn't get the standard Unix distribution of Python to install, for example, despite a successful compilation. The fact that Interop Systems has made available special packages for many GNU applications is evidence that porting applications to SFU may not be as straightforward as is claimed. Alternatives There are alternatives available for running Unix applications on Windows, but they rarely include the other services that Microsoft is providing here. It might be possible to assemble a similar toolkit yourself from third-party components, but that's more work than just downloading SFU. Alternatively, you could mix-and-match the components from SFU and other toolkits to get the combination you need -- in many cases, you don't even need to install the components on the same machine to get the same facilities. Windows Services for Unix 3.5 will be useful to developers working in a mixed environment, since you're able to run scripts on your desktop that would otherwise have to be run on a separate host. Similarly, Unix system administrators can use some of SFU's components to perform tasks in the same way as with their Unix machines. If you depend heavily on the GNU toolkit for your work, you may be less than impressed with SFU, since you'll have a job on getting many packages to install correctly -- it's not impossible, but a certain amount of tweaking will be needed. SFU is interesting as a glimpse of the way Microsoft is taking Windows -- more command-line administration being one example. It's unlikely to be the deciding factor in mass migrations from existing Unix installations to Windows, but if you've already made a decision to move to a purely Windows environment, SFU will ease the pain somewhat. If you want to use Windows for some jobs that would otherwise need a Unix machine, SFU is a neat toolkit, but there are others available. *** Microsoft *nix http://www.dashes.com/anil/2004/01/19/microsoft_nix What if Microsoft shipped "Linux for Windows"? On Friday, Microsoft released a free download of Windows Services for Unix version 3.5, a significant upgrade to the Unix integration product they've been offering for about 5 years. I've used it before, mostly as an NFS client, but there's some remarkable changes this time around. The Services for Unix (SFU) are free to download and consist of an entire Unix environment installed as a native subsystem on Windows. For those of you who don't know your Windows NT/2000/XP/2003 history, the NT kernel has always supported running multiple subsystems, and NT has always shipped with a Posix-compliant command-line subsystem, largely for checklist compatibility with some now-obsolete government requirements. Unlike tools like Cygwin, which run on top of the standard Windows shell, SFU implements the Interix subsystem as a true peer to the Windows shell. But to that base SFU 3.5 adds some extraordinary new features. Both the Korn and C shells are included. A single rooted file system is now supported, finally abandoning the need to include drive paths in applications or scripts. And speaking of scripts, SFU includes Perl 5.6.1. There's even the full complement of standard Unix utilities, including awk, grep, sed, tr, cut, tar, cpio, less, at, cron and batch. Essential applications like bind, sendmail and ftp? Present. Even gcc, gdb, and make are in the package. There's a lot of other stuff, of course, including the first tools to expose Windows' long-dormant file system support for junctions as symbolic links in the Interix environment. There's the above-mentioned NFS support. There's all kinds of user account synchronization features. A real version of telnet. But what's most astounding, perhaps, is not the fact that I can now untar most perl scripts as-is and have them run on Windows. (I'll be testing out Movable Type shortly, of course.) What amazes me is that this product has slipped under the radar for so long. Any bets as to whether Longhorn includes this functionality out of the box? And It seems to me that this collection of functionality will rapidly allow Windows users to cover 90% of the things that OS X users are doing with Darwin. Interesting. Download: http://download.microsoft.com/download/a/1/c/a1ca7af1-a6e3-46e7-874a-4c5d8c0fb3b7/SFU35SEL_EN.exe http://download.microsoft.com/download/6/d/8/6d8210f1-49b9-457e-816b-860242f2d5ef/sfu35new.doc ------------------------ Yahoo! Groups Sponsor --------------------~--> Take a look at donorschoose.org, an excellent charitable web site for anyone who cares about public education! http://us.click.yahoo.com/1gzaND/8WnJAA/HwKMAA/4tWolB/TM --------------------------------------------------------------------~-> -- -------------------------------------------------- Berhenti (Quit): [EMAIL PROTECTED] Arsip milis: http://groups.yahoo.com/group/smun65 Arsip Files: http://groups.yahoo.com/group/smun65/files Website: http://smun65.blogspot.com -------------------------------------------------- Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/smun65/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
