Setup for Yellow
boot device: dc
processor number: 0
hostname: blue.uchicago.edu
file name: /products/prd/vxworks/v5_3b/target/config/mv2301/vxWorks
inet on ethernet(e): 128.135.152.90
host inet(h): 128.135.152.88
gateway inet(g): 128.135.152.1
user(u): vxworks
flags(f): 0x0
target name(tn): yellow
startup script(s): yellow_startup_ppc

Old Setup for Red, before using PPC computer
Connecting to Fermilab
boot device: ei
processor number: 0
hostname: b0dau30.fnal.gov
filename: /cdf/code-IRIX-6.5/products/vxworks_generic/v5_3b/target/config/mv167/vxWorks
inet on ethernet(e): 128.135.152.89
inet on backplane(b): 128.135.152.89
host inet(h): 131.225.206.191
gateway inet(g): 128.135.152.1
user(u): Your fermilab account name
ftp passwd(pw): Your fermilab account passwd
flags(f): 0x0
target name(tn): red.uchicago.edu startup script(s): red_startup

If you want to set up red to use blue.uchicago.edu, follow the settings for bilbo above. The only item that would change would be the startup script used and the inet on ethernet.

You can use either ftp or rsh to work with blue from bilbo. Ftp is slower, and caused some problems, so we changed to rsh. The mounting of disks is something that should go into the startup script (bilbo_startup_pedro, in this case) along with any other programs that will be loaded into memory. Here is the items from the startup script that pertain to using NFS:

hostAdd "blue", "128.135.152.88"
nfsMount "blue", "/home", "/home"
nfsMount "blue", "/products", "/products"

nfsAuthUnixPrompt
blue.uchicago.edu
502
100
0

This second section with nfsAuthUnixPrompt had to be added so that the programs running on bilbo could create and write to files on blue's NFS mounted disks. All this line really does is set the user to user vxworks' uid and gid, which it should have already been set at, but wasn't.