You can start the Device Configuration Utility in either of these ways:
Use this procedure to add a new hardware controller.
Some hardware requires manual configuration. For example, you may have to set jumper pins on a hardware card. Check the documentation provided with the hardware you are installing.
If you attach a peripheral to a non-SCSI controller, configure the device according to the information found in the documentation provided with the controller and peripheral.
To view existing SCSI hardware data, enter the following
command as root:
/etc/scsi/sdiconfig -l
See the sdiconfig(1M) manual page for additional information.
To be safe, disconnect the power cord.
Insert any needed hardware controller(s) into your system and connect the new hardware peripheral(s) to the controllers (hardware boards and/or adapters). For details, see the documentation that came with your hardware.
If the hardware you are installing has its own power supply, plug in the power cord and power up the hardware.
Some hardware comes with software that must be run in order to configure the device. When installing a new device (for example, a network adapter):
Many platform configuration utilities and/or hardware initialization programs require a DOS operating system. Sometimes the hardware vendor provides a partial DOS operating system from which you can boot your system. Otherwise, you must provide your own copy of DOS.
Then follow the instructions given in the next section.
This procedure is used to configure your devices after they have been physically added to your system.
Do the following to verify that the UnixWare 7 system is properly configured to access the new hardware and, if necessary, to revise your software configuration:
If you are not sure whether the device driver is installed and configured, go to ``Viewing hardware device configuration'' for instructions about how to verify this using the DCU.
Use the following table to decide what to do next.
| If | Then |
|---|---|
| The device driver for the controller has not been installed. | Go to Step 2. |
| The device driver for the controller is installed but has not been configured. | Go to Step 3. |
| The device driver for the controller is installed and has been automatically configured. | Go to Step 4. |
If Then The device driver for the controller has Go to Step 2. not been installed. The device driver for the controller is Go to Step 3. installed but has not been configured. The device driver for the controller is Go to Step 4. installed and has been automatically configured.
If the device driver that supports the new controller is not installed on your system, you need to install a package that contains the driver. The driver may be on the boot diskette, or it may have been provided by your hardware vendor on a separate diskette.
To install a package, insert the diskette into the diskette drive and issue a pkgadd(1M) command, or use the SCOadmin Application Installer. See ``Installing and removing software'' in the UnixWare 7 System Handbook.
You may be required to rebuild or reboot the system before you can use the new hardware. See ``Rebuilding your system''.
The UnixWare 7 system automatically detects when some controllers (for example, supported EISA, MCA, or PCI hardware) are installed on the system. If such controllers are removed from the system, the controller's device driver parameter settings are automatically removed from the system resource database.
However, if the UnixWare 7 system cannot detect whether a controller is installed on your system, the controller's device driver parameter settings are not automatically removed from the system resource database when you remove the hardware. ISA controller settings must be removed manually using the Device Configuration Utility (DCU).
You can use this procedure to remove ISA hardware components from your system.
unused.
unused back to the name of the device driver.
Sometimes when you add new hardware or change the kernel configuration, you need to rebuild the kernel. For example, when you add a new device driver, the package installation software may prompt you to rebuild the kernel.
The preferred way to rebuild the kernel is to use the idbuild(1M) command. If the rebuild fails, you can use the error messages that idbuild displays to determine the problem.
Otherwise, you can simply reboot your system. If a kernel rebuild is required, the system will perform it automatically upon rebooting.
Booting UnixWare... message is displayed.
Then, at the [boot]# prompt, enter:
To add hard disks to your system:
The system should be able to access the hard disk following the reboot.
The diskadd utility guides you through the activities necessary to complete installation of the new disk. These activities include setting up partitions, surface analysis, making new filesystems and mounting the disk, among others.
This example uses the diskadd(1M) command to add a second disk with a single partition and two filesystems (slices) to the system.
# diskadd 1 # use ``1'' for a second disk. for other disks,
# the disk_number is in the form cCbBtTdD
UX:diskadd: INFO: You have invoked the System V disk management (s5dm)
diskadd utility.
The purpose of this utility is to set up additional disk drives.
This utility can destroy the existing data on the disk. Do you wish
to continue? (Type y for yes or n for no followed by ENTER): y
The recommended default partitioning for your disk is:
a 100% "UNIX System" partition.
To select this, please type "y". To partition your disk
differently, type "n" and the "fdisk" program will let you
select other partitions. y
# if you type ``n'' the fdisk(1M) program is
# run and you can set up additional partitions
# (for example, a DOS partition).
Surface analysis of your disk is recommended but not required.
Do you wish to skip surface analysis? (y/n) n
# surface analysis is especially important for
# new disks
You will now be queried on the setup of your disk. After you
have determined which slices will be created, you will be
queried to designate the sizes of the various slices.
# before answering the following questions,
# determine how many filesystems you want to
# set up, what their names will be, and how
# much space they require
How many slices/filesystems do you want created on the disk (1 - 13)? 2
Please enter the absolute pathname (e.g., /home3) for
slice/filesystem 1 (1 - 32 chars)? /home3
Enter the filesystem type for this slice (vxfs,ufs,s5,sfs), type 'na'
if no filesystem is needed, or press <ENTER> to use the default (vxfs):
Specify the block size from the the following list
(1024, 2048, 4096, 8192), or press <ENTER> to use the first one:
# 1024 is default
Should /home3 be automatically mounted during a reboot?
Type "no" to override auto-mount or press <ENTER> to enable the option:
Please enter the absolute pathname (e.g., /home3) for
slice/filesystem 2 (1 - 32 chars)? /usr2
Enter the filesystem type for this slice (vxfs,ufs,s5,sfs), type 'na'
if no filesystem is needed, or press <ENTER> to use the default (vxfs):
Specify the block size from the the following list
(1024, 2048, 4096, 8192), or press <ENTER> to use the first one:
Should /usr2 be automatically mounted during a reboot?
Type "no" to override auto-mount or press <ENTER> to enable the option:
You will now specify the size in cylinders of each slice.
(One megabyte of disk space is approximately 1 cylinders.)
There are now 3074 cylinders available on your disk.
The filesystem type you have chosen is limited to 1048576 cylinders.
How many cylinders would you like for /home3 (0 - 3074)?
Press <ENTER> for 0 cylinders: 274
There are now 2800 cylinders available on your disk.
The filesystem type you have chosen is limited to 1048576 cylinders.
How many cylinders would you like for /usr2 (0 - 2800)?
Press <ENTER> for 0 cylinders: 2800
You have specified the following disk configuration:
A /home3 filesystem with 274 cylinders (274.0 MB)
A /usr2 filesystem with 2800 cylinders (2800.0 MB)
Is this allocation acceptable to you (y/n)? y
Filesystems will now be created on the needed slices
Creating the /home3 filesystem on /dev/rdsk/c0b0t1d0s1
Allocated approximately 70112 inodes for this file system. Specify a
new value or press <ENTER> to use the default:
Creating the /usr2 filesystem on /dev/rdsk/c0b0t1d0s2
Allocated approximately 716768 inodes for this file system. Specify a
new value or press <ENTER> to use the default:
UX:diskadd: INFO: Diskadd for Disk Drive 2 DONE at Fri Sep 05 14:47:16
# df # the df command shows the new filesystems
/ (/dev/root ): 4628818 blocks 616572 files
/proc (/proc ): 0 blocks 342 files
/stand (/dev/dsk/c0b0t0d0sa): 42954 blocks 79 files
/dev/fd (/dev/fd ): 0 blocks 0 files
/home (/dev/dsk/c0b0t0d0s4): 13026 blocks 1736 files
/home2 (/dev/dsk/c0b0t0d0sc): 13068 blocks 1740 files
/system/processor (/processorfs ): 0 blocks 0 files
/tmp (/tmp ): 14680 blocks 32123 files
/var/tmp (/var/tmp ): 61424 blocks 32765 files
/home3 (/dev/dsk/c0b0t1d0s1): 523908 blocks 69852 files
/usr2 (/dev/dsk/c0b0t1d0s2): 5372640 blocks 716348 files
To add a tape drive to your system:
The system should be able to access the tape drive following the reboot.