This section highlights updates and changes to SCO OpenServer Release 6.0.0 system management tools and commands:
SCO OpenServer Release 6.0.0 provides a number of enhancements to the boot process, including:
By default, SCO OpenServer Release 6.0.0 autoboots into multi-user mode (init run-level, or ``state'', 2).
To circumvent autoboot during system startup and get to a [boot] prompt, press the <Space> bar at the Splash screen.
To put the system into single-user mode (init run-level S or s) from the [boot] prompt, press <Enter>. At the following message, enter the root password:
Type CONTROL-d to proceed with normal startup, (or give root password for system maintenance):
System startup behavior is defined in /stand/boot and /etc/default/boot. By default, the AUTOBOOT variable in /stand/boot is set to ``1'' and MULTIUSER in /etc/default/boot is set to ``YES''. Therefore, the default system initialization behavior is to autoboot directly into multi-user mode within one second of the boot program being loaded.
To turn off autobooting, edit /stand/boot and set AUTOBOOT to ``NO''. With this setting, the [boot] prompt is always displayed after the kernel is loaded.
For more information, see the boot(HW) and init(M) manual pages. Also refer to the ``Understanding the boot process'' online help topic.
If, during the installation, you selected to autoconfigure your video adapter and enable scologin, you are automatically placed on tty02 when the system boots into multi-user mode. If the X server is not turned on during the installation, you are instead placed automatically on the console when the system boots.
System error and notification messages no longer appear on the active multiscreen (as they did on SCO OpenServer Release 5 systems), but now display on the console screen. As usual, these messages are also saved in /usr/adm/syslog.
Use <Alt><Ctrl><Fn> to switch among multiscreens:
See ``Using the system console and non-graphical displays'' for more information.
The suite of SCOadmin managers has undergone a number of changes and enhancements.
FTP Server Manager -- for common FTP configuration and administration tasks.
Floppy Filesystem Manager
Network Configuration Manager
System Startup Manager
Video Configuration Manager
Specific changes and enhancements are discussed in the corresponding manager topics.
Internet Configuration Manager
all IPX/SPX-related managers
ISA PnP Configuration Manager
all NetWare-related managers
PPP Connection Wizard
The Floppy Filesystem Manager option for creating emergency recovery floppy diskettes is no longer supported.
You can now create bootable emergency recovery CD-ROM disks, using the emergency_disk(ADM) command. See ``Emergency Recovery boot media'' for more information.
The Hardware/Kernel Manager has been modified to provide access to the Device Configuration Utility (DCU), a new utility that lists the hardware controllers and device drivers configured on your system and allows you to assign parameter values (IRQ, memory address range, DMA channel, and so forth) for the device driver. See the dcu(ADM) manual page for more information.
Because most devices are now autodetected and immediately available, many of the mkdev(ADM) scripts previously used on SCO OpenServer Release 5 systems are no longer necessary. However, some new mkdev scripts have been added:
See the mkdev(ADM) manual page for more details.
The following mkdev scripts are no longer needed:
|APC UPS Port Monitoring Daemon||Power Management|
|CD-ROM and WORM||SCSI Floptical drive|
|Corollary Daemon||SCSI Juke Box|
|DOS Filesystem||SNMP Host Resources MIB|
|HTFS Filesystem||Shell Layers|
|Hard Disk||Tape Drive|
|High Performance Pipe System||Terminal emulation control|
|High Sierra/ISO9660/RockRidge Filesystem||Tricord|
|Layers Configuration||XENIX Filesystem|
|Plug and Play Configuration Manager|
You no longer need to run the Serial Manager to add, modify, or delete serial boards. These devices are automatically configured at boot-time.
You do need to run the Serial Manager, however, to configure the ports attached to the boards, to set up the inittab entries so that you can use enable and disable on the ports. Simply starting the manager is sufficient to configure the ports -- once the manager is running, the ports are automatically configured and you can exit the manager.
No longer reports on remote resources -- NFS and NUCFS filesystems.
A new version of the ps(C) command is provided. Functionality and command output differ in the following ways:
There have also been some changes in the area of multiprocessor commands:
SCO OpenServer Release 6.0.0 provides two new commands to help manage multi-processor (MP) systems: psradm(ADM), an interface for processor configuration management and psrinfo(ADM), a tool for displaying processor information. The SCO OpenServer Release 5 command, cpuonoff(ADM), also remains available for performing these functions.
Please note that there is a difference between these commands in the starting values assigned to processors. psradm(ADM) and psrinfo(AD M) begin numbering processors with ``0'', while cpuonoff(ADM) uses a starting integer of ``1''.
The performance monitor from earlier releases, mpstat(ADM), is also available. The following updates have been made to the mpstat command:
Note that rtpm numbers processors starting with "0", while the mpstat command numbers processors starting with "1".
SCO OpenServer Release 6.0.0 provides the pbind(ADM) command, in addition to the standard lockpid(ADM) command. These commands also use different starting values for processors: pbind begins numbering processors with ``0'', while lockpid uses a starting integer of ``1''.
Because of the kernel enhancements in SCO OpenServer Release 6.0.0, there are some differences in the metrics now supported by the sar(ADM) command. Differences include:
However, when you use the -Kudk option, SVR5 variations of the -g and -R options are enabled. In this mode, -g reports on paging activities and -R reports raw data values.