If you are accessing a Linux Subscriber server (including OES Linux) using a Windows client, access can be provided via a Samba share. Desktop Application objects hosted on that server will use the Samba share name in the UNC patch of the Application object.
To use Samba for share recognition:
On your Linux server, install Samba.
Refer to your Linux documenation for instructions on installing and configuring Samba.
Configure Samba by including a Samba share name (such as SYS) with the following path:
/usr/novell/share
where share is the Samba share name, such as sys.
Make sure Samba is running on the server when you send Desktop Application Distributions.
When a Desktop Application Distribution is configured with a golden application containing a path such as \\192.68.1.203\sys\firefox, the sys volume is interpreted as a share on the Linux server, allowing the Firefox application to be written to the /usr/novell/sys/firefox directory.
Repeat Step 1 through Step 3 for each Linux Subscriber and Distributor server where access to a Samba share name is required.
Include servers that have a location where:
The application files are to be written to (Linux Subscribers)
The application files are to be distributed from (Linux Distributors)