Meridian Link/Customer Controlled Routing, Installation And Upgrade Manual

Page: 468 / 595

450 Chapter 14: Software installation, upgrade, and update procedures
553-3202-210 Standard October 1998
Procedure 7: Reboot and go through setup (continued)
Figure 205
System autoboot messages 2
This machine has not been used as a customer machine yet. The messages that
follow are from checking the built-in file systems for damage that might have
occurred during shipment. As long as you do not see either of the messages
BOOT SYSV68
or
FILE SYSTEM WAS MODIFIED
all is well. If either message does come out, call your service representative.
However, the machine is still usable unless you are told otherwise.
Checking file systems:
/dev/root
File System: root Volume: R3
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Free List
1992 files 27376 blocks 31684 free
/dev/usr
File System: usr Volume: R3
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Free List
2861 files 44730 blocks 327360 free
Node name set to sysV68.
Welcome!
This machine has to be set up by you. When you see the "login" message type
setup
followed by the RETURN key. This will start a procedure that leads you through
those things that should be done the "first time" the machine is used.
Until you do so, the above filesystem shipment damage check will be run
each time you boot.
mount -f S51K /dev/usr /usr
Checking for system dump ...
Expreserve notification performed.
Error logging started.
Stream Error logging started.
netspec "tcpip" not set up.
Line printer scheduler started.
The system is ready.
Console Login:
2 At the ÒConsole Login:Ó prompt, type root and press [Return] to log
in as the root user.
3 At the ÒPassword:Ó prompt, press [Return].
The root password is reset once the application is installed.