properly set dependencies for NSIS and wix targets to build loopback target
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
do not install a second loopback adapter if one is already installed.
====================
1. Custom actions should not depend on any library that is not in the Windows distribution. Change makefile to link
with a static runtime.
2. Add common reporting mechanism to report ActionData messages back to the MSI process during the loopback
installation.
3. CoInitializeSecurity can be called only once per process. When running as a custom action DLL under the MSI process
we won't be able to successfully call this since the MSI process beats us to it.
====================
Compensate for difference in argument passing in MSI and RunDll32
1. We are packaging debug symbols for all builds. In a checked build the default is to install debug symbols while on a
free build debug symbols won't be installed unless asked to.
2. Change impersonation level for loopback installation.
3. Change UI to allow for ActionData messages during the long wait while the loopback is installed.
4. Add templates for displaying ActionData.
5. Parameterize language resources.
The afsloopback.dll will configure the LMHOSTS and HOSTS files for "AFS"
therefore it is safe to use the loopback adapter on win2000 even though
it does not support broadcasts
Construct a new afsloopback.dll which contains the routines
for installing, removing, and verifying the existance of
a loopback adapter. This dll will be used by both the NSIS
and the Wix installers.
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
Update the wix installer to use the new version of instloop.exe
which uses the new afsloopback.dll
1. Fix choice for logon options to include only 'not integrated',
'integrated' and 'integrated with high security'.
2. Add configuration page to select whether or not to run afscreds.exe
when logging in and also choose the command line
options for afscreds.exe.
3. Assert that all dependencies are satisfied at install time when
installing the server component.
4. If running in full UI mode and installing the server component,
the user is notified about dependencies and given a
choice to review selections or just let the installer add the
required components.
Update README-NT to include details on Wix MSI installer builder.
Modify build system to create work directories and provide "wix"
and "install-wix" build targets
Begin the process of supporting multiple sysnames on Windows as is
done on Unix. These changes replace the internal variable with a list
of sysnames.
Still to do: change command line interface to allow entry of multiple
names; and replace cm_ExpandSysName() with code similar to Unix which
allows expansion of one element in the list at a time.
place 'auth' before 'afsdobjs' to ensure creation of afs/cellconfig.h
allow DESTDIR to be specified as an arbitrary location earlier in the
build process.
New BSD License for compatibility with GPL and NSIS licenses.
Add Loopback Adapter installation
Add Debugging Symbols for all builds (optional module)
Add user configuration of afscreds.exe startup
Add Is Administrator requirement to fs functions.
- checkservers with a non-zero timer value
- setcachesize
- newcell
- sysname with a new sysname list
- exportafs
- setcell
- setserverprefs
- storebehind
- setcrypt
- cscpolicy
- trace
Should create a user group to which users can be added so that
non Admin users can issue fs commands.
The fixed timeout of 19 seconds was too short. Should be set to the
value of HardDeadtimeout as set by cm_conn.c. The failure to specify
an adequate timeout value prevented successful Hibernation and Standby
mode access when network connectivity was not available.
