NAME

insf − install special (device) files

SYNOPSIS

/sbin/insf

/sbin/insf [−C class | −d driver] [−D directory] [−e] [−H hw−path] [−I instance]
     [−n npty] [−q|−v] [−s nstrpty] [−p first−optical−disk:last−optical−disk]

DESCRIPTION

The insf command installs special files in the devices directory, normally /dev.  If required, insf creates any subdirectories that are defined for the resulting special file. 

If no options are specified, special files are created for all new devices in the system.  New devices are those devices for which no special files have been previously created.  A subset of the new devices can be selected with the −C, −d, and −H options. 

With the −e option, insf reinstalls the special files for pseudo-drivers and existing devices.  This is useful for restoring special files when one or more have been removed. 

Normally, insf displays a message as the special files are installed for each driver.  The −q (quiet) option suppresses the installation message.  The −v (verbose) option displays the installation message and the name of each special file as it is created. 

Options

insf recognizes the following options. 

−C class Match devices that belong to a given device class, class. Device classes can be listed with the lsdev command (see lsdev(1M)). They are defined in the files in the directory /usr/conf/master.d.  The special class pseudo includes all pseudo-drivers.  This option cannot be used with −d. 

−d driver Match devices that are controlled by the specified device driver, driver. Device drivers can be listed with the lsdev command (see lsdev(1M)). They are defined in the files in the directory /usr/conf/master.d.  This option cannot be used with −C. 

−D directory Override the default device installation directory /dev and install the special files in directory instead.  directory must exist; otherwise, insf displays an error message and exits.  See WARNINGS. 

−e Reinstall the special files for pseudo-drivers and existing devices.  This is useful for restoring special files if one or more have been removed. 

−H hw−path Match devices at a given hardware path, hw−path. Hardware paths can be listed with the ioscan command (see ioscan(1M)). A hardware path specifies the addresses of the hardware components leading to a device. It consists of a string of numbers separated by periods (.), such as 52 (a card), 52.3 (a target address), and 52.3.0 (a device).  If a hardware component is a bus converter, the following period, if any, is replaced by a slash (/) as in 2, 2/3, and 2/3.0. 

If the specified path contains fewer numbers than are necessary to reach a device, special files are made for all devices at addresses that extend the given path.  If the specified path is 56, then special files are made for the devices at addresses 56.0, 56.1, 56.2, etc. 

−I instance Match a device with the specified instance number.  Instances can be listed with the −f option of the ioscan command (see ioscan(1M)).

This option is effective only if the −e option is specified or if an appropriate device class or driver is specified with a −C or −d option. 

−n npty Install npty special files for each specified ptym and ptys driver.  The pty driver specifies both the ptym and ptys drivers.  npty is a decimal number. 

This option is effective only if the −e option is specified or if an appropriate device class or driver is specified with a −C or −d option. 

If this option is omitted, npty defaults to 60 for the ptym and ptys drivers. 

−p first−optical−disk:last−optical−disk
Install the special files for those optical disks located in slots in the range first−optical−disk to last−optical−disk. The two variables can have values from the set 1a, 1b, ..., 32a, 32b.  This option only applies to the autox0 and schgr drivers.  If it is omitted, the 64 special files for both sides of 32 optical disks (1a through 32b) will be installed. 

−q Quiet option.  Normally, insf displays a message as each driver is processed.  This option suppresses the driver message, but not error messages.  See the −v option. 

−s nstrpty Install nstrpty slave-side stream special files for the pts driver.  nstrpty is a decimal number.  This option only applies to the pts special file installation. 

This option is effective only if the −e option is specified or if an appropriate device class or driver is specified with a −C or −d option. 

If this option is omitted, nstrpty defaults to 60. 

−v Verbose option.  In addition to the normal processing message, display the name of each special file as it is created.  See the −q option. 

Naming Conventions

Many special files are named using the ccardttargetddevice naming convention.  These variables have the following meaning wherever they are used. 

card The unique interface card identification number from ioscan (see ioscan(1M)). It is represented as a decimal number with a typical range of 0 to 255.

target The device target number, for example the address on a HP-FL or SCSI bus.  It is represented as a decimal number with a typical range of 0 to 15. 

device A address unit within a device, for example, the unit in a HP-FL device or the LUN in a SCSI device.  It is represented as a decimal number with a typical range of 0 to 15. 

Special Files

This subsection shows which special files are created and the permissions for each device driver. 

The special file names are relative to the installation directory, normally /dev.  This directory may be overridden with the −D option. 

insf sets the file permissions and the owner and group IDs.  They are shown here in a format similar to that of the ll command:

special−file permissions owner group

For example:

tty rw−rw−rw− bin bin

Device Driver Special Files and Description

asio0 For each card instance, the following special files are installed:

ttycardp0 rw−−w−−w− bin bin
Direct connect

asyncdsk The following special file is installed:

asyncdsk rw−rw−rw− bin bin

audio The following special files are installed.  Note the underscore (_) before card in each special file name. 

For card 0, the device files are linked to files without the trailing _0 in their names. 

audio_card rw−rw−rw− bin bin
Default audio device

audioCtl_card rw−rw−rw− bin bin
Audio control device

audioBA_card rw−rw−rw− bin bin
All outputs, A-law format

audioBL_card rw−rw−rw− bin bin
All outputs, 16-bit linear format

audioBU_card rw−rw−rw− bin bin
All outputs, Mu-law format

audioEA_card rw−rw−rw− bin bin
External output, A-law format

audioEL_card rw−rw−rw− bin bin
External output, 16-bit linear format

audioEU_card rw−rw−rw− bin bin
External output, Mu-law format

audioIA_card rw−rw−rw− bin bin
Internal speaker output, A-law format

audioIL_card rw−rw−rw− bin bin
Internal speaker output, 16-bit linear format

audioIU_card rw−rw−rw− bin bin
Internal speaker output, Mu-law format

audioLA_card rw−rw−rw− bin bin
Line output, A-law format

audioLL_card rw−rw−rw− bin bin
Line output, 16 bit linear format

audioLU_card rw−rw−rw− bin bin
Line output, Mu-law format

audioNA_card rw−rw−rw− bin bin
No output, A-law format

audioNL_card rw−rw−rw− bin bin
No output, 16 bit linear format

audioNU_card rw−rw−rw− bin bin
No output, Mu-law format

autox0 schgr Special file names for autox0 and schgr use the format:

ccardttargetddevice_surface

surface: 1a through 32b, unless modified by the −p option.  Note the underscore (_) between device and surface.

For each autochanger device, the following special files are installed:

ac/ccardttargetddevice_surface rw−r−−−−− bin sys
Block entry

rac/ccardttargetddevice_surface rw−r−−−−− bin sys
Character entry

rac/ccardttargetddevice rw−−−−−−− bin sys
Character entry

beep The following special file is installed:

beep rw−rw−rw− bin bin

CentIf For each card instance, the following special file is installed. 

ccardttargetddevice_lp rw−rw−rw− lp bin
Handshake mode 2, character entry

cn The following special files are installed:

syscon rw−−w−−w− bin bin

systty rw−−w−−w− bin bin

console rw−−w−−w− root sys

ttyconf rw−−−−−−− root sys

cs80 disc1 disc2 disc3 disc4 sdisk
For each disk device, the following special files are installed:

dsk/ccardttargetddevice rw−r−−−−− bin sys
Block entry

rdsk/ccardttargetddevice rw−r−−−−− bin sys
Character entry

For disc1 and disc2 instances, the following additional special file is installed:

diag/rdsk/ccardttargetddevice rw−−−−−−− bin bin
Character entry

For cs80 and disc1 instances, the following additional special files are installed:

ct/ccardttargetddevice rw−r−−−−− bin sys
Block entry

rct/ccardttargetddevice rw−r−−−−− bin sys
Character entry

For disc1 instances, the following additional special file is installed:

diag/rct/ccardttargetddevice rw−−−−−−− bin bin
Character entry

For disc3 instances, the following additional special files are installed:

floppy/ccardttargetddevice rw−r−−−−− bin sys
Block entry

rfloppy/ccardttargetddevice rw−r−−−−− bin sys
Character entry

devconfig The following special file is installed:

config rw−r−−−−− root sys

diag0 The following special file is installed:

diag/diag0 rw−−−−−−− bin bin

diag1 The following special file is installed:

diag/diag1 rw−−−−−−− bin bin

diag2 The following special files are installed:

diag2 rw−−−−−−− bin bin

diag/diag2 rw−−−−−−− bin bin

diaghpib1 For each device, the following special files are installed:

diag/hpib/hp28650A/instance rw−−−−−−− bin bin

disc1 disc2 disc3 disc4
See cs80. 

dlpi The following special files are installed:

dlpi rw−rw−rw− root sys

dlpi0 rw−rw−rw− root sys

dlpi1 rw−rw−rw− root sys

dlpi2 rw−rw−rw− root sys

dlpi3 rw−rw−rw− root sys

dlpi4 rw−rw−rw− root sys

dmem The following special file is installed:

dmem rw−−−−−−− bin bin

echo The following special file is installed:

echo rw−rw−rw− root sys

eisa_mux0 For each instance of an eisa_mux card, the following special files are installed:

ttycardletterport rw−−w−−w− bin bin
letter: a to p, module index
port: 1 to 16, direct connect

muxcard rw−−−−−−− bin bin

diag/muxcard rw−−−−−−− bin bin

diag/muxcard_1 rw−−−−−−− bin bin

diag/muxcard_2 rw−−−−−−− bin bin

fddi The following special file is installed:

lancard rw−rw−rw− bin bin

framebuf For each graphics device, the following special files are installed. 

crtdevice_number rw−rw−rw− bin bin

ocrtdevice_number rw−rw−rw− bin bin

device_number is 0 indexed and is assigned in the order in which the devices appear in ioscan(1m) output. 

If the console device is a graphics device, the files crt and ocrt are created as the console device.  If the console is not a graphics device, crt and ocrt are identical to crt0 and ocrt0. 

hil For each device, the following special files are installed.  Note the underscore (_) before card in each special file name. 

For card 0, the device files are linked to files named hiladdr for the link addresses 1 to 7; hilkbd for the cooked keyboard device; and rhil for the hil controller device. 

hil_card.addr rw−rw−rw− bin bin
addr: link addresses 1 to 7

hilkbd_card rw−rw−rw− bin bin

rhil_card rw−rw−rw− bin bin

inet_clts The following special file is installed:

inet_clts rw−rw−rw− root sys

inet_cots The following special file is installed:

inet_cots rw−rw−rw− root sys

instr0 For each card instance, the following special files are installed:

hpib/ccard rw−rw−rw− bin bin

hpib/ccardtaddrd0 rw−rw−rw− bin bin
addr: 0 to 30

diag/hpib/ccard rw−−−−−−− bin bin

kepd The following special file is installed:

kepd rw−r−−r−− root other

klog The following special file is installed:

klog rw−−−−−−− bin bin

lan0 lan1 lan2 lan3
For each card instance, the following special files are installed:

lancard rw−rw−rw− bin bin

ethercard rw−rw−rw− bin bin

diag/lancard rw−−−−−−− bin bin

lantty0 For each card instance, the following special files are installed:

lanttycard rw−rw−rw− bin bin
Normal access

diag/lanttycard rw−rw−rw− bin bin
Exclusive access

lpr0 lpr1 lpr2 lpr3
For each card instance, the following special files are installed:

ccardttargetddevice_lp rw−−−−−−− lp bin

diag/ccardttargetddevice_lp rw−−−−−−− bin bin

mm The following special files are installed:

mem rw−r−−−−− bin sys
Minor 0

kmem rw−r−−−−− bin sys
Minor 1

null rw−rw−rw− bin bin
Minor 2

mux0 For each instance of a 6-channel card, the following special files are installed:

ttycardpport rw−−w−−w− bin bin
port: 0 to 5, direct connect

muxcard rw−−−−−−− bin bin

diag/muxcard rw−−−−−−− bin bin

For each instance of a 16-channel card, the following special files are installed:

ttycardpport rw−−w−−w− bin bin
port: 0 to 15, direct connect

muxcard rw−−−−−−− bin bin

diag/muxcard rw−−−−−−− bin bin

mux2 For each instance of an 16-channel card, the following special files are installed:

ttycardpport rw−−w−−w− bin bin
port: 0 to 15, direct connect

muxcard rw−−−−−−− bin bin

diag/muxcard rw−−−−−−− bin bin

For each card instance of an 8-channel card, the following special files are installed:

ttycardpport rw−−w−−w− bin bin
port: 0 to 7, direct connect

muxcard rw−−−−−−− bin bin

diag/muxcard rw−−−−−−− bin bin

For each card instance of an 3-channel card, the following special files are installed:

ttycardpport rw−−w−−w− bin bin
port: 0, 1, and 7, direct connect

muxcard rw−−−−−−− bin bin

diag/muxcard rw−−−−−−− bin bin

mux4 For each card instance, the following special files are installed:

ttycardpport rw−−w−−w− bin bin
port: 0 and 1, direct connect

pflop sflop For each card instance, the following special files are installed:

floppy/ccardttargetddevice rw−r−−−−− bin sys
Block entry

rfloppy/ccardttargetddevice rw−r−−−−− bin sys
Character entry

ps2 The following special files are installed:

ps2kbd rw−rw−rw− bin bin
Autosearch for first ps2 keyboard

ps2mouse rw−rw−rw− bin bin
Autosearch for first ps2 mouse

ps2_0 rw−rw−rw− bin bin
ps2 port 0

ps2_1 rw−rw−rw− bin bin
ps2 port 1

ptm The following special file is installed:

ptmx rw−rw−rw− root sys

pts The following special files are installed:

pts/number rw−rw−rw− root sys
number: 0 to 59

pty Specifying this driver tells insf to install the special files for both the master and slave pty drivers, ptym and ptys.  The command insf -d pty is equivalent to the two commands insf -d ptym; insf -d ptys. 

ptym The following special files are installed:

ptym/clone rw−r−−r−− root other

ptym/ptyindexnumber rw−rw−rw− bin bin
index: p to z, a to c, e to o; number: 0 to f (hexadecimal)

The first 48 special files ptym/pty* are linked to pty*. 

ptym/ptyindexnumber rw−rw−rw− bin bin
index: p to z, a to c, e to o; number: 00 to 99

ptym/ptyindexnumber rw−rw−rw− bin bin
index: p to z, a to c, e to o; number: 000 to 999

ptys The following special files are installed:

pty/ttyindexnumber rw−rw−rw− bin bin
index: p to z, a to c, e to o; number: 0 to f (hexadecimal)

The first 48 special files pty/tty* are linked to tty*. 

pty/ttyindexnumber rw−rw−rw− bin bin
index: p to z, a to c, e to o; number: 00 to 99

pty/ttyindexnumber rw−rw−rw− bin bin
index: p to z, a to c, e to o; number: 000 to 999

root The following special files are installed:

root rw−r−−−−− bin sys

rroot rw−r−−−−− bin sys

sad The following special file is installed:

sad rw−rw−rw− root sys

schgr See autox0. 

sdisk See cs80. 

sflop See pflop. 

stape tape1 tape2
For each driver instance, different special files are installed depending on the number of characters allowed in the target directory. There are two lists below, one for long file name directories and one for short file name directories (14 characters maximum). Short file names are used for files installed on an NFS file system.

Note that the first four special files in each list for tape driver instances 0-9 are also linked to rmt/instancem, rmt/instancemb, rmt/instancemn, and rmt/instancemnb, respectively. 

For installation in a long file name directory:

rmt/ccardttargetddeviceBEST rw−rw−rw− bin bin
AT&T-style, best available density, character entry

rmt/ccardttargetddeviceBESTb rw−rw−rw− bin bin
Berkeley-style, best available density, character entry

rmt/ccardttargetddeviceBESTn rw−rw−rw− bin bin
AT&T-style, no rewind, best available density, character entry

rmt/ccardttargetddeviceBESTnb rw−rw−rw− bin bin
Berkeley-style, no rewind, best available density, character entry

For installation in a short file name directory:

rmt/ccardttargetddevicef0 rw−rw−rw− bin bin
AT&T-style, best available density, character entry

rmt/ccardttargetddevicef0b rw−rw−rw− bin bin
Berkeley-style, best available density, character entry

rmt/ccardttargetddevicef0n rw−rw−rw− bin bin
AT&T-style, no rewind, best available density, character entry

rmt/ccardttargetddevicef0nb rw−rw−rw− bin bin
Berkeley-style, no rewind, best available density, character entry

For both long and short file name directories, the following additional files are created. 

rmt/driver_name_config rw−r−−r−− bin bin
Tape configuration, character entry

diag/rmt/ccardttargetddevice rw−−−−−−− bin bin
For tape1 and tape2 only, diagnostic access, character entry

strlog The following special file is installed:

strlog rw−rw−rw− root sys

sy The following special file is installed:

tty rw−rw−rw− bin bin

tape1 tape2 See stape. 

token2 The following special file is installed:

lancard rw−rw−rw− bin bin

unix_clts The following special file is installed:

unix_clts rw−rw−rw− root sys

unix_cots The following special file is installed:

unix_cots rw−rw−rw− root sys

RETURN VALUE

insf exits with one of the following values:

0 Successful completion, including warning diagnostics. 

1 Failure. 

DIAGNOSTICS

Most diagnostic messages from insf are self-explanatory.  Listed below are some messages deserving further clarification. 

Warnings

Device driver name is not in the kernel
Device class name is not in the kernel

The indicated device driver or device class is not present in the kernel.  A device driver and/or device class can be added to the kernel using config(1M).

No instance number available for device class name

All of the instance numbers available for the device class are already assigned.  Use the rmsf command to remove any unneeded devices from the system (see rmsf(1M)).

Don’t know how to handle driver name − no special files created for path

insf does not know how to create special files for the specified device driver.  Use mknod to create special files for the device (see mknod(1M)).

EXAMPLES

Install special files for all new devices belonging to the tty device class:

insf −C tty

Install special files to the new device added at hardware path 2/4.0.0:

insf −H 2/4.0.0

WARNINGS

insf should only be run in single-user mode.  It can change the mode, owner, or group of an existing special file, or unlink and recreate one; special files that are currently open may be left in an indeterminate state. 

Many commands and subsystems assume their device files are in /dev, therefore the use of the −D option is discouraged. 

AUTHOR

insf was developed by HP. 

FILES

/dev/config I/O system special file

/etc/ioconfig I/O system configuration database

SEE ALSO

config(1M), ioscan(1M), lsdev(1M), lssf(1M), mknod(1M), mksf(1M), rmsf(1M). 

Hewlett-Packard Company  —  HP-UX Release 10.20:  July 1996