system initialization procedures
Syntax
letdbcheckrc [ -a ] letdbrc
Description
See also
brc - clears mounted filesystem table and adds entry for root filesystem bcheckrc - checks root filesystem
These shell procedures are executed via entries in /etc/inittab by init(M) when-ever the system is booted (or rebooted).
First, the bcheckrc procedure checks the status of the root filesystem. If the root filesystem is found to be bad, bcheckrc repairs it. When invoked with the -a (autoboot) flag, bcheckrc will run without operator intervention. init calls bcheckrc with the -a flag when the system autoboots.
Then, the brc procedure clears the mounted filesystem table, /etc/mnttab, and puts the entry for the root filesystem into the mount table.
After these two procedures have executed, init checks for the "initdefault"
value in /etc/inittab. This tells init in which run-level to place the system.
Since "initdefault" is initially set to 2, the system will be placed in the multi-user state via the letdrc2 procedure.
Note that bcheckrc should always be executed before brc. Also, these shell procedures may be used for several run-level states.
boot(HW), fsck(ADM), init(M), rc2(ADM), shutdown(ADM)
btldinstall(ADM)
btldinstall
install boot-time loadable device drivers into the Link Kit
Syntax
letdbtldinstall mount_dir
Description
This command asks the user which packages on a boot-time loadable device driver diskette (the btld(F) diskette) are to be installed, and then adds the appropriate drivers to the Link Kit. A "package" is a directory hierarchy which contains one or more drivers, and associated files.
mount_dir is expected to be the root directory of a mounted btld diskette.
btldinstall is typically run by a Bourne shell (sh(C» script (/installlINSTALL) which is always present on a btld diskette. linstalllINSTALL is itself run au-tomatically by installpkg(ADM).
btldinstall performs the following actions, in order:
a) Ensure the Link Kit is installed. If it is not, the user is asked whether to install it using custom(ADM), or to abandon the installation of boot-time drivers.
b) Asks the user which boot-time loadable device driver packages to install. The default behavior is that btldinstall installs all the packages on the btld diskette which are also in the package string (see string(M».
Then once per required package:
c) If the Bourne shell script Ipkglinstaillcopyright exists and is executable it is run.
d) If the Bourne shell script Ipkglinstalllpreinstall exists it is run as though it were part of btldinstaH.
e) The list of drivers in /pkg/install/drivers is checked to determine if a driver with the same name already exists in the Link Kit. The user is asked to resolve this conflict, either by replacing the driver in the Link Kit or by choosing not to install the boot-time loadable driver.
£) The drivers are installed with idinstall(ADM).
g) If the hierarchy /pkg/new exists, it is copied to the hard disk as if it were
/I
I".
h) If the file /pkg/install/pkg.name exists it is copied to /usr/options/pkg.name.
i) If the Bourne shell script Ipkglinstalllpostinstall exists it is run as though it were part of btldinstall.
btldinstall(ADM)
See also Notes
The following environment variables are available for use in scripts run by btldinstall:
$pkg The current package being installed.
$pkginst All packages to be installed.
$okdrivers All drivers to be installed for this package.
boot(HW), btld(F), idinstall(ADM), installpkg(ADM), string(M)
If an error occurs during the installation, btldinstall unwinds changes to the Link Kit to leave it in a working state.
Value added
letclbtldinstall is an extension of AT&T System V provided by The Santa Cruz Operation, Inc.
captoinjo( ADM)
captoinfo
convert a termcap description into a terminfo description
Syntax
one found, an equivalent terminfo{F) description is written to standard output, along with any comments found. A description which is expressed as relative to another description (as specified in the TERMCAP "tC=" field) will be reduced to the minimum superset before being output.If no file is given, then the environment variable TERMCAP is used for the file name or entry. If TERMCAP is a full pathname to a file, only the terminal whose name is specified in the environment variable TERM is extracted from that file. If the environment variable TERMCAP is not set, then the file /etc/termcap is read.
-v print out tracing information on standard error as the program runs.
Specifying additional -v options will cause more detailed information to be printed.
-v
print out the version of the program in use on standard error and exit.-1 cause the fields to print out, one to a line. Otherwise, the fields will be printed several to a line, up to a maximum width of 60 characters.
-w change the output to width characters.
/usr/lib/terminfo/?
/*
compiled terminal description databaseCertain termcap defaults are assumed to be true. For example, the bell charac-ter (terminfo bel) is assumed to be AG. The linefeed capability (termcap nl) is assumed to be the same for both cursor_down and scroll_forward (terminfo cud1 and ind, respectively). Padding information is assumed to belong at the end of the string.
The algorithm used to expand parameterized information for termcap fields such as cursor_position (termcap em, terminfo cup) will sometimes produce a string which, though technically correct, may not be optimal. In particular, the rarely used termcap operation %n will produce strings that are especially long. Most occurrences of these non-optimal strings will be flagged with a warning message and may need to be recoded by hand.
The short two-letter name at the beginning of the list of names in a termcap entry, present for backwards compatibility, has been removed.