Installing and Configuring an ULTRIX V3.0 DMS Server on a SIMH MicroVAX 3900

From Computer History Wiki
Revision as of 09:30, 8 July 2022 by Vaxorcist (talk | contribs) (New page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Install ULTRIX V3.0 on a SIMH MicroVAX 3900

You find the ULTRIX V3.0 installation media here.

microvax3900.ini

Use the following settings for the SIMH MicroVAX 3900:

; microvax3900.ini

SET QUIET

SET CPU MODEL=MicroVAX
SET CPU 64M
SET CPU CONHALT
SET CPU AUTOBOOT

; SET CONSOLE TO 7 BIT
SET TTI 7B 
SET TTO 7B 

ATT NVR NVR.BIN

SET CONSOLE LOG=ULT030_001.LOG

SET RQ KDA50
SET RQ0 ENA
SET RQ0 RA82
ATT RQ0 -F VHD ULT030_VHD.R82

SET RQ1 RA82
ATT RQ1 -F VHD ULT030_DMS_VHD.R82
SET RQ2 DIS
SET RQ3 DIS

SET DZ LINES=4
;ATT DZ 6666

SET TQ0 ENA
ATT TQ0 AQ-HN73D-BE_ULT030-UWS020SUP.tk5

SET TQ1 DIS
SET TQ2 DIS
SET TQ3 DIS

SET LPT DIS
SET RL  DIS
SET TS  DIS

SET XQ ENA
SET XQ TYPE=DELQA
SET XQ MAC=08:00:2B:5A:71:E1
;08-00-2B-5A-71-E1
ATT XQ tap:tap0

BOOT

Boot SIMH MicroVAX 3900

KA655-A V5.3, VMB 2.7
 1) Dansk
 2) Deutsch (Deutschland/Vsterreich)
 3) Deutsch (Schweiz)
 4) English (United Kingdom)
 5) English (United States/Canada)
 6) Espaqol
 7) Frangais (Canada)
 8) Frangais (France/Belgique)
 9) Frangais (Suisse)
10) Italiano
11) Nederlands
12) Norsk
13) Portugujs
14) Suomi
15) Svenska
 (1..15): 5
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>

Boot Standalone ULTRIX V3.0 Environment from Tape and Start Basic Installation

>>>BOOT MUA0
(BOOT/R5:0 MUA0
  2..
-MUA0
  1..0..
Ultrixload (using VMB version 13)
Sizes:
text = 623856
data = 958384
bss  = 664196
Rewinding tape ...
Starting at 0x4beb
Ultrix-32 V3.0 (Rev 64) System #3: Tue Nov 15 14:20:57 EST 1988
real mem  = 67043328
avail mem = 62282752
Buffer configuration adjusted to run with small system page table
using 132 buffers containing 1081344 bytes of memory
KA655 processor with an FPU
       CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
NO LOOPBACK
WARNING: clock lost 132 days -- CHECK AND RESET THE DATE!
*** STANDALONE ULTRIX ENVIRONMENT *** 
If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.
If you require additional installation choices, select the ADVANCED
Installation option.
Select one of the following options: 
        1) BASIC Installation
        2) ADVANCED Installation
        3) System management 
Enter your choice: 1
ra0 at uq0 slave 0 (RA82)
ra1 at uq0 slave 1 (RA82)
tms0 at uq16 slave 0 (TK50)
*** SOFTWARE DISTRIBUTION DEVICE SELECTION *** 
The installation booklet for your processor explains the following table 
of software distribution devices and which installation media you should 
load on it:
Selection   Device     Device       Controller   Controller
            Name       Number       Name         Number
-----------------------------------------------------------
    1       TK50          0         TK50          16
-----------------------------------------------------------
Enter your choice: 1
REMOVE THE TAPE LABELED 'STANDALONE ULTRIX TK50 #1'.
You selected TK50, device number 0.  After you load the media,
make sure the device is on line and write protected.  The media is labeled 
SUPPORTED SOFTWARE.
Press the RETURN key when you are ready to continue. 
*** SYSTEM DISK SELECTION *** 
The installation booklet for your processor explains the following table 
of system disk drives.  Select one of the devices below to contain the
root file system: 
Selection   Device     Device       Controller   Controller
            Name       Number       Name         Number
-----------------------------------------------------------
    1       RA82          0         KDA50          0
    2       RA82          1         KDA50          0
-----------------------------------------------------------
Enter your choice: 1
You selected RA82, device number 0. Make sure this disk drive 
is on line and write-enabled (if applicable to your disk drive).
Press the RETURN key when you are ready to continue. [RETURN]
The installation procedure now allocates the root file system on
partition 'a' of the system disk, ra0 RA82. 
Making the root file system on ra0 RA82.
The installation procedure is now restoring the root file system to
partition 'a' of the system disk, ra0 RA82.
The installation procedure now checks the root file system on partition 'a'
of the system disk, ra0  RA82.
** /dev/rra0a
** Last Mounted on /mnt
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
165 files, 2730 used, 4693 free (21 frags, 584 blocks)
 *** BOOTSTRAP COMMAND SEQUENCE ***
Enter the following boot sequence at the console mode prompt
after the installation software halts the processor: 
        >>> b dua0
syncing disks... done
?06 HLT INST
        PC = 8004544D
Simulation stopped, PC: 800052C3 (BEQL 800052CD)
sim> exit
Goodbye

Boot ULTRIX V3.0 Miniroot from Disk and Build Kernel

KA655-A V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>b dua0
(BOOT/R5:0 DUA0
  2..
-DUA0
  1..0..
Ultrixboot (using VMB version 13)
Loading (a)vmunix ...
Sizes:
text = 760060
data = 197976
bss  = 827824
Starting at 0x4beb
Ultrix-32 V3.0 (Rev 64) System #3: Tue Nov 15 14:19:17 EST 1988
real mem  = 67043328
avail mem = 62029824
Buffer configuration adjusted to run with small system page table
using 217 buffers containing 1777664 bytes of memory
KA655 processor with an FPU
       CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
ra1 at uq0 slave 1 (RA82)
ra0 at uq0 slave 0 (RA82)
tms0 at uq16 slave 0 (TK50)
 *** SYSTEM NAME SPECIFICATION *** 
Select the name of your system using alphanumeric characters. 
The first character must be a letter.   For example, tinker.
Enter your system name: piggy
You selected piggy as the name of your system.  Is this
correct? (y/n) [y]: [RETURN]
*** DATE AND TIME SPECIFICATION *** 
The current date and time should be specified using the following
format:
        yymmddhhmm
Use two digits for year (yy), month (mm), day (dd), hour (hh), and
minute (mm).  Enter the time in 24-hour format.  For example, 11:30
p.m. on May 14, 1988 would be entered as:
        8805142330
Enter the date and time: 8805142330
*** TIME ZONE SELECTION ***
        
Select the time zone for your area, using the options listed in the
table below.  You can also enter the number of hours (-12 to 12) in
time west of Greenwich.
  Selection     Time Zone 
---------------------------------
      e         Eastern
      c         Central
      m         Mountain
      p         Pacific
      g         Greenwich
---------------------------------
Enter your choice: c
Does your area alternate between Daylight Savings and Standard
time? (y/n) [y]: y
Select your geographic area for Daylight Savings Time, using the
options in the table below.
  Selection     Geographic Area 
--------------------------------
      u         USA
      a         Australia
      e         Eastern Europe
      c         Central Europe
      w         Western Europe
--------------------------------
Enter your choice [u]: w
The current date and time is Sat May 14 23:30:00 CDT 1988
*** SPECIFY THE SUPERUSER PASSWORD *** 
The installation booklet for your processor instructs
you on how to enter the superuser password.  
New password: ult030 (not echoed)
Retype new password: ult030 (not echoed)
*** SPECIFY THE FIELD SERVICE PASSWORD *** 
The installation booklet for your processor instructs
you on how to enter the field service password.  
New password: ult030 (not echoed)
Retype new password: ult030 (not echoed)
Making the new file system for /usr on /dev/rra0d RA82 
Making the new file system for /usr/users 
on /dev/rra0h RA82 
Installing mandatory software subsets.
Please make sure your installation tape is mounted and on-line.
Are you ready? (y/n): y
Positioning tape...done.
Copying Base System (ULTBASE030) from tape
Verifying Base System (ULTBASE030)
Copying Kernel Configuration Files (ULTBIN030) from tape
Verifying Kernel Configuration Files (ULTBIN030)
Copying TCP/IP Networking Utilities (ULTINET030) from tape
Verifying TCP/IP Networking Utilities (ULTINET030)
Copying System Exerciser Package (ULTEXER030) from tape
Verifying System Exerciser Package (ULTEXER030)
Copying Network File System Utilities (ULTNFS030) from tape
Verifying Network File System Utilities (ULTNFS030)
Copying Extended (Berkeley) Mailer (ULTUMAIL030) from tape
Copying X11/DECwindows User Environment (UWSX11020) from tape
Verifying Extended (Berkeley) Mailer (ULTUMAIL030)
Verifying X11/DECwindows User Environment (UWSX11020)
Copying X11/DECwindows 75dpi Fonts (UWSFONT020) from tape
Verifying X11/DECwindows 75dpi Fonts (UWSFONT020)
The installation software has successfully installed the software
subsets. You can now remove the tape containing the software subsets
from the device.
*** SYSTEM CONFIGURATION PROCEDURE ***
The installation software found these devices in the floating 
address space:
        dz0             on uba0         at 0160100
Configuration file complete.
*** PERFORMING SYSTEM CONFIGURATION *** 
    working ..... Sat May 14 23:31:59 CDT 1988
*** DEVICE SPECIAL FILE CREATION *** 
    working ..... Sat May 14 23:32:24 CDT 1988
Enter the following boot sequence at the console mode prompt
after the installation software halts the processor: 
        >>> b dua0
*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***
The following files were created during the installation procedure:
/vmunix                         - customized kernel
/genvmunix                      - generic kernel
/usr/adm/install.log            - installation log file
/usr/adm/install.FS.log         - file systems log file
/usr/adm/install.DEV.log        - special device log file
syncing disks... done
HALT instruction, PC: 8004EC85 (BRB 8004EC84)

Boot ULTRIX V3.0 and Install Software Subsets

KA655-A V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>set boot dua0
>>>boot
(BOOT/R5:0 DUA0
  2..
-DUA0
  1..0..
Ultrixboot (using VMB version 13)
Loading (a)vmunix ...
Sizes:
text = 496832
data = 91740
bss  = 578832
Starting at 0x29eb
Ultrix-32 V3.0 (Rev 64) System #1: Sat May 14 23:32:19 CDT 1988
real mem  = 67043328
avail mem = 57248768
using 3273 buffers containing 6704128 bytes of memory
KA655 processor with an FPU
       CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
dz0 at uba0 csr 160100 vec 300, ipl 17
ra1 at uq0 slave 1 (RA82)
ra0 at uq0 slave 0 (RA82)
tms0 at uq16 slave 0 (TK50)
WARNING: clock gained 52 days -- CHECK AND RESET THE DATE!
Automatic reboot in progress...
Wed Jul  6 04:21:06 CDT 1988
/dev/ra0a: 408 files, 4095 used, 3328 free (88 frags, 405 blocks)
/dev/rra0d: umounted cleanly
/dev/rra0h: umounted cleanly
Wed Jul  6 04:21:06 CDT 1988
System supports 2 users.
check quotas: done.
savecore: checking for dump...dump does not exist
local daemons: syslog sendmail.
Removing remnant Opser files
preserving editor files
clearing /tmp
standard daemons: update cron accounting network rwhod printer.
start errlog daemon - elcsd
Wed Jul  6 04:21:07 CDT 1988
Ultrix-32 V3.0 (Rev 64) (piggy)
login: root
Password: ult030 (not echoed)
Ultrix-32 V3.0 (Rev 64) System #1: Sat May 14 23:32:19 CDT 1988
                Digital Equipment Corporation
                Nashua, New Hampshire
*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***
The following files were created during the installation procedure:
/vmunix                         - customized kernel
/genvmunix                      - generic kernel
/usr/adm/install.log            - installation log file
/usr/adm/install.FS.log         - file systems log file
/usr/adm/install.DEV.log        - special device log file
# setld -l /dev/nrmt0h
Please make sure your installation tape is mounted and on-line.
Are you ready? (y/n): y
Positioning tape...done.
*** Enter Subset Selections ***
The subsets listed below are optional:
 1) X11/DECwindows 100dpi Fonts          2) Optional DECwindows Applications    
 3) X10 to X11 Compatibility Tools       4) The RAND Mail Handler               
 5) Document Preparation Software        6) Adobe Font Metric Files             
 7) Software Development Utilities       8) Internationalization Tools          
 9) Source Code Control System          10) Worksystem Development Software     
11) Pascal Development Package          12) VAX C/ULTRIX                        
13) On Line Manual Pages                14) UWS Manual Pages                    
15) Accounting Software                 16) Communications Utilities            
17) Bisynchronous Communications        18) Maintenance Operations Protocol     
19) Unix-to-Unix Copy Facility          
20) All of the Above
21) None of the Above
Enter your choice(s): 5 13 18 16
You are installing the following subsets:
   Document Preparation Software           On Line Manual Pages                 
   Communications Utilities                Maintenance Operations Protocol      
Is this correct? (y/n): y
Copying Document Preparation Software (ULTDCMT030) from tape
Verifying Document Preparation Software (ULTDCMT030)
Copying On Line Manual Pages (ULTMAN030) from tape
Verifying On Line Manual Pages (ULTMAN030)
Copying Communications Utilities (ULTCOMM030) from tape
Verifying Communications Utilities (ULTCOMM030)
Copying Maintenance Operations Protocol (ULTMOP030) from tape
Verifying Maintenance Operations Protocol (ULTMOP030)
# setld -i
Subset          Status          Description
======          ======          ===========
ULTACCT030                      Accounting Software
ULTBIN030       installed       Kernel Configuration Files
ULTDCMT030      installed       Document Preparation Software
ULTEXER030      installed       System Exerciser Package
ULTINET030      installed       TCP/IP Networking Utilities
ULTBSC030                       Bisynchronous Communications
ULTBASE030      installed       Base System
ULTAFM030                       Adobe Font Metric Files
ULTCOMM030      installed       Communications Utilities
ULTINTL030                      Internationalization Tools
ULTMAN030       installed       On Line Manual Pages
ULTMH030                        The RAND Mail Handler
ULTMOP030       installed       Maintenance Operations Protocol
ULTNFS030       installed       Network File System Utilities
ULTPASCAL030                    Pascal Development Package
ULTPGMR030                      Software Development Utilities
ULTSCCS030                      Source Code Control System
ULTUMAIL030     installed       Extended (Berkeley) Mailer
ULTUUCP030                      Unix-to-Unix Copy Facility
ULTVAXC030                      VAX C/ULTRIX
UWSDECW020                      Optional DECwindows Applications
UWSFONT020      installed       X11/DECwindows 75dpi Fonts
UWSFONT15020                    X11/DECwindows 100dpi Fonts
UWSMAN020                       UWS Manual Pages
UWSX11020       installed       X11/DECwindows User Environment
UWSXCOMP020                     X10 to X11 Compatibility Tools
UWSXDEV020                      Worksystem Development Software
#

Install 16 User License Key

# [STRG + e]
Simulation stopped, PC: 800030DC (TSTL 800F4CBC)
sim> att tq0 AQ-JU88A-BE_ULTRIX-32_2.0_16usr_87.tap
sim> c
# /etc/install_upgrade /dev/nrmt0h
Is the correct capacity upgrade kit loaded on /dev/nrmt0h at piggy <y/n>? y
Capacity Upgrade installation done.
# shutdown -h now
Shutdown at 04:26 (in 0 minutes) [pid 576]
System shutdown time has arrived
syncing disks... done
HALT instruction, PC: 8005DD05 (BRB 8005DD04)
sim> boot
KA655-A V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>boot
(BOOT/R5:0 DUA0
  2..
-DUA0
  1..0..
Ultrixboot (using VMB version 13)
Loading (a)vmunix ...
Sizes:
text = 496832
data = 91740
bss  = 578832
Starting at 0x29eb
Ultrix-32 V3.0 (Rev 64) System #1: Sat May 14 23:32:19 CDT 1988
real mem  = 67043328
avail mem = 57248768
using 3273 buffers containing 6704128 bytes of memory
KA655 processor with an FPU
       CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
dz0 at uba0 csr 160100 vec 300, ipl 17
ra1 at uq0 slave 1 (RA82)
ra0 at uq0 slave 0 (RA82)
tms0 at uq16 slave 0 (TK50)
Automatic reboot in progress...
Wed Jul  6 04:31:30 CDT 1988
/dev/ra0a: 417 files, 4183 used, 3240 free (80 frags, 395 blocks)
/dev/rra0d: umounted cleanly
/dev/rra0h: umounted cleanly
Wed Jul  6 04:31:30 CDT 1988
System supports 16 users.
check quotas: done.
savecore: checking for dump...dump does not exist
local daemons: syslog sendmail.
Removing remnant Opser files
preserving editor files
clearing /tmp
standard daemons: update cron accounting network rwhod printer.
start errlog daemon - elcsd
Wed Jul  6 04:31:31 CDT 1988
Ultrix-32 V3.0 (Rev 64) (piggy)
login: root
Password: ult030 (not echoed)
Last login: Wed Jul  6 04:21:31 on console
Ultrix-32 V3.0 (Rev 64) System #1: Sat May 14 23:32:19 CDT 1988
                Digital Equipment Corporation
                Nashua, New Hampshire
*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***
The following files were created during the installation procedure:
/vmunix                         - customized kernel
/genvmunix                      - generic kernel
/usr/adm/install.log            - installation log file
/usr/adm/install.FS.log         - file systems log file
/usr/adm/install.DEV.log        - special device log file
#

Configure TCP/IP Networking

# netsetup install
You will be asked a series of questions about your system.
Default answers are shown in square brackets ([]).
To use a default answer, press the RETURN key.
Your system's name is "piggy".  Is this correct [yes]? [RETURN]
Your system can have one or more abbreviation names.  An abbreviation
name reduces the number of keystrokes required for network commands. A
common abbreviation name is the first letter of the system name.
Press the RETURN key if you do not want any abbreviation names for
piggy.  Otherwise, enter one or more abbreviation names, separated by
blank spaces: [RETURN]
You do not want any abbreviation names for piggy.  Is this correct [yes]? [RETURN]
For a Class A network, the network number is in the range 1 through
126.  For a Class B network, the network number consists of two fields
separated by periods.  The first field is in the range 128 through 191,
and the second field is in the range 1 through 254.  For a Class C
network, the network number consists of three fields separated by
periods.  The first field is in the range 192 through 223, the second
field is in the range 0 through 255, and the third field is in the
range 1 through 254:
   Class A:  1       through 126
   Class B:  128.1   through 191.254
   Class C:  192.0.1 through 223.255.254
Enter the network number for piggy: 10
The network number is 10.  Is this correct [yes]? [RETURN]
Subnetworks allow the systems on a given local area network to be on
different network wires.  If your existing local area network is using
subnet routing, you need to know how many bits of your host number
are being reserved for specifying the subnetwork address.
Are you setting up piggy on a network that uses subnet routing [no]? [RETURN] 
You will NOT set up piggy on a network that uses subnet
routing.  Is this correct [yes]? [RETURN]
You are setting up piggy on a Class A network.
Valid Class A host numbers consist of three fields separated by
periods.  The first two fields are in the range 0 through 255, and
the third field is in the range 1 through 254:
   0.0.1 through 255.255.254
An alternate representation for the three bytes of information specifying
the host number is one field in the range 1 through 16777214:
   1 through 16777214
Enter the host number for piggy: 33
The Host number is 0.0.33.  Is this correct [yes]? [RETURN]
***** UPDATING /etc/hosts WITH piggy AND localhost *****
An Internet Protocol (IP) broadcast address is an address in which the
bits of the host number are either all ones or all zeros.  You need to
know what the other hosts on your existing local area network are using as
their broadcast address.  If you are setting up your own network, use
the default..
WARNING! You must use the same broadcast address as all of the other
hosts on your network.  This is very important!
If you use all ones your IP broadcast address is: 10.255.255.255
if you use all zeros your IP broadcast address is: 10.0.0.0
Enter a "1" if you use all ones, or "0" if you use all zeros [1]: [RETURN]
You are using all ones for your broadcast address.
Is this correct [yes]? [RETURN]
Please specify the device name and unit number of your network
interface.  This information is entered in the /etc/rc.local file so
that the correct device is initialized when you bring the system to
multiuser mode.  The device name consists of the network device
as found in your system config file.  The following are some common
network device names:
        Device Name     Description
        -----------     -----------
          de0           DEUNA, DELUA - UNIBUS
          ni0           DEBNT, DEBNA - BI bus
          qe0           DEQNA, DELQA - Q-Bus
          scs0          SCS network interface to CI
          se0           DESVA, Busless LANCE network interface
What is the device name of your Network Interface [qe0]? [RETURN]
Your Network interface is "qe0".  Is this correct [yes]? [RETURN]
***** UPDATING /etc/rc.local WITH network configuration information *****
Network numbers have names so you can refer to them by name rather than
by number.  The network name is entered in the /etc/networks file.  If
you are adding piggy to an existing network, you should use the same
names as the other hosts on the network use for the various network
numbers.  If you are not adding piggy to an existing network, you can
name the network number whatever you want.  You can assign alias names
for the network number.
What is the name of network 10 [ethernet]? [RETURN]
The network name for piggy is "ethernet".  Is this correct [yes]? [RETURN]
Enter any aliases for ethernet: [RETURN]
You do not have any aliases for ethernet.  Is this correct [yes]? [RETURN]
***** UPDATING /etc/networks WITH ethernet *****
***** ADD/CHANGE SYSTEMS IN /etc/hosts *****
Enter the host name, abbreviations, network number, and host number for
each host on the network.  Enter this information on separate lines
when prompted.  This information is stored in the /etc/hosts file.  When
finished, press the RETURN key at the hostname prompt.
Enter the name of the host you want to add to /etc/hosts: [RETURN]
Are you finished adding hosts [yes]? [RETURN]
Enter the names of trusted hosts.  Trusted hosts are systems you
consider to be secure.  Be careful if you select trusted hosts.  Any
users on a trusted host can log in to piggy without password
verification if they have a valid account on your system.  The names of
the trusted hosts are stored in the /etc/hosts.equiv file.  When you
have finished entering the names of trusted hosts, press the RETURN key.
Enter the name of a trusted host: [RETURN]
Have you finished entering the names of trusted hosts [yes]? [RETURN]
***** SETTING UP /usr/hosts DIRECTORY *****
***** NETWORK SETUP COMPLETE *****
# shutdown now
Shutdown at 04:33 (in 0 minutes) [pid 105]
System shutdown time has arrived
erase ^?, kill ^U, intr ^C
# [STRG + d]
Wed Jul  6 04:33:51 CDT 1988
System supports 16 users.
check quotas: done.
savecore: checking for dump...dump does not exist
local daemons: syslog sendmail.
Removing remnant Opser files
preserving editor files
clearing /tmp
standard daemons: update cron accounting network rwhod printer.
start errlog daemon - elcsd
Wed Jul  6 04:33:52 CDT 1988
Ultrix-32 V3.0 (Rev 64) (piggy)
login: root
Password: ult030 (not echoed)
Last login: Wed Jul  6 04:31:41 on console
Ultrix-32 V3.0 (Rev 64) System #1: Sat May 14 23:32:19 CDT 1988
                Digital Equipment Corporation
                Nashua, New Hampshire
*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***
The following files were created during the installation procedure:
/vmunix                         - customized kernel
/genvmunix                      - generic kernel
/usr/adm/install.log            - installation log file
/usr/adm/install.FS.log         - file systems log file
/usr/adm/install.DEV.log        - special device log file
# ifconfig qe0
qe0: 10.0.0.33 netmask ff000000 flags=0x443<DYNPROTO,RUNNING,BROADCAST,UP>
broadcast: 10.255.255.255

Add User guest

# adduser
Enter login name for new user (initials, first or last name): guest
Enter full name for new user: guest
What login group should this user go into [ users ] ? [RETURN]
Working ...
Enter another group that 'guest' should be a member of
(<RETURN> only if none): [RETURN]
Enter parent directory for guest [/usr/users]: [RETURN]
Adding new user ...
The new user account initially has no password.

Test Networking using Telnet

# telnet piggy
Trying...
Connected to piggy.
Escape character is '^]'.
Ultrix-32 V3.0 (Rev 64) (piggy)
login: guest
Ultrix-32 V3.0 (Rev 64) System #1: Sat May 14 23:32:19 CDT 1988
                Digital Equipment Corporation
                Nashua, New Hampshire
*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***
The following files were created during the installation procedure:
/vmunix                         - customized kernel
/genvmunix                      - generic kernel
/usr/adm/install.log            - installation log file
/usr/adm/install.FS.log         - file systems log file
/usr/adm/install.DEV.log        - special device log file
Wed Jul  6 04:35:01 CDT 1988
piggy> w
  4:35am  up 4 mins,  2 users,  load average: 0.13, 0.04, 0.02
User     tty       login@  idle   JCPU   PCPU  what
root     console   4:34am                      telnet piggy 
guest    ttyp0     4:35am                      w 
piggy> ps -axl
      F UID   PID  PPID CP PRI NI ADDR  SZ  RSS WCHAN STAT TT  TIME COMMAND
2000003   0     0     0  0 -25  0  8eb   0    0 fa1a6 D    ?   0:00 swapper
b000001   0     1     0  0   5  0 4c3e 248  225 37e08 I    ?   0:00 init
3000003   0     2     0  0 -24  0 4c1e4096    0 37ec8 D    ?   0:00 pagedaemon
3000001   1   150     1  0   1  0 56a8  59   27 5ce24 I    ?   0:00 /etc/syslog
3000201   0   168     1  0  15  0 5d66   4    2 fe400 I    ?   0:00 /etc/update
3000201   0   171     1  0  15  0 5da2  26    6 fe400 S    ?   0:00 /etc/cron
3000001   0   177     1  0   1  0 5e0c  62   30 fa1c8 S    ?   0:00 /etc/inetd
3000001   0   181     1  0   1  0 5ec0 171   98 8c7a4 I    ?   0:00 /etc/rwhod
3008001   0   189     1  0   1  0 5fb8  56   31 fa1c8 I    ?   0:00 /usr/lib/lp
3000001   0   195     1  0   1  0 6098 110   43 fa1c8 I    ?   0:00 /etc/elcsd
b008201   0   196     1  0  15  0 5446  39   28 fe400 S    co  0:00 -csh (csh)
3008001   0   197     1  0   1  0 6116 264  169 8cd64 I    ?   0:00 /usr/lib/se
b000001   0   268   196  0   1  0 6416  54   34 fa1c8 S    co  0:00 telnet pigg
b000001   0   269   177  0   1  0 671c  45   28       R    p0  0:00 telnetd
b808001 268   270   269  0  25  0 67b0  54   33       R    p0  0:00 -csh (csh)
b000001 268   277   270  2  26  0 69ba 248  139       R    p0  0:00 ps -axl
piggy> logout
Connection closed by foreign host.
#

Configure Terminal Lines

# ed /etc/ttys
1319
1,$n
1      #                "@(#)ttys      4.1     (ULTRIX)        11/23/87"
5      # name  getty           type            status          comments
7      console "/etc/getty e"   dw3            on secure       # console terminal
8      tty00   "/etc/getty std.9600" vt100     off nomodem     # direct connect tty
9      tty01   "/etc/getty std.9600" vt100     off nomodem     # direct connect tty
10     tty02   "/etc/getty std.9600" vt100     off nomodem     # direct connect tty
11     tty03   "/etc/getty std.9600" vt100     off nomodem     # direct connect tty
12     tty04   "/etc/getty std.9600" vt100     off nomodem     # direct connect tty
13     tty05   "/etc/getty std.9600" vt100     off nomodem     # direct connect tty
14     tty06   "/etc/getty std.9600" vt100     off nomodem     # direct connect tty
15     tty07   "/etc/getty std.9600" vt100     off nomodem     # direct connect tty
16     ttyp0   none            network
17     ttyp1   none            network
18     ttyp2   none            network
19     ttyp3   none            network
20     ttyp4   none            network
21     ttyp5   none            network
22     ttyp6   none            network
23     ttyp7   none            network
24     ttyp8   none            network
25     ttyp9   none            network
26     ttypa   none            network
27     ttypb   none            network
28     ttypc   none            network
29     ttypd   none            network
30     ttype   none            network
31     ttypf   none            network
32     ttyq0   none            network
33     ttyq1   none            network
34     ttyq2   none            network
35     ttyq3   none            network
36     ttyq4   none            network
37     ttyq5   none            network
38     ttyq6   none            network
39     ttyq7   none            network
40     ttyq8   none            network
41     ttyq9   none            network
42     ttyqa   none            network
43     ttyqb   none            network
44     ttyqc   none            network
45     ttyqd   none            network
46     ttyqe   none            network
47     ttyqf   none            network
1,$s/off nomodem/on secure
tty07  "/etc/getty std.9600" vt100     on secure       # direct connect tty
1,$n
1      #                "@(#)ttys      4.1     (ULTRIX)        11/23/87"
5      # name  getty           type            status          comments
7      console "/etc/getty e"   dw3            on secure       # console terminal
8      tty00   "/etc/getty std.9600" vt100     on secure       # direct connect tty
9      tty01   "/etc/getty std.9600" vt100     on secure       # direct connect tty
10     tty02   "/etc/getty std.9600" vt100     on secure       # direct connect tty
11     tty03   "/etc/getty std.9600" vt100     on secure       # direct connect tty
12     tty04   "/etc/getty std.9600" vt100     on secure       # direct connect tty
13     tty05   "/etc/getty std.9600" vt100     on secure       # direct connect tty
14     tty06   "/etc/getty std.9600" vt100     on secure       # direct connect tty
15     tty07   "/etc/getty std.9600" vt100     on secure       # direct connect tty
16     ttyp0   none            network
17     ttyp1   none            network
18     ttyp2   none            network
19     ttyp3   none            network
20     ttyp4   none            network
21     ttyp5   none            network
22     ttyp6   none            network
23     ttyp7   none            network
24     ttyp8   none            network
25     ttyp9   none            network
26     ttypa   none            network
27     ttypb   none            network
28     ttypc   none            network
29     ttypd   none            network
30     ttype   none            network
31     ttypf   none            network
32     ttyq0   none            network
33     ttyq1   none            network
34     ttyq2   none            network
35     ttyq3   none            network
36     ttyq4   none            network
37     ttyq5   none            network
38     ttyq6   none            network
39     ttyq7   none            network
40     ttyq8   none            network
41     ttyq9   none            network
42     ttyqa   none            network
43     ttyqb   none            network
44     ttyqc   none            network
45     ttyqd   none            network
46     ttyqe   none            network
47     ttyqf   none            network
w
1303
q
# kill -HUP 1
# ps -axl
      F UID   PID  PPID CP PRI NI ADDR  SZ  RSS WCHAN STAT TT  TIME COMMAND
2000003   0     0     0  0 -25  0  8eb   0    0 fa1a6 D    ?   0:00 swapper
b000001   0     1     0  0   5  0 4c3e 248  225 37e08 S    ?   0:00 init
3000003   0     2     0  0 -24  0 4c1e4096    0 37ec8 D    ?   0:00 pagedaemon
3000001   1   150     1  0   1  0 56a8  59   27 5ce24 I    ?   0:00 /etc/syslog
3000201   0   168     1  0  15  0 5d66   4    2 fe400 I    ?   0:00 /etc/update
3000201   0   171     1  0  15  0 5da2  26    6 fe400 I    ?   0:00 /etc/cron
3000001   0   177     1  0   1  0 5e0c  62   30 fa1c8 I    ?   0:00 /etc/inetd
3000001   0   181     1  0   1  0 5ec0 171   98 8c7a4 I    ?   0:00 /etc/rwhod
3008001   0   189     1  0   1  0 5fb8  56   31 fa1c8 I    ?   0:00 /usr/lib/lp
3000001   0   195     1  0   1  0 6098 110   43 fa1c8 I    ?   0:00 /etc/elcsd
b008001   0   196     1  0  25  0 5446  39   28       R    co  0:00 -csh (csh)
3008001   0   197     1  0   1  0 6116 264  169 8cd64 I    ?   0:00 /usr/lib/se
b000001   0   287   196  2 -25  0 6fde 250  142       R    co  0:00 ps -axl
b000001   0   279     1  0   3  0 6712  47   28 1adac S    00  0:00 - std.9600 
b000001   0   280     1  0   3  0 69a4  47   28 1ae44 S    01  0:00 - std.9600 
b000001   0   281     1  0   3  0 6bcc  47   28 1aedc S    02  0:00 - std.9600 
b000001   0   282     1  0   3  0 6da2  47   28 1af74 S    03  0:00 - std.9600 
b000001   0   283     1  0   3  0 6f78  47   26 f6a14 S    04  0:00 - std.9600 
b000001   0   284     1  0   3  0 714e  47   26 f6aac S    05  0:00 - std.9600 
b000001   0   285     1  0   3  0 7324  47   26 f6b44 S    06  0:00 - std.9600 
b000001   0   286     1  0   3  0 74fa  47   26 f6bdc S    07  0:00 - std.9600 
#

Shutdown

# shutdown -h now
Shutdown at 05:00 (in 0 minutes) [pid 348]
System shutdown time has arrived
syncing disks... done
HALT instruction, PC: 8005DC19 (BRB 8005DC18)
sim> exit

Configure DMS on the MicroVAX 3900

Boot MicroVAX 3900

KA655-A V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>boot
(BOOT/R5:0 DUA0
  2..
-DUA0
  1..0..
Ultrixboot (using VMB version 13)
Loading (a)vmunix ...
Sizes:
text = 496832
data = 91740
bss  = 578832
Starting at 0x29eb
Ultrix-32 V3.0 (Rev 64) System #1: Sat May 14 23:32:19 CDT 1988
real mem  = 67043328
avail mem = 57248768
using 3273 buffers containing 6704128 bytes of memory
KA655 processor with an FPU
       CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
dz0 at uba0 csr 160100 vec 300, ipl 17
ra1 at uq0 slave 1 (RA82)
ra0 at uq0 slave 0 (RA82)
tms0 at uq16 slave 0 (TK50)
Automatic reboot in progress...
Wed Jul  6 05:01:08 CDT 1988
/dev/ra0a: 417 files, 4183 used, 3240 free (96 frags, 393 blocks)
/dev/rra0d: umounted cleanly
/dev/rra0h: umounted cleanly
Wed Jul  6 05:01:08 CDT 1988
System supports 16 users.
check quotas: done.
savecore: checking for dump...dump does not exist
local daemons: syslog sendmail.
Removing remnant Opser files
preserving editor files
clearing /tmp
standard daemons: update cron accounting network rwhod printer.
start errlog daemon - elcsd
Wed Jul  6 05:01:09 CDT 1988
Ultrix-32 V3.0 (Rev 64) (piggy)
login: root
Password: ult030 (not echoed)
Last login: Wed Jul  6 04:34:00 on console
Ultrix-32 V3.0 (Rev 64) System #1: Sat May 14 23:32:19 CDT 1988
                Digital Equipment Corporation
                Nashua, New Hampshire
*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***
The following files were created during the installation procedure:
/vmunix                         - customized kernel
/genvmunix                      - generic kernel
/usr/adm/install.log            - installation log file
/usr/adm/install.FS.log         - file systems log file
/usr/adm/install.DEV.log        - special device log file
#

Set Up Network File System (NFS)

# /etc/nfssetup
Checking kernel configuration...
The nfssetup command configures the network file system (NFS)
environment for your system.  All systems using NFS facilities
must run the Remote Procedure Call (RPC) port mapper daemon.
An entry for this daemon is placed in the /etc/rc.local file
along with entries for the optional daemons you select.
You will be asked a series of questions about your system.
Default answers are shown in square brackets ([]).  To use a
default answer, press the RETURN key.
       Local locking supports local file and file region locking. Local
       locking is the default.  NFS locking supports local and remote (NFS) 
       file and file region locking. If you would like to enable the NFS
       locking functionality, then answer 'y' to the following question.
       NFS locking to be enabled [n] ? y
       Will you be exporting any directories [n] ? y
       Systems that export NFS directories must run /etc/nfsd to
       handle NFS requests from clients.  You can configure up
       to 20 nfsd daemons, but for average workload situations,
       4 is a good number to run.
       Enter the number of nfsd servers to run [4] : [RETURN]
       NFS clients can use block I/O daemons for buffering
       data transfers, although their use is not required.
       You can configure up to 5 biod daemons on your system
       based upon the workload you expect, but for average
       workload situations, 4 is a good number to run.
       Enter the number of block I/O daemons to run [4] : [RETURN]
       NFS clients that rely heavily on having certain NFS
       directories mounted may wish to be notified in the
       event of NFS servers going down.  In order for users
       on your system to receive notifications, you must run
       the remote wall daemon. (rwalld)
       Would you like to run the rwalld daemon [n] ? y
You are now setting up your directory export list.  Enter the
full pathnames of the directories to be exported.  For each
pathname, enter the network group names and/or machine names to
be given access permission to this directory, or a null list to
indicate general permission.  (Network groups are ONLY available
on machines using Yellow Pages).  This information is placed in the
/etc/exports file.  Press the RETURN key to terminate the pathname
and permissions lists.
Enter the directory pathname: /usr/users
       Netgroup/Machine name: usr
       Netgroup/Machine name: [RETURN]
Enter the directory pathname: [RETURN]
Directory export list complete...
You will now be asked to provide information about the remote file
systems you wish to access.  First list the name of the remote host
serving the directories you wish to mount, then give the full directory
pathnames.  Also, for each remote directory, you must specify the full
directory pathname of the mount point on the local machine and whether
the mount is read-only or read-write.  (Nfssetup will create the mount
point directory if it does not already exist.)  Press the RETURN key to
terminate the host and directory pathname lists:
Enter the remote host name: [RETURN]
Remote directory mount list complete...
Please confirm the following information which you
have entered for your NFS environment:
       4 nfsd daemons
       4 biod daemons
       locking daemons installed
       rwalld daemon installed
       Directory export list:
               /usr/users exported to: usr
       No remote directories to mount
Enter "c" to CONFIRM the information, "q" to QUIT nfssetup
without making any changes, or "r" to RESTART the procedure [no default]: c
Updating files:
       /etc/rc.local
       /etc/exports
The necessary NFS daemon entries have been placed in the file /etc/rc.local.
In order to begin using NFS, you must now start the daemons and mount
any remote directories you wish to access.  You may either allow nfssetup
to start these daemons automatically or invoke them by hand, but in either
case they will be started automatically on subsequent reboots.
Would you like nfssetup to start the daemons automatically [y]? [RETURN]
The NFS daemons for your machine have been started. In order to mount the
remote directories you wish to access, type the following command after
exiting from nfssetup:
       # /etc/mount -a -t nfs
***** NFSSETUP COMPLETE *****
# cat /etc/exports
/usr/users             usr
# ps -axl
      F UID   PID  PPID CP PRI NI ADDR  SZ  RSS WCHAN STAT TT  TIME COMMAND
2000003   0     0     0  0 -25  0  8eb   0    0 fa1a6 D    ?   0:00 swapper
b000001   0     1     0  0   5  0 4c3e 248  225 37e08 I    ?   0:00 init
3000003   0     2     0  0 -24  0 4c1e4096    0 37ec8 D    ?   0:00 pagedaemon
3008001   0    59     1  0   1  0 5422 264  169 872e4 I    ?   0:00 /usr/lib/se
3000201   0    66     1  0  15  0 55b2   4    2 fe400 S    ?   0:00 /etc/update
3000201   0    69     1  0  15  0 5576  26    6 fe400 I    ?   0:00 /etc/cron
3000001   0    75     1  0   1  0 5512  62   30 fa1c8 I    ?   0:00 /etc/inetd
3000001   0    79     1  0   1  0 566c 171   98 8cc24 I    ?   0:00 /etc/rwhod
3008001   0    86     1  0   1  0 5790  56   31 fa1c8 I    ?   0:00 /usr/lib/lp
3000001   1    88     1  0   1  0 586a  43   23 8dca4 I    ?   0:00 /etc/syslog
b008001   0    94     1  0  25  0 58e2  39   28       R    co  0:00 -csh (csh)
3000001   0   103     1  0   1  0 688c 110   44 fa1c8 I    ?   0:00 /etc/elcsd
3000001   0   418     1  0   1  0 5f7e  33   17 fa1c8 I    ?   0:00 /etc/portma
3000001   0   420     1  0   1  0 5bb2  84   40 fa1c8 I    co  0:00 /etc/mountd
3000001   0   422     1  0   1  0 5afa  71   23 91d24 I    ?   0:00 /etc/nfsd 4
3000001   0   423     1  0   1  0 5abc  71   23 91d24 I    ?   0:00 /etc/nfsd 4
3000001   0   424     1  0   1  0 614e  71   23 91d24 I    ?   0:00 /etc/nfsd 4
3000001   0   425     1  0   1  0 6110  71   23 91d24 I    ?   0:00 /etc/nfsd 4
3000001   0   427     1  0   1  0 6056   6    4  b754 I    ?   0:00 /etc/biod 4
3000001   0   428     1  0   1  0 606e   6    4  b754 I    ?   0:00 /etc/biod 4
3000001   0   429     1  0   1  0 6086   6    4  b754 I    ?   0:00 /etc/biod 4
3000001   0   430     1  0   1  0 609e   6    4  b754 I    ?   0:00 /etc/biod 4
3000001   0   432     1  0   1  0 6956  33   17 fa1c8 I    co  0:00 /usr/etc/rw
b000001   0   438    94  7  26  0 6a2e 246  132       R    co  0:00 ps -axl
b000001   0    95     1  0   3  0 5a74  47   28 1adac I    00  0:00 - std.9600 
b000001   0    96     1  0   3  0 5c4a  47   28 1ae44 I    01  0:00 - std.9600 
b000001   0    97     1  0   3  0 5e20  47   28 1aedc I    02  0:00 - std.9600 
b000001   0    98     1  0   3  0 5ff6  47   28 1af74 I    03  0:00 - std.9600 
b000001   0    99     1  0   3  0 61cc  47   26 f6a14 I    04  0:00 - std.9600 
b000001   0   100     1  0   3  0 63a2  47   26 f6aac I    05  0:00 - std.9600 
b000001   0   101     1  0   3  0 6578  47   26 f6b44 I    06  0:00 - std.9600 
b000001   0   102     1  0   3  0 674e  47   26 f6bdc I    07  0:00 - std.9600 
#

Set Up DMS Disk Partitions

# dms
       **************************************************************
       ***********            LICENSING NOTICE              *********
       ***********                  FROM                    *********
       ***********       DIGITAL EQUIPMENT CORPORATION      *********
       Digital Equipment Corporation and most software vendors
       distribute software products under Software License Agreements
       which govern the installation and use of their software.
       YOU are responsible for ensuring that the correct Software
       Licenses have been obtained BEFORE completing this procedure.
       Descriptions of License Options available for specific Digital
       Equipment Corporation products may be found in the applicable
       Software Product Descriptions (SPD).  
       Should you have questions concerning any of the above, please
       contact your local Digital Equipment Representative, or call
       1-800-DIGITAL for assistance. 
To continue please enter the superuser password: ult030 (not echoed)
       DISKLESS MANAGEMENT SERVICES (DMS) UTILITY MENU
       Configure Server Menu    => c
       Add Client Processor     => a
        Remove Client Processor  => r
       Modify Client Parameters => m
       List Configurations Menu => l
       Exit                     => e
Enter your choice: c
               Configure Server Menu
               Set up Disk Partitions                 => d
               Install Software into an Environment   => i
               Set up Clients' Defaults               => s
               Rebuild Kernels                        => k
Enter your choice: d
This utility is used to partition a disk into the file systems necessary
to run a diskless environment. The disk will be totally reconfigured
All the current data and file systems on the disk will be removed.
The disk must be already formatted.
Do you want to continue? (y/n) [n]: y
Enter the raw device special file name of the "c" partition of
the desired disk, for example /dev/rra2c: /dev/rra1c
Press RETURN when /dev/rra1c is ready. [RETURN]
Warning: missing disk partition table
The diskless server uses both dlenv and dlclient file systems:
dlenv    = contains one or more common root areas with
           a shared usr area in each,
           allocated in partition d
           recommended size range = 35-120 Mbytes
dlclient = contains each diskless client's root and swap areas 
           allocated in partition e
           recommended size ranges per client = 5-10 Mbytes/root 
                                                8-24 Mbytes/swap
Remaining disk space is allocated to partition f, if
more than 20 Mbytes are available.
The disk you have selected has 566 Mbytes available.
Please select one of the following uses for this disk: 
       1) Both dlenv and dlclient areas are to reside
          on this disk.
       2) Only a dlenv area is to reside on this disk.
       3) Only a dlclient area is to reside on this disk.
Enter your selection: 1
Each diskless client requires a swap file and a root area.
The distribution of swap files and root areas over multiple
disks will increase performance. The distribution may also allow
more space to be dedicated for additional diskless clients.
Each diskless client is allocated a swap file. 
Swap files should be at least two times the main memory
size of the diskless client.
The recommended swap file size range is 8 to 24 Mbytes.
Enter the swap file size in Mbytes: 16
A root area is propagated to each diskless client.
The recommended range is 5 to 10 Mbytes.
Enter the propagated root area size in Mbytes: 10
Partitioning the dlenv area
The disk you have selected has 566 Mbytes available.
The recommended size range of the sharable usr portion
of the dlenv file system is 35 to 539 Mbytes.
Enter the size of the sharable usr portion in Mbytes: 400
Creating the dlenv partition on /dev/rra1d.
Warning: partition table overriding /etc/disktab
Warning: 815 sector(s) in last cylinder unallocated
/dev/rra1d:    855040 sectors in 1001 cylinders of 15 tracks, 57 sectors
       437.8Mb in 63 cyl groups (16 c/g, 7.00Mb/g, 2048 i/g)
super-block backups (for fsck -b#) at:
 32, 13776, 27520, 41264, 55008, 68752, 82496, 96240, 109984, 123728,
 137472, 151216, 164960, 178704, 192448, 206192, 218912, 232656, 246400, 260144,
 273888, 287632, 301376, 315120, 328864, 342608, 356352, 370096, 383840, 397584,
 411328, 425072, 437792, 451536, 465280, 479024, 492768, 506512, 520256, 534000,
 547744, 561488, 575232, 588976, 602720, 616464, 630208, 643952, 656672, 670416,
 684160, 697904, 711648, 725392, 739136, 752880, 766624, 780368, 794112, 807856,
 821600, 835344, 849088,
** /dev/rra1d
** Last Mounted on 
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
2 files, 9 used, 410358 free (14 frags, 51293 blocks)
Finished making the dlenv area
Updating /etc/fstab with dlenv0 entry
Updating /etc/exports with dlenv0 entry
Mounting the dlenv0 filesystem
Enter the number of clients you want to support
on this disk. 
Enter a number between 1 and 6: 5
5 clients will be supported
Creating the dlclient partition on /dev/rra1e
Warning: partition table overriding /etc/disktab
Warning: 842 sector(s) in last cylinder unallocated
/dev/rra1e:    277888 sectors in 326 cylinders of 15 tracks, 57 sectors
       142.3Mb in 21 cyl groups (16 c/g, 7.00Mb/g, 2048 i/g)
super-block backups (for fsck -b#) at:
 32, 13776, 27520, 41264, 55008, 68752, 82496, 96240, 109984, 123728,
 137472, 151216, 164960, 178704, 192448, 206192, 218912, 232656, 246400, 260144,
 273888,
        Wed Jul 6 06:15:00 CDT 1988
** /dev/rra1e
** Last Mounted on 
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
2 files, 9 used, 133206 free (14 frags, 16649 blocks)
Finished making the dlclient area
Updating /etc/fstab with dlclient0 entry
Updating /etc/exports with dlclient0 entry
Mounting the dlclient0 filesystem
Creating /dev/rra1f for remaining space
Warning: partition table overriding /etc/disktab
Warning: 62 sector(s) in last cylinder unallocated
/dev/rra1f:    83728 sectors in 98 cylinders of 15 tracks, 57 sectors
       42.9Mb in 7 cyl groups (16 c/g, 7.00Mb/g, 2048 i/g)
super-block backups (for fsck -b#) at:
 32, 13776, 27520, 41264, 55008, 68752, 82496,
** /dev/rra1f
** Last Mounted on 
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
2 files, 9 used, 39934 free (14 frags, 4990 blocks)
This is your new disk configuration:
/dev/rra1c
Current partition table:
partition     bottom        top       size    overlap
    a              0      15883      15884    b,c,d,g,h
    b              0          0          0    a,c,d,g,h
    c              0    1216664    1216665    a,b,d,e,f,g,h
    d              0     855039     855040    a,b,c,g,h
    e         855040    1132927     277888    c
    f        1132928    1216664      83737    c
    g              0          0          0    a,b,c,d,h
    h              0          0          0    a,b,c,d,g
Partition d contains the dlenv area.
Partition e contains the dlclient area.
Partition f contains the available space,
if more than 20 Mbytes remain.
Disk partitioning is completed.
#

Install ULTRIX V3.0 Supported Software into a DMS Environment

# dms
       **************************************************************
       ***********            LICENSING NOTICE              *********
       ***********                  FROM                    *********
       ***********       DIGITAL EQUIPMENT CORPORATION      *********
       Digital Equipment Corporation and most software vendors
       distribute software products under Software License Agreements
       which govern the installation and use of their software.
       YOU are responsible for ensuring that the correct Software
       Licenses have been obtained BEFORE completing this procedure.
       Descriptions of License Options available for specific Digital
       Equipment Corporation products may be found in the applicable
       Software Product Descriptions (SPD).  
       Should you have questions concerning any of the above, please
       contact your local Digital Equipment Representative, or call
       1-800-DIGITAL for assistance. 
To continue please enter the superuser password: ult030 (not echoed)
       DISKLESS MANAGEMENT SERVICES (DMS) UTILITY MENU
       Configure Server Menu    => c
       Add Client Processor     => a
        Remove Client Processor  => r
       Modify Client Parameters => m
       List Configurations Menu => l
       Exit                     => e
Enter your choice: c
               Configure Server Menu
               Set up Disk Partitions                 => d
               Install Software into an Environment   => i
               Set up Clients' Defaults               => s
               Rebuild Kernels                        => k
Enter your choice: i
Setting up mop_mom in rc.local
Are you installing ULTRIX-32 supported software? (y/n) [n]: y
mop_mom listening on qe0
You have chosen to install a new diskless environment.
The environment is /usr/var/diskless/dlenv0/root0.vax.
Enter the device special file name or mount point of the
distribution media, for example, /dev/rmt0h: /dev/rmt0h
Please make sure your installation tape is mounted and on-line.
Are you ready? (y/n): y
Positioning tape...done.
*** Enter Subset Selections ***
The following subsets are mandatory and will be installed automatically:
 * Base System                           * Kernel Configuration Files           
 * TCP/IP Networking Utilities           * System Exerciser Package             
 * Network File System Utilities         * Extended (Berkeley) Mailer           
 * X11/DECwindows User Environment       * X11/DECwindows 75dpi Fonts           
The subsets listed below are optional:
 1) X11/DECwindows 100dpi Fonts          2) Optional DECwindows Applications    
 3) X10 to X11 Compatibility Tools       4) The RAND Mail Handler               
 5) Document Preparation Software        6) Adobe Font Metric Files             
 7) Software Development Utilities       8) Internationalization Tools          
 9) Source Code Control System          10) Worksystem Development Software     
11) Pascal Development Package          12) VAX C/ULTRIX                        
13) On Line Manual Pages                14) UWS Manual Pages                    
15) Accounting Software                 16) Communications Utilities            
17) Bisynchronous Communications        18) Maintenance Operations Protocol     
19) Unix-to-Unix Copy Facility          
20) All of the Above
21) None of the Above
Enter your choice(s): 21
You are installing the following subsets:
   Base System                             Kernel Configuration Files           
   TCP/IP Networking Utilities             System Exerciser Package             
   Network File System Utilities           Extended (Berkeley) Mailer           
   X11/DECwindows User Environment         X11/DECwindows 75dpi Fonts           
Is this correct? (y/n): y
Copying Base System (ULTBASE030) from tape
Verifying Base System (ULTBASE030)
Copying Kernel Configuration Files (ULTBIN030) from tape
Verifying Kernel Configuration Files (ULTBIN030)
Copying TCP/IP Networking Utilities (ULTINET030) from tape
Verifying TCP/IP Networking Utilities (ULTINET030)
Copying System Exerciser Package (ULTEXER030) from tape
Verifying System Exerciser Package (ULTEXER030)
Copying Network File System Utilities (ULTNFS030) from tape
Verifying Network File System Utilities (ULTNFS030)
Copying Extended (Berkeley) Mailer (ULTUMAIL030) from tape
Verifying Extended (Berkeley) Mailer (ULTUMAIL030)
Copying X11/DECwindows User Environment (UWSX11020) from tape
Verifying X11/DECwindows User Environment (UWSX11020)
Copying X11/DECwindows 75dpi Fonts (UWSFONT020) from tape
Verifying X11/DECwindows 75dpi Fonts (UWSFONT020)
Which kernels do you want to build?
SETEVAX applies to the following processor types:
        MicroVAX 2000           non-graphics
Build SETEVAX kernel? (y/n) [n]: y
SESMVAX applies to the following processor types:
        VAXstation 2000         monochrome
Build SESMVAX kernel? (y/n) [n]: y
SESGVAX applies to the following processor types:
        VAXstation 2000         color
Build SESGVAX kernel? (y/n) [n]: y
QETEVAX applies to the following processor types:
        MicroVAX II             non-graphics
        MicroVAX 3500/3600 series    non-graphics
Build QETEVAX kernel? (y/n) [n]: y
QEQVVAX applies to the following processor types:
        VAXstation II           monochrome
Build QEQVVAX kernel? (y/n) [n]: y
QEQDVAX applies to the following processor types:
        VAXstation II/GPX       color
        VAXstation 3200/3500    color
        VAXstation 3200/3500    monochrome
Build QEQDVAX kernel? (y/n) [n]: y
QEQD2VAX applies to the following processor types:
        VAXstation II/GPX
            multi-station       color
Build QEQD2VAX kernel? (y/n) [n]: y
PVSMVAX applies to the following processor types:
        VAXstation 3100         monochrome
Build PVSMVAX kernel? (y/n) [n]: y
PVSGVAX applies to the following processor types:
        VAXstation 3100         color
Build PVSGVAX kernel? (y/n) [n]: y
LNTEVAX applies to the following processor types:
        MicroVAX 3300/3400      non-graphics
Build LNTEVAX kernel? (y/n) [n]: y
LNFGVAX applies to the following processor types:
        VAXstation 3520/3540    color
Build LNFGVAX kernel? (y/n) [n]: [RETURN]
Building kernels.  This may take several hours
for some processor types.
*** PERFORMING SYSTEM CONFIGURATION *** 
Warning: UFS not configured
    working ..... Wed Jul  6 06:23:23 CDT 1988
*** PERFORMING SYSTEM CONFIGURATION *** 
Warning: UFS not configured
    working ..... Wed Jul  6 06:23:39 CDT 1988
*** PERFORMING SYSTEM CONFIGURATION *** 
Warning: UFS not configured
    working ..... Wed Jul  6 06:23:57 CDT 1988
*** PERFORMING SYSTEM CONFIGURATION *** 
Warning: UFS not configured
    working ..... Wed Jul  6 06:24:13 CDT 1988
*** PERFORMING SYSTEM CONFIGURATION *** 
Warning: UFS not configured
    working ..... Wed Jul  6 06:24:34 CDT 1988
*** PERFORMING SYSTEM CONFIGURATION *** 
Warning: UFS not configured
    working ..... Wed Jul  6 06:24:51 CDT 1988
*** PERFORMING SYSTEM CONFIGURATION *** 
Warning: UFS not configured
    working ..... Wed Jul  6 06:25:07 CDT 1988
*** PERFORMING SYSTEM CONFIGURATION *** 
Warning: UFS not configured
    working ..... Wed Jul  6 06:25:26 CDT 1988
*** PERFORMING SYSTEM CONFIGURATION *** 
Warning: UFS not configured
    working ..... Wed Jul  6 06:25:44 CDT 1988
*** PERFORMING SYSTEM CONFIGURATION *** 
Warning: UFS not configured
    working ..... Wed Jul  6 06:26:01 CDT 1988
#

Set Up DMS Clients' Defaults

# dms
        **************************************************************
        ***********            LICENSING NOTICE              *********
        ***********                  FROM                    *********
        ***********       DIGITAL EQUIPMENT CORPORATION      *********
        Digital Equipment Corporation and most software vendors
        distribute software products under Software License Agreements
        which govern the installation and use of their software.
        YOU are responsible for ensuring that the correct Software
        Licenses have been obtained BEFORE completing this procedure.
        Descriptions of License Options available for specific Digital
        Equipment Corporation products may be found in the applicable
        Software Product Descriptions (SPD).  
        Should you have questions concerning any of the above, please
        contact your local Digital Equipment Representative, or call
        1-800-DIGITAL for assistance. 
To continue please enter the superuser password: ult030 (not echoed)
        DISKLESS MANAGEMENT SERVICES (DMS) UTILITY MENU
        Configure Server Menu    => c
        Add Client Processor     => a
        Remove Client Processor  => r
        Modify Client Parameters => m
        List Configurations Menu => l
        Exit                     => e
Enter your choice: c
                Configure Server Menu
                Set up Disk Partitions                 => d
                Install Software into an Environment   => i
                Set up Clients' Defaults               => s
                Rebuild Kernels                        => k
Enter your choice: s
This option lets you set up or change
the server's diskless environment defaults
for clients.
Enter answers to the following prompts.
If there is a default, it appears in square brackets.
Press RETURN to accept the default.
Select the the root directory to be copied for clients: 
1       /usr/var/diskless/dlenv0/root0.vax
Enter your choice []: 1
Select the file system to contain the clients' root directories: 
1       /usr/var/diskless/dlclient0
Enter your choice []: 1
Select the file system to contain the clients' swap file: 
1       /usr/var/diskless/dlclient0
Enter your choice []: 1
Select the swap file system location, 0-client (disk), 1-server []: 1
Enter swap file size, in 1/2-Mbyte increments []: 16
Do you want clients to dump across the network?
Enter n (no dump), f (full dump), p (partial dump) []: n
Select the processor type for this client:
 1  VAXstation  II/GPX          color
 2  VAXstation  II/GPX
        (multi-station)         color
 3  VAXstation  II              monochrome
 4  MicroVAX    II              no graphics
 5  VAXstation  2000            color
 6  VAXstation  2000            monochrome
 7  MicroVAX    2000            no graphics
 8  VAXstation  3200/3500       color
 9  VAXstation  3200/3500       monochrome
10  MicroVAX    3500/3600       no graphics 
11  MicroVAX    3300/3400       no graphics
12  VAXstation  3100            color
13  VAXstation  3100            monochrome
14  VAXstation  3520/3540       color
Enter your selection []: 4
The next question asks if you want clients linked to a default kernel.
It is recommended that you answer yes to save disk space.
If you answer no, each client gets a separate copy of a default kernel.
Answering no also allows the client to use a customized kernel.
Link to a default kernel? (y/n) []: y
#

Configure DMS Client TCP/IP Networking at the DMS Server

# netsetup
You will be asked a series of questions about your system.
Default answers are shown in square brackets ([]).
To use a default answer, press the RETURN key.
***** ADD/CHANGE SYSTEMS IN /etc/hosts *****
Enter the host name, abbreviations, network number, and host number for
each host on the network.  Enter this information on separate lines
when prompted.  This information is stored in the /etc/hosts file.  When
finished, press the RETURN key at the hostname prompt.
Enter the name of the host you want to add to /etc/hosts: louie
You want to add host "louie".  Is this correct [yes]? [RETURN]
Enter any abbreviations for "louie", separated by a blank space.
If you do not want any abbreviation names, press the RETURN key: [RETURN]
You do not want any abbreviation names for "louie".  Is this correct [yes]? [RETURN]
For a Class A network, the network number is in the range 1 through
126.  For a Class B network, the network number consists of two fields
separated by periods.  The first field is in the range 128 through 191,
and the second field is in the range 1 through 254.  For a Class C
network, the network number consists of three fields separated by
periods.  The first field is in the range 192 through 223, the second
field is in the range 0 through 255, and the third field is in the
range 1 through 254:
   Class A:  1       through 126
   Class B:  128.1   through 191.254
   Class C:  192.0.1 through 223.255.254
Enter the network number for louie: 10
The network number is 10.  Is this correct [yes]? [RETURN]
You are setting up piggy on a Class A network.
Valid Class A host numbers consist of three fields separated by
periods.  The first two fields are in the range 0 through 255, and
the third field is in the range 1 through 254:
   0.0.1 through 255.255.254
An alternate representation for the three bytes of information specifying
the host number is one field in the range 1 through 16777214:
   1 through 16777214
Enter the host number for louie: 5
The Host number is 0.0.5.  Is this correct [yes]? [RETURN]
Enter the name of the host you want to add to /etc/hosts: [RETURN]
Are you finished adding hosts [yes]? [RETURN]
Enter the names of trusted hosts.  Trusted hosts are systems you
consider to be secure.  Be careful if you select trusted hosts.  Any
users on a trusted host can log in to piggy without password
verification if they have a valid account on your system.  The names of
the trusted hosts are stored in the /etc/hosts.equiv file.  When you
have finished entering the names of trusted hosts, press the RETURN key.
Enter the name of a trusted host: louie
"louie" is a trusted host.  Is this correct [yes]? [RETURN]
Enter the name of a trusted host: [RETURN]
Have you finished entering the names of trusted hosts [yes]? [RETURN]
***** SETTING UP /usr/hosts DIRECTORY *****
***** NETWORK SETUP COMPLETE *****

Add a MicroVAX II as DMS Client

# dms
        **************************************************************
        ***********            LICENSING NOTICE              *********
        ***********                  FROM                    *********
        ***********       DIGITAL EQUIPMENT CORPORATION      *********
        Digital Equipment Corporation and most software vendors
        distribute software products under Software License Agreements
        which govern the installation and use of their software.
        YOU are responsible for ensuring that the correct Software
        Licenses have been obtained BEFORE completing this procedure.
        Descriptions of License Options available for specific Digital
        Equipment Corporation products may be found in the applicable
        Software Product Descriptions (SPD).  
        Should you have questions concerning any of the above, please
        contact your local Digital Equipment Representative, or call
        1-800-DIGITAL for assistance. 
To continue please enter the superuser password: ult030 (not echoed)
        DISKLESS MANAGEMENT SERVICES (DMS) UTILITY MENU
        Configure Server Menu    => c
        Add Client Processor     => a
        Remove Client Processor  => r
        Modify Client Parameters => m
        List Configurations Menu => l
        Exit                     => e
Enter your choice: a
You have chosen to add a client for diskless management services.
This utility lets you register a client for diskless management
services.
         
The following conditions must be met to run this utility successfully:
         
        1. The client must be entered in the server's /etc/hosts file
        2. You must know the client's hostname 
        3. You must know the client's hardware Ethernet address 
Do you want to continue? (y/n) [y]: [RETURN] 
Enter the client processor's hostname: louie
Enter the client processor's hardware Ethernet address, for
example, 08-00-2B-02-67-E1 []: 08-00-2B-0B-18-1A
Select the name of the file system to contain the
client's root directory: 
1       /usr/var/diskless/dlclient0
Enter your choice [1]: [RETURN]
Copying the client's root directory ...
This may take up to 30 minutes depending on the processor.
Enter passwd for root on louie
New password: ult030 (not echoed)
Retype new password: ult030 (not echoed)
Select the swap file system location, 0-client (disk), 1-server [1]: [RETURN]
Select name of the file system to contain the swap file: 
1       /usr/var/diskless/dlclient0
Enter your choice [1]: [RETURN]
Select the client's swap file size in 1/2-Mbyte increments.  
For example, enter 16 for an 8-Mbyte swap file [16]: [RETURN]
Creating the client's swap file ...
Do you want the client to dump across the network to piggy?
Enter n (no dump), f (full dump), p (partial dump) [n]: [RETURN]
Select the processor type for this client:
Enter n (no dump), f (full dump), p (partial dump) [n]: 
Select the processor type for this client:
 1  VAXstation         II/GPX          color
 2  VAXstation         II/GPX
       (multi-station)         color
 3  VAXstation         II              monochrome
 4  MicroVAX   II              no graphics
 5  VAXstation         2000            color
 6  VAXstation         2000            monochrome
 7  MicroVAX   2000            no graphics
 8  VAXstation  3200/3500      color
 9  VAXstation  3200/3500      monochrome
10  MicroVAX   3500/3600       no graphics
11  MicroVAX   3300/3400       no graphics
12  VAXstation  3100           color
13  VAXstation         3100            monochrome
14  VAXstation         3520/3540       color   
Enter your selection [6]: 4
MAKEDEV: special file(s) for console: 
console 
MAKEDEV: special file(s) for drum: 
drum 
MAKEDEV: special file(s) for errlog: 
errlog 
MAKEDEV: special file(s) for kUmem: 
kUmem 
MAKEDEV: special file(s) for kmem: 
kmem 
MAKEDEV: special file(s) for mem: 
mem 
MAKEDEV: special file(s) for null: 
null 
MAKEDEV: special file(s) for tty: 
tty 
MAKEDEV: special file(s) for pty0: 
ptyp0 ttyp0 ptyp1 ttyp1 ptyp2 ttyp2 ptyp3 ttyp3 ptyp4 ttyp4 ptyp5 ttyp5 ptyp6 ttyp6 ptyp7 ttyp7 ptyp8 ttyp8 ptyp9 ttyp9 ptypa ttypa ptypb ttypb ptypc ttypc ptypd ttypd ptype ttype ptypf ttypf 
The next question asks if you want this client linked to a default kernel.
It is recommended that you answer yes to save disk space.
If you answer no, each client gets a separate copy of a default kernel.
Answering no also allows the client to use a customized kernel.
Link to a default kernel? (y/n) [y]: [RETURN]
Running software control programs on louie's root area
Configuring ULTBASE030
Configuring ULTBIN030
Configuring ULTEXER030
Configuring ULTINET030
Configuring ULTNFS030
Configuring ULTUMAIL030
Do you want to add another client processor to the
/usr/var/diskless/clients directory? (y/n) [n]: [RETURN]
#

Boot the DMS Client over Network

First DMS Client Boot

KA630-A.V1.3
Performing normal system tests.
  5..4..3..
Tests completed.
>>> b xqa0
  2..1..0..
Ultrixload (using VMB version 13)
Host server is 'piggy'
Loading operating system image ...
****************
Ultrix-32 V3.0 (Rev 64) System #1: Wed Jul  6 06:25:23 CDT 1988
real mem  = 16769024
avail mem = 13457408
using 818 buffers containing 1676288 bytes of memory
MicroVAX-II with an FPU
Q22 bus
qe0 at uba0 csr 174440 vec 774, ipl 17
root on piggy:/usr/var/diskless/dlclient0/louie.root
swap on piggy:/usr/var/diskless/dlclient0/louie.swap
swap size - 16384 blocks
Automatic reboot in progress...
Wed Jul  6 12:37:19 EDT 1988
System supports 2 users (the default).
local daemons: syslog biod sendmail.
Removing remnant Opser files
running installation verification
ULTBASE030
Checking setld data files.
ULTBIN030
Checking setld data files.
ULTEXER030
Checking setld data files.
ULTINET030
Checking setld data files.
ULTNFS030
Checking setld data files.
ULTUMAIL030
Checking setld data files.
preserving editor files
standard daemons:clearing /tmp
 update cron accounting network rwhod printer.
start errlog daemon - elcsd
Wed Jul  6 12:37:23 EDT 1988
Ultrix-32 V3.0 (Rev 64) (louie)
login: root
Password: ult030 (not echoed)
Ultrix-32 V3.0 (Rev 64) System #1: Wed Jul  6 06:25:23 CDT 1988
                Digital Equipment Corporation
                Nashua, New Hampshire
#
# df
Filesystem                                   Total    kbytes   kbytes   %     
node                                         kbytes   used     free     used  Mounted on
piggy:/usr/var/diskless/dlclient0/louie.root  133215   10834  109060     9%   /
piggy:/usr/var/diskless/dlenv0/root0.vax/usr  410367   42449  326882    11%   /usr
# mount
piggy:/usr/var/diskless/dlclient0/louie.root on / type nfs (rw,hard)
piggy:/usr/var/diskless/dlenv0/root0.vax/usr on /usr type nfs (ro,hard)
# nfsstat
Server rpc:
calls      badcalls   nullrecv   badlen     xdrcall
0          0          0          0          0          
Server nfs:
calls      badcalls
0          0          
null       getattr    setattr    root       lookup     readlink   read       
0 0%       0 0%       0 0%       0 0%       0 0%       0 0%       0 0%       
wrcache    write      create     remove     rename     link       symlink    
0 0%       0 0%       0 0%       0 0%       0 0%       0 0%       0 0%       
mkdir      rmdir      readdir    fsstat     
0 0%       0 0%       0 0%       0 0%       
Client rpc:
calls      badcalls   retrans    badxid     timeout    wait       newcred
13577      0          0          0          0          0          0          
Client nfs:
calls      badcalls   nclget     nclsleep
13573      0          13573      0          
null       getattr    setattr    root       lookup     readlink   read       
0  0%      510  3%    102  0%    0  0%      10087 74%  2155 15%   325  2%    
wrcache    write      create     remove     rename     link       symlink    
0  0%      55  0%     22  0%     14  0%     5  0%      2  0%      0  0%      
mkdir      rmdir      readdir    fsstat     
6  0%      6  0%      277  2%    7  0%      
# netstat -i
Name  Mtu   Network     Address            Ipkts Ierrs    Opkts Oerrs  Coll
qe0   1500  10          louie              14834     0    13624     0     0
lo0   1536  loop        localhost              0     0        0     0     0
# ifconfig qe0
qe0: 10.0.0.5 netmask ff000000 flags=0x443<DYNPROTO,RUNNING,BROADCAST,UP>
broadcast: 10.255.255.255
# shutdown -h now
Shutdown at 12:41 (in 0 minutes) [pid 301]
System shutdown time has arrived
syncing disks... done
?06 HLT INST
    PC = 8005208D
>>> [CTRL + e]
sim> exit

"Normal" DMS Client Boot

KA630-A.V1.3
Performing normal system tests.
  5..4..3..
Tests completed.
Loading system software.
  2..1..0..
Ultrixload (using VMB version 13)
Host server is 'piggy'
Loading operating system image ...
****************
Ultrix-32 V3.0 (Rev 64) System #1: Wed Jul  6 06:25:23 CDT 1988
real mem  = 16769024
avail mem = 13457408
using 818 buffers containing 1676288 bytes of memory
MicroVAX-II with an FPU
Q22 bus
qe0 at uba0 csr 174440 vec 774, ipl 17
root on piggy:/usr/var/diskless/dlclient0/louie.root
swap on piggy:/usr/var/diskless/dlclient0/louie.swap
swap size - 16384 blocks
Automatic reboot in progress...
Wed Jul  6 12:42:36 EDT 1988
System supports 2 users (the default).
local daemons: syslog biod sendmail.
Removing remnant Opser files
preserving editor files
standard daemons:clearing /tmp
 update cron accounting network rwhod printer.
start errlog daemon - elcsd
Wed Jul  6 12:42:37 EDT 1988
Ultrix-32 V3.0 (Rev 64) (louie)
login: root
Password: ult030 (not echoed)
Last login: Wed Jul  6 12:37:34 on console
Ultrix-32 V3.0 (Rev 64) System #1: Wed Jul  6 06:25:23 CDT 1988
                Digital Equipment Corporation
                Nashua, New Hampshire
# shutdown -h now
Shutdown at 12:43 (in 0 minutes) [pid 95]
System shutdown time has arrived
syncing disks... done
?06 HLT INST
    PC = 8005208D
>>> [CTRL + e]
Simulation stopped, PC: 20040CAF (MFPR #20,R1)
sim> exit

Install 16 User License Key on the DMS Client

Set Account "ris" to No Password on the DMS Server

Log in as root and edit /etc/passwd as follows:

# ed /etc/passwd
782
1,$n
1       root:M1bQ4pf2tBs9.:0:1:System PRIVILEGED Account:/:/bin/csh
2       field:e1c4BYG5cIsuI:0:1:Field Service PRIVILEGED Account:/usr/field:/bin/csh
3       nobody:Nologin:-2:-2:anonymous NFS user:/:
4       operator:PASSWORD HERE:0:28:Operator PRIVILEGED Account:/opr:/opr/opser
5       ris:Nologin:11:11:Remote Installation Services Account:/usr/adm/ris:/bin/sh
6       daemon:*:1:1:Mr Background:/:
7       sys:PASSWORD HERE:2:3:Mr Kernel:/usr/sys:
8       bin:PASSWORD HERE:3:4:Mr Binary:/bin:
9       uucp:Nologin:4:1:UNIX-to-UNIX Copy:/usr/spool/uucppublic:/usr/lib/uucp/uucico
10      uucpa:Nologin:4:1:uucp adminstrative account:/usr/lib/uucp:
11      news:Nologin:8:8:USENET News System:/usr/spool/netnews:
12      sccs:PASSWORD HERE:9:10:Source Code Control:/:
13      ingres:PASSWORD HERE:267:74:& Group:/usr/ingres:/bin/csh
14      guest::268:15:guest:/usr/users/guest:/bin/csh
1,$s/ris:Nologin:/ris::
ris::11:11:Remote Installation Services Account:/usr/adm/ris:/bin/sh
w
775
q
# 

Start Remote Installation of 16 User License Key on the DMS Client

# /etc/install_upgrade piggy /dev/rmt0l

Is the correct capacity upgrade kit loaded on /dev/rmt0l at piggy <y/n>? y
Capacity Upgrade installation done.
#
# shutdown -r now
Shutdown at 04:32 (in 0 minutes) [pid 152]
# 
System shutdown time has arrived
syncing disks... done

Loading system software.

                          2..1..0..


Ultrixload (using VMB version 13)

Host server is 'piggy'
Loading operating system image ...
****************
Ultrix-32 V3.0 (Rev 64) System #1: Wed Jul  6 06:25:23 CDT 1988
real mem  = 16769024
avail mem = 13457408
using 818 buffers containing 1676288 bytes of memory
MicroVAX-II with an FPU
Q22 bus
qe0 at uba0 csr 174440 vec 774, ipl 17
root on piggy:/usr/var/diskless/dlclient0/louie.root
swap on piggy:/usr/var/diskless/dlclient0/louie.swap
swap size - 16384 blocks
Automatic reboot in progress...
Thu Jul  7 04:32:17 EDT 1988
System supports 16 users.
local daemons: syslog biod sendmail.
Removing remnant Opser files
preserving editor files
standard daemons:clearing /tmp
 update cron accounting network rwhod printer.
start errlog daemon - elcsd
Thu Jul  7 04:32:18 EDT 1988


Ultrix-32 V3.0 (Rev 64) (louie)

login: root
Password:
Last login: Thu Jul  7 04:21:29 on console
Ultrix-32 V3.0 (Rev 64) System #1: Wed Jul  6 06:25:23 CDT 1988

                Digital Equipment Corporation
                Nashua, New Hampshire

#