Windows Services for UNIX components

You can use the Windows Services for UNIX installation program to install the following:

• Utilities. Provides commonly used utilities.
  • Base Utilities. Provides the Interix subsystem, a powerful, full-featured UNIX environment running as a separate subsystem on the Windows computer. Includes C and Korn shells, plus more than 350 utilities that run on the Interix subsystem. In addition, provides Windows-based administrator utilities and UNIX-style commands, plus the Windows-based Cron service for scheduling tasks and the Windows-based Telnet Client.
  • UNIX perl. Allows perl scripts to be run on the Interix subsystem. Installing UNIX perl also installs base utilities.
• Interix GNU components. Interix utilities and software development kit (SDK) tools distributed under the terms of the GNU General Public License (GPL)
  • Interix GNU utilities. Supplements the base utilities. Installing the GNU utilities also installs the base utilities.
  • Interix GNU SDK. SDK tools that supplement the Interix SDK. Installing the GNU SDK tools also installs the GNU utilities and the Interix SDK.
• Network file system (NFS) components. Support file and directory interoperability between Windows and UNIX systems.
  • Server for NFS. Exports Windows directories as NFS file systems, allowing UNIX-based NFS clients to access them.
  • Gateway for NFS. Shares directories exported by UNIX NFS servers as Windows shared directories, allowing Windows users to access them without installing NFS client software. You cannot install Gateway for NFS and Client for NFS on the same computer.
  • Client for NFS. Allows Windows computers to access files on UNIX-based NFS servers. You cannot install Client for NFS and Gateway for NFS on the same computer.
• Server for NIS. Enables a Windows server to function as a Network Information Service (NIS) server, integrating NIS domains with Active Directory and giving Windows Active Directory administrators the ability to manage Windows and NIS domains together.
• Password Synchronization. Password Synchronization makes it easy for users to maintain one password for Windows domains and UNIX systems, synchronizing them when one of them changes.
• Remote connectivity components. Allow users to access the computer remotely.
  • Telnet Server. Gives remote users the ability to connect to the server with any Telnet client software.
  • Windows Remote Shell service. Allows commands from remote computers to be run on the server.
• Authentication tools for NFS. Allow NFS components to authenticate users.
  • User Name Mapping. Associates Windows and UNIX user names, allowing users to access files through Interix or Remote Shell service, or to connect to NFS resources without having to log on to Windows and UNIX systems separately.
  • Server for NFS Authentication. Works with User Name Mapping and Server for NFS to allow UNIX users transparent access to files shared on Server for NFS. It should be installed on all domain controllers.
  • Server for PCNFS Similar to a PCNFS daemon (PCNFSD) running on a UNIX server.
• Interix SDK. A full-featured software development kit (SDK) to make it easy to create applications to run on the Interix subsystem. Installing this component also installs base utilities.
• ActiveState ActivePerl 5.6. Allows Windows-based perl scripts to be executed on the server.

Windows Services for UNIX supports Sun Solaris version 7 running on Scalable Processor Architecture (SPARC)–based computers; Hewlett Packard HP-UX version 11; IBM AIX version 4.3.3; and Redhat Linux version 7.0. Windows Services for UNIX Telnet, NIS, and NFS components should also work with other operating systems or products that use these protocols.

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.