Microsoft KB Archive/246378

From BetaArchive Wiki
Knowledge Base

Configure Scripts and Porting - INTERIX Target Directories

Article ID: 246378

Article Last Modified on 10/30/2006


  • Microsoft Interix 2.2 Standard Edition
  • Microsoft Interix 2.2 Standard Edition
  • Microsoft Interix 2.2 Standard Edition
  • Microsoft Interix 2.2 Standard Edition

This article was previously published under Q246378


The following discusses where you should install software on an INTERIX system:

Installing software in $INTERIX_ROOT/bin or $INTERIX_ROOT/usr /contrib is not recommended for the following reasons:

  • If the new binary has the same name as an existing binary, your new binary will be replaced when INTERIX is reinstalled or upgraded.
  • Even if it has a different name from any existing binary, it is sometimes convenient to be able to remove existing software before a reinstallation, by using a command such as:

rm -rf $INTERIX_ROOT/bin $INTERX_ROOT/usr/contrib

This is not possible if there are local files installed in those directories. If you are the only user who logs in to your INTERIX system, you may want to install in the $HOME/bin directory and add that directory to your PATH. This is convenient, but it means that those binaries are unavailable if you have to log in as Administrator. You may want to create directories for local binaries, such as $INTERIX_ROOT/usr/local/bin. Be sure to add that directory to the default PATHs set in the global login files, and make sure that the permissions on the directory are set correctly.


The previous excerpt was taken from technote 0007 entitled "Configure Scripts with INTERIX". Review this note for a more detailed description of the use of configure scripts when porting code with INTERIX.

For additional information on configuring scripts with INTERIX, see:

Keywords: kbinfo KB246378