| Date: Tue, 20 May 1997 16:27:53 -0400
From: David Jedlinsky USG <dcj>
To: thomson
Cc: dcj
Subject: Installing new Encodings file
Here's what you need to do to put an alternate Encodings file on the
RIS kit (MLS+ V4.0 or later, only). Items in <brackets> should be
replaced with the appropriate value on your system. Be sure to name
your <encodings> file with a name other than "Encodings",
"Encodings.MITRE", or "Encodings.commercial".
cd /var/adm/ris/<ris_dir>/product_001
cp <path_to_encodings>/<encodings> ./etc/policy/macilb
chown bin.bin ./etc/policy/macilb/<encodings>
chmod 755 ./etc/policy/macilb/<encodings>
# Note the first number from the following line:
sum ./etc/policy/macilb/<encodings>
# Note the size and date from the following line:
ls -l ./etc/policy/macilb/<encodings>
cp ./instctrl/OSFMLSBASE405.inv ./instctrl/OSFMLSBASE405.inv.orig
# Edit ./instctrl/OSFMLSBASE405.inv
Add a new line where it belongs alphabetically by filename. The
format of this line should be (fields are separated by <TAB>
characters only, no spaces, no returns!):
0 <size in bytes> <sum> 3 4 100755 <date MM/DD/YY> f ./etc/policy/macilb/<encodings> none OSFMLSBASE405
Save this, and install your client normally via ris. When you reach
the question about Encodings files, choose
"2) Edit default Encodings file"
then type the following to ed:
1,$d
r /etc/policy/macilb/<encodings>
w
q
Your new Encodings file will be installed.
-Dave Jedlinsky
MLS+ Release Engineering
dcj@zk3.dec.com
|
| > Can an FDDI link be used to due an RIS install?
Yes.
> Can the site specific Encodings file be added to the RIS server
Yes.
Note: The procedure in note 49.1 and 49.2 do not apply to V4. Dave says
you get "rcmd: socket: Network is down" because in V4 the Encodings
file loading doesn't take place until after the system is rebooted
(i.e., running under the real local root, not the mini-root).
|