The Aqua Connect Mappable File System (ACMFS) is a component from Aqua Connect’s next generation terminal server product do out in late 2010. Do to high demand from our customers Aqua Connect is making it available for use in its ACTS 3.x series.
What is ACMFS?
ACMFS is a file system driver that depends on the open source project known as “MacFuSE”. ACMFS allows a system administrator the ability to create a folder and have the contents of that folder be user specific but use a shared path. For example a folder called “/Applications/FileMaker” could be created and used with ACMFS, when accessed the contents of that folder is really the contents of “/Users/username/Applications/FileMaker”. The folder that is mapped can be anything and anywhere with the exception that the administrator must have write access to the parent folder and to the folder in question AND the contents of that folder is empty. The folder’s user specific contents can be anywhere and can include the users name, UID, GID, EUID, Graphical Session ID or nothing related to the user.
Why would I use it?
Examples of why you would use is listed below but the exact reason is specific to an organization’s need. Some examples include:
1. A folder that has per user configuration files where the application is not multi-user aware.
2. A folder that has the applications that users can use in them but the contents change depending on what group membership they have.
3. A needed application that is not multi-user aware and thus does not run unless each user has a private copy.
4. A method for scripting various pieces of data.
5. A folder for users to use that has user specific data or group specific data but is at a common location so applications and users can easily find them.
Of course the list goes on but those are some of the few reasons to use ACMFS.
How to use it:
Usage of ACMFS is easy but causing the configuration to be persistent is a bit difficult at this time since ACMFS currently does not have an installer and does not have a driver specific configuration file. One of the common usage methods is to place the ACMFS into the “/usr/sbin” folder, however the future permanent location for this file will be “/Library/Application Support/ACTS/Drivers/Filesystems”, (which you will note is not in ACTS 3.x series). The configuration for ACMFS is currently done through command line arguments in the future it will be part of the master configuration file located at “/Library/Application Support/ACTS/Configuration/Master.json”.
The command line usage is as follows: < 0 >/ACMFS –mountpoint < 1 > –prefix < 2 > <3> –suffix <4> (The numbered items found in the “< >” should be replaced along with the “< >” by the configuration choices you make. The meaning of each number is below)
Example used to describe the usage: Assuming we want the folder at the path “/TS Applications/Office” to really go to a folder called “/Managed Applications/By Group//Default/Office Suite” and the ACMFS file is stored in “/usr/sbin” then we would proceed with the command line: /usr/sbin/ACMFS –mountpoint “/TS Applications/Office” –prefix “/Managed Applications/By Group” –gid –suffix “Default/Office Suite”
1. 0 - This is the path that holds the ACMFS file, example: /usr/sbin
2. 1 - This is the folder in which the contents will be user specific. If the folder’s path contains a space in it then quote the whole path, example: “/TS Applications/Office”.
3. 2 - This is used in constructing the real location of the file’s contents. This signifies the 1st part of the real path before any user specific information is used, example: “/Managed Applications/By Group”.
4. 3 - This is the user specific information that should be used, valid choices are:
a. –none = Which means that no user specific information will be used
b. –username = Which means that the user’s UNIX name will be used, (often the user’s “shortname”)
c. –uid = Which means that the user’s UNIX user ID will be used, (UID)
d. –gid = Which means that the user’s UNIX primary group ID will be used, (GID)
e. –euid = Which means that the user’s Effective UNIX user ID will be used, (EUID - See “man 2 geteuid” and “man 8 sudo” for more information).
f. –sid = Which means that the user’s Mac Graphical User Interface session ID will be used, (SID - this changes for each logged in session and no user is guaranteed to have a specific number but will have the same number until he/she logs out).
5. 4 - This is used in constructing the real location of the file’s contents. This signifies the last part of the real path after any user specific information is used, example: “Default/Office Suite”.
Persistent Configuration
If you wish to make the configuration of ACMFS persistent through out the life of the server then you can append the command to the end of the “/etc/rc.common” file. This will cause it to execute before the Mac OS X Graphical User Interface starts and thus it’s effects will happen early on in the boot process of the server.
Disclaimers and Usage Agreement:
This driver (file) is offered with out any support or any implied support. It is offered with out any quality assurances or any implied quality assurances. You are NOT authorized to distribute, disassemble, reverse engineer or comment on the driver’s performance, merchantability or stability in a public manner with out written consent of Aqua Connect’s Support Division. Some support can be obtained through a professional service agreement that is different then your current maintenance agreement, the support is specific to ACMFS and be purchased through your Sales contact. The driver (file) is provided AS IS with the intent of it being useful to your environment, if you do not like it or wish to use then please delete the driver and refrain from commenting on pre-release software.
If you would like to download the driver, please contact your sales representative for the download link.
