SCO Unix 5.0.5
NIS configuration
a) Boot the SCO system to single user mode (also known as “system maintenance mode”)
b) Issue the ypinit command as shown below
#/etc/yp/ypinit -C
c) The text shown below will be displayed. Respond with the NIS domainname “domain.local”
The local host’s domain name hasn’t been set. Please set it.
Please enter the domain name or q to quit: domain.local
d) You will now be prompted for the mode in which ypbind is to run.
Select choice 4 to run with no special options
You must specify whether ypbind is to be run with secure
Option (-s), the ypset option (-ypset), allowing anyone to
Change your binding, or the ypsetme option (-ypsetme) which
Only allows requests with scotkr.domain.local’s IP address to change
scotkr.domain.local’s binding, or with no options.
Please see ypserv(NADM) for more information
1) ypbind –s
2) ypbind –ypset
3) ypbind –ypsetme
4) ypbind
Please entry your choice (1-4,q): 4
Backing up system passwd files …
scotkr.domain.local’s has been set up as a NIS client without any errors
#
e) You can now exit from system maintenance mode by pressing CTRL-D
7.11.2 Nameservice switch configuration
Create an append entry in /etc/passwd
We need to append an entry to the end of the password file to cause
NIS data to be processed as well as data from local files. An example
is shown below
Create an append entry in /etc/group
We also to append an entry to the end of the /etc/group file to
cause NIS data to be processed as well as data from the local group
file. An example is shown below
Modify the /etc/resolv.conf file
SCO Open server 5.0.5 is unusual as it specifies the hostname lookup
directory service search order in the file /etc/resolv.conf A line must
be added to specify the resolution order as shown in the example below.
[ for more information see the SCO resolv.conf man page ]
Set up “/export/home/users” directory NFS mount
Most users’ home directories will be on the main file server.
Carry out the configuration actions below to enable users to access
their home directories automatically
a) Create a mount point using the command
“mkdir – p /export/home/users”
b) Add an entry into the file /etc/default/filesys as shown below
bdev=mainfileserver.domain.local:/users \
mountdir=/export/home/users mount=yes fstype=NFS \
desc="common home directories" \
mntopts=rw
rcmount=yes \
c) Cause the file systems to be mounted by issuing the following
commands (note that they will be mounted automatically at boot time)
#
mount /export/home/users
d) If the directory /home exists create a softlink in this directory pointing to /export/home/users as shown below
#ln –s /export/home/users /home/users
e) You should now be able “cd” to the/home/users
directory. The individual user directories should be visible
Set up main file server “/export/home/hg1” NFS mount
Several key directories are mapped to the “U” drive on
the NAS server. To enable their use it is necessary to map the NAS
server “U” drive to the “/export/home/hg1” NFS
mounted filesystem as shown below
a) Create the /export/home/hg1 mountpoint using the command “mkdir /export/home/hg1”
b) Add an entry into the file /etc/default/filesys as shown below
bdev=mainfileserver.domain.local:/homegroup1 \
mountdir=/export/home/hg1 mount=yes fstype=NFS \
desc="group1 home area" \
mntopts=rw
rcmount=yes \
c) Issue the command “mount –a” which should mount
the new file system entry added in the previous step. You can ignore
messages pertaining to filesystems that are already mounted
g) Ensure that if the directory “/export/home/group1”
exists that its contents are either unneeded or saved. It is suggested
that it be renamed to saved_group1
h) Create a soft link for /export/home/group1 and /home/group1 pointing to /export/home/hg1/ using a command of the form shown below
#ln –s /home/hg1/sco5-05 /home/group1
#ln –s /home/hg1/sco5-05 /export/home/group1
i) You should now be able “cd” to the /home/group1 directory.
Set up “/export/home/source” directory NFS mount
The source directory is on the main file server. This must be mounted on the /export/home/source directory
a) Create the /export/home/source mountpoint using
the command “mkdir –p /export/home/source” Note that
any “local” contents of the directory
“/export/home/source” will not be visible once this file
system is mounted. Therefore check that
“/export/home/source” contains no data at this time. If it
does take steps to preserve or delete it
c) Add an entry into the file /etc/default/filesys as shown below
bdev=mainfileserver.domain.local:/source \
mountdir=/export/home/source mount=yes fstype=NFS \
desc="group1 home area" \
mntopts=rw
rcmount=yes \
d) Issue the command “mount –a”
which should mount the new file system entry added in the previous
step. You can ignore messages pertaining to filesystems that are
already mounted
e) Create a softlink to point /home/source at /export/home/source as shown below
#ln –s /export/home/source /home/source
Set up “/export/home/qatests” directory NFS mount
The qatests directory is on the main file server. This must be mounted on the /export/home/source directory
a) Create the /export/home/qatests mountpoint using
the command “mkdir –p /export/home/qatests” Note that
any “local” contents of the directory
“/export/home/qatests” will not be visible once this file
system is mounted. Therefore check that
“/export/home/qatests” contains no data at this time. If it
does take steps to preserve or delete it
b) Add an entry into the file /etc/default/filesys as shown below
bdev=mainfileserver.domain.local:/qatests \
mountdir=/export/home/qatests mount=yes fstype=NFS \
desc="group1 home area" \
mntopts=rw
rcmount=yes \
c) Issue the command “mount –a”
which should mount the new file system entry added in the previous
step. You can ignore messages pertaining to filesystems that are
already mounted
d) Create a softlink to point /home/qatests at /export/home/qatests as shown below
#ln –s /export/home/qatests /home/qatests
Set up “/export/home/hg1output” directory NFS mount
The qaoutput directory is on the main file server. This must be mounted on the /export/home/source directory
a) Create the /export/home/hg1output mountpoint using the command “mkdir –p /export/home/hg1output”
b) Add an entry into the file /etc/default/filesys as shown below
bdev=mainfileserver.domain.local:/qaoutput \
mountdir=/export/home/hg1output mount=yes fstype=NFS \
desc="platform specific areas for QA tests" \
mntopts=rw
rcmount=yes \
c) Issue the command “mount –a”
which should mount the new file system entry added in the previous
step. You can ignore messages pertaining to filesystems that are
already mounted
d) Create a soft link for /export/home/group1/output and /home/group1/output pointing to /export/home/hg1output/
using a command of the form shown below. Note to obtain the correct
permissions to create this link it will be necessary to
“su” to the build user as shown below
#su build
$ln –s /export/home/hg1output/sco5-05 /export/home/group1/output
Set up “/export/home/unixcfg” directory NFS mount
The unixcfg directory area is on the IBM NAS 300 server. This must be mounted on the /export/home/unixcfg directory
m) Create the /export/home/unixcfg mountpoint using the command “mkdir –p /export/home/unixcfg”
n) Add an entry into the file /etc/fstab as shown below
mainfileserver.domain.local:/unixcfg /export/home/unixcfg nfs rw,suid,soft 0 0
o) Issue the command “mount
–a” which should mount the new file system entry added in
the previous step. You can ignore messages pertaining to filesystems
that are already mounted
Next (Digital Unix)
Back to menu
