| 1 | <sect2>
|
|---|
| 2 | <title>Configuring <application>NCPFS</application></title>
|
|---|
| 3 |
|
|---|
| 4 | <sect3><title>Config files</title>
|
|---|
| 5 | <para><filename>~/.nwclient</filename></para>
|
|---|
| 6 | </sect3>
|
|---|
| 7 |
|
|---|
| 8 | <sect3><title>Configuration Information</title>
|
|---|
| 9 |
|
|---|
| 10 | <para>A config file <filename>~/.nwclient</filename> should be placed
|
|---|
| 11 | in the home directory of each user that intends to use <application>ncpfs
|
|---|
| 12 | </application>. The permissions on this file should be set to 600, for obvious
|
|---|
| 13 | security reasons. The configuration file should contain a single line
|
|---|
| 14 | per server that the user will use. Each line should contain
|
|---|
| 15 | the server name, the user name, and optionally the password. Below is a
|
|---|
| 16 | sample <filename>.nwclient</filename> file.</para>
|
|---|
| 17 |
|
|---|
| 18 | <screen><userinput># Begin example <filename>~/.nwclient</filename> config file
|
|---|
| 19 |
|
|---|
| 20 | Server1/User1 Password
|
|---|
| 21 | Server2/User1
|
|---|
| 22 | Server2/Guest1 -
|
|---|
| 23 |
|
|---|
| 24 | # End example .nwclient config file</userinput></screen>
|
|---|
| 25 |
|
|---|
| 26 | <para>The syntax for the <filename>.nwclient</filename> file is simple,
|
|---|
| 27 | <userinput>server_name/user_name password</userinput>. Be extremely
|
|---|
| 28 | careful when creating or editing this file as the client utilities are
|
|---|
| 29 | very picky about syntax. There should always be a space immediately
|
|---|
| 30 | after the username. If this space is substituted by a tab or multiple
|
|---|
| 31 | spaces, you will not get the expected results when attempting to use
|
|---|
| 32 | the <application>NCPFS</application> tools. If no password is supplied,
|
|---|
| 33 | the client utilities will ask for a password when it is needed. If no
|
|---|
| 34 | password is needed, for instance when using a guest account, a single '-'
|
|---|
| 35 | should be put in place of a password.</para>
|
|---|
| 36 |
|
|---|
| 37 | <para>It should be noted that the ncpmount is not intended to mount
|
|---|
| 38 | individual volumes because each mount point creates a separate client
|
|---|
| 39 | connection to the Novell server. Mounting each individual volume
|
|---|
| 40 | separately would be unwise, as mounting all volumes on a server
|
|---|
| 41 | under one mount point uses only one client connection.</para>
|
|---|
| 42 |
|
|---|
| 43 | <para>If you need to set up the <acronym>IPX</acronym> protocol at boot,
|
|---|
| 44 | you can install the
|
|---|
| 45 | <filename>/etc/sysconfig/network-devices/services/ipx</filename>
|
|---|
| 46 | network service script included with the
|
|---|
| 47 | <xref linkend="intro-important-bootscripts"/> package.</para>
|
|---|
| 48 |
|
|---|
| 49 | <screen><userinput><command>make install-service-ipx</command></userinput></screen>
|
|---|
| 50 |
|
|---|
| 51 | <para>Next install the configurations script,
|
|---|
| 52 | <filename>ifconfig.ipx0</filename>. The configuration assumes
|
|---|
| 53 | <acronym>IPX</acronym> will be set up on
|
|---|
| 54 | <emphasis role="strong">eth0</emphasis>
|
|---|
| 55 | and the network frame type is 802.2. You should confirm that these are
|
|---|
| 56 | the correct settings and adjust as necessary.</para>
|
|---|
| 57 |
|
|---|
| 58 | <para><emphasis>Note</emphasis>: This will overwrite any existing file.</para>
|
|---|
| 59 |
|
|---|
| 60 | <screen><userinput><command>cat > /etc/sysconfig/network-devices/ifconfig.ipx0 << "EOF"</command>
|
|---|
| 61 | ONBOOT=yes
|
|---|
| 62 | SERVICE=ipx
|
|---|
| 63 | IPXDEV=eth0
|
|---|
| 64 | FRAME=802.2
|
|---|
| 65 | <command>EOF</command></userinput></screen>
|
|---|
| 66 |
|
|---|
| 67 | </sect3>
|
|---|
| 68 |
|
|---|
| 69 | </sect2>
|
|---|
