Installation guide

When you install a static subsystem, its SCP normally edits the
/usr/sys/conf/.product.list file and adds an entry for the
subsystem. After the SCP completes, you run the /usr/sbin/doconfig
program to configure the new subsystem into the kernel.
The /usr/sbin/doconfig program creates the
NAME .list file. The NAME
variable is the same as the target configuration file, and by convention, is
your system name in capital letters. For example, the
NAME .list file for a
system named MYSYS is MYSYS.list.
If you need to modify your system because of a third-party layered product
(for example, to remove a layered product from the kernel being built),
make the necessary modifications to the
NAME .list file and build a new
kernel.
Each entry in the
NAME .list file consists of six fields separated by a colon
(:). The following example is part of a
NAME .list file and shows an entry
for a static kernel subsystem that has been loaded into the
/usr/sys/opt/ESB100 directory:
/usr/sys/opt/ESB100:UNXDASH100:920310100739:DASH Systems:controlsys:100
1 2 3 4 5 6
The fields in this entry contain the following information:
1 The full pathname where the system configuration tools will find
extensions to input data. This location can contain files such as:
• Product-specific configuration files
• The config.file file fragment (contains keywords related only to
the product)
• The files file fragment (contains information about the location of
the product’s source code, when the product should be loaded into
the kernel, and whether source or binary code is provided)
• The stanza.static file (contains information about a static
driver’s major number requirements and the names and minor
numbers of the device special files)
• Object files
• Source code files
2 The setld subset identifier.
3 The date and time that the product is ready for distribution.
4 The name of the company that provided the subsystem.
5 The product name.
6 The setld 3-digit product version code.
Configuring the Kernel 5–29