1 | <sect2>
|
---|
2 | <title>Configuring nfs-utils</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 ncpfs.
|
---|
12 | The permissions on this file should be set to 600, for obvious security
|
---|
13 | 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 | <para><screen># 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</screen></para>
|
---|
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 ncpfs tools. If no password is supplied, the client utilities will
|
---|
33 | ask for a password when it is needed. If no password is needed, for
|
---|
34 | instance when using a guest account, a single '-' should be put in
|
---|
35 | 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 mountpoint 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 IPX protocol at boot, you can create the
|
---|
44 | following scripts. These scripts assume IPX will be set up on eth0
|
---|
45 | and the network frame type is 802.2. You should confirm that these
|
---|
46 | are the correct settings and adjust as necessary.</para>
|
---|
47 |
|
---|
48 | <para><screen>cat > /etc/sysconfig/network-devices/ifup-ipx0 << "EOF"
|
---|
49 | #!/bin/sh
|
---|
50 | # Begin /etc/sysconfig/network-devices/ifup-ipx0
|
---|
51 |
|
---|
52 | source /etc/sysconfig/rc || exit
|
---|
53 | source $rc_functions || exit
|
---|
54 |
|
---|
55 | echo "Setting up the IPX protocol on eth0..."
|
---|
56 | /bin/ipx_interface add eth0 802.2 &&
|
---|
57 | /bin/ipx_configure --auto_interface=on --auto_primary=on
|
---|
58 | evaluate_retval
|
---|
59 |
|
---|
60 | # End /etc/sysconfig/network-devices/ifup-ipx0
|
---|
61 | EOF
|
---|
62 | cat > /etc/sysconfig/network-devices/ifdown-ipx0 << "EOF"
|
---|
63 | #!/bin/sh
|
---|
64 | # Begin /etc/sysconfig/network-devices/ifdown-ipx0
|
---|
65 |
|
---|
66 | source /etc/sysconfig/rc || exit
|
---|
67 | source $rc_functions || exit
|
---|
68 |
|
---|
69 | echo "Stoping IPX on the eth0 interface..."
|
---|
70 | /bin/ipx_configure --auto_interface=off --auto_primary=off &&
|
---|
71 | /bin/ipx_interface del eth0 802.2
|
---|
72 | evaluate_retval
|
---|
73 |
|
---|
74 | # End /etc/sysconfig/network-devices/ifdown-ipx0
|
---|
75 | EOF
|
---|
76 | echo "ONBOOT=yes" > /etc/sysconfig/network-devices/ifconfig.ipx0
|
---|
77 | chmod 755 /etc/sysconfig/network-devices/ifup-ipx0
|
---|
78 | chmod 755 /etc/sysconfig/network-devices/ifdown-ipx0</screen></para>
|
---|
79 |
|
---|
80 | </sect3>
|
---|
81 |
|
---|
82 | </sect2>
|
---|
83 |
|
---|