Previous Topic: Operational CharacteristicsNext Topic: Install the APK Separately


Windows-specific Information

File Names

Unless otherwise stated, names in this document are in the CygWin file namespace, which emulates a Posix system.

Note: These names cannot be used with any non-Cygwin utilities. This includes the APK binaries themselves, such as vme and udlparse, and all the native Windows command line tools. Most Cygwin utilities will accept either a CygWin name (posix-style) or a Windows name (for example, C:\path\), with the exception of those that consider strings with ":" in them to mean computername:filename, for example, scp, rsync, and notably tar. The latter can be forced to accept a Windows name with the --force-local option.

To convert a file name between the Windows and Cygwin namespaces, use cygpath.

windowspath=`cygpath -w /var/applogic/appliance.desc` 

Disk Mounts

When specifying a mount point for disks, use the following names, as desired:

X - a single letter (A,B,D-Z) will make the disk accessible as X:\.

X:\ - same as X

C:\dir1\[dir2\...] - makes the disk accessible in the given sub-directory of the boot file system. If the directory does not exist, it will be created.

Note: You should not allow the APK to create the directory. The default directory permissions may differ from your needs.

Leaving a disk without a mount point specified in the class descriptor causes the APK to ignore the disk and leave its mount assignment in Windows as-is. In this case, any mount point assignment for that disk performed manually from Windows itself is persistent and takes priority over assignment of the same mount point to another disk using the class descriptor. The latter assignment will have no effect and will leave the disk unmounted. For example, if you have specified this in the class editor / Modify dialog:

disk 0 -> (boot)
disk 1 -> (no mount assigned)
disk 2 -> Z:\ 

and you log into the appliance, remove Z from disk2 and assign it to disk1. Z will remain assigned to disk1 across reboots. The disk2 -> Z assignment in the class descriptor will not take effect. Disk2 will not be mounted anywhere, until Z is removed from disk1 or another assignment other than Z is set for disk2.

C:\ is reserved and cannot be assigned as the mount point for any disk. Any assignment for the boot disk will be ignored and reported as mounted on C:\ in the appliance instance descriptor.

Do not use mount paths with sub-directories on any drive except C:. Doing this may cause your mount to be un-usable since it depends on the order in the disks are mounted.

Windows will not refuse to mount an unformatted disk or one formatted with a file system that is not understood by Windows. There will be no error or warning at all when the APK assigns the mount. However, attempts to access the mount point and any subpaths fail.

User Names

The APK installation script makes the CygWin alias for the Administrator be root. Therefore, root will be the user name seen by any CygWin binary and display as the current user name in a CygWin shell, and in directory listings. This setting allows accessing the appliance using the remote shell command ( 3t ssh component-name).

The mapping between CygWin user names and Windows user names is not automatic. It is described in the /etc/passwd and /etc/group files, which are not automatically updated when adding/removing Windows users. CygWin includes utilities to maintain the /etc/passwd and /etc/group files. When using these utilities, preserve the special mapping for root created by the APK. If not, the ssh login from the grid will stop working.