insf(1M) — Series 800 Only
NAME
insf − install special files
SYNOPSIS
/etc/insf
/etc/insf [−N cnode] [−d driver] [−C class] [−H hw_path] [−l lu] [−f] [−k|−e] [−n npty]
[−p first_cartridge:last_cartridge]
DESCRIPTION
insf installs special files in the current directory and assigns logical unit numbers to devices in the system. If no options are specified, special files are created for all new devices in the system. New devices are those devices that have not previously been assigned a logical unit number (i.e., lu). A subset of the new devices can be selected with the −d, −C, and −H options.
For each new device in the system, insf assigns the next available logical unit number for the device class. The −l option may be used to explicitly specify the lu. If insf is invoked with the −l option, the subsetting must be sufficient to identify a unique device in the system. In addition, if the specified lu has already been assigned to another device in the device class, insf fails unless the −f option is specified. The −f option forces the lu to map to the specified device; any previous mapping of this lu to another device is lost.
If the −k option is specified, insf assigns logical unit numbers without creating special files. Combining the −l, −f, and −k options allows the user to force an existing lu and the corresponding set of special files to map to a different device. This is useful when moving devices around in the system.
If the −e option is specified, insf reinstalls device files for pseudo-drivers and existing devices; that is, devices which have associated logical unit numbers. This option can be used to restore device files in case one or more have been removed.
The −N option specifies that the special files are to be created with the associated cnode id; the format of cnode is the same as that given in mknod(1M). If −N is not specified, insf uses the cnode id of the machine on which it is executing.
The −n option only applies to pty special file installation, that is, drivers pty0 and pty1. If it is given, only npty pty special files for each driver will be installed; if it is omitted, 48 pty special files will be installed.
The −p option only applies to autochanger special file installation, that is, the driver autox0. If it is given, only special files for those cartridges located in the slots ranging from first_cartridge to last_cartridge will be installed; if it is omitted, special files for 32 cartridges (1 - 32) will be installed (2048 special files in all).
After assigning logical unit numbers and installing special files, insf updates the /etc/ioconfig file. If /etc/ioconfig is not present, insf will create it.
Options
−C class Match devices that belong to a given device class. Device classes are defined in the /etc/master file and can be listed using lsdev(1M). The special class “pseudo” includes all pseudo-drivers. Cannot be used with −d.
−H hw_path Match devices at a given hw_path. A hardware path specifies the address of the hardware components leading to a device. It consists of a string of numbers each suffixed by slash, ‘/’, followed by an arbitrary length string of numbers separated by periods, ‘.’. Hardware components suffixed by slashes indicate bus converters and may not be necessary on your machine. Hardware components suffixed by ‘.’ indicate the addresses of the remaining hardware components on the path to a device. If the hardware path contains fewer numbers than is necessary to reach a device, special files will be made for all devices connected to the hardware component corresponding to the last number specified.
−N cnode Install special files with the specified cnode id; the format of cnode is the same as that given in mknod(1M).
−d driver Match devices that are controlled by the specified device driver. Device drivers are defined in the /etc/master file and can be listed using lsdev(1M). Cannot be used with −C.
−e Reinstall special files for existing devices; that is, devices which have associated logical units. Cannot be used with −k.
−f Force the lu specified in the −l option to map to a specific new device; any previous mapping of the lu to another device in the device class is lost.
−k Assign logical unit numbers without creating special files. Cannot be used with −e.
−l lu Assign the specified lu to a single new device in the system.
−n npty Install npty pty special files. This option only applies to pty0 and pty1 special file installation.
−p first_cartridge:last_cartridge
Install special files for those cartridges located in the range first_cartridge to second_cartridge. This option only applies to autox0 special file installation.
Naming Conventions
The following section shows which special files are created and their permissions for each device driver. The file permissions are set by insf. Unless otherwise noted, the owner and group ID are set to bin.
autox0 Special file names for autox0 use the following format: c<lu>s<section>d<surface>. For each logical unit, the following special files are installed:
ac/c<lu>s<section>d<surface>
sections 0 to 15, surfaces 1a to 32b unless otherwise noted by the −p option, group sys, block entry, rw- r-- ---
rac/c<lu>s<section>d<surface>
sections 0 to 15, surfaces 1a to 32b unless otherwise noted by the −p option, group sys, character entry, rw- r-- ---
rac/ioctl<lu>
character entry, rw- --- ---
cn syscon rw- -w- -w-
systty rw- -w- -w-
console rw- -w- -w-
devconfig config owner root, group sys, rw- r-- ---
diag0 diag0 rw- --- ---
diaghpib1 For each logical unit, the following special files are installed:
diag/hpib/hp28650A/<lu> rw- --- ---
disc1 Special file names for disc1 use the following format: c<lu>d<unit>s<section>. For each logical unit, the following special files are installed:
dsk/c<lu>d0s<section>
sections 0 to 15, group sys, block entry, rw- r-- ---
rdsk/c<lu>d0s<section>
sections 0 to 15, group sys, character entry, rw- r-- ---
ct/c<lu>d<unit>s2
units 0 and 1, block entry, rw- rw- rw-
rct/c<lu>d<unit>s2
units 0 and 1, character entry, rw- rw- rw-
diag/dsk/c<lu>d<unit>
units 0 and 1, character entry, rw- --- ---
disc2 Special file names for disc2 use the following format: c<lu>d<unit>s<section>. For each logical unit, the following special files are installed:
dsk/c<lu>d0s<section>
sections 0 to 15, group sys, block entry, rw- r-- ---
rdsk/c<lu>d0s<section>
sections 0 to 15, group sys, character entry, rw- r-- ---
diag/dsk/c<lu>d0
character entry, rw- --- ---
disc3 Special file names for disc3 use the following format: c<lu>d0s<section>. For each logical unit, the following special files are installed:
dsk/c<lu>d0s<section>
sections 0 to 15, group sys, block entry, rw- r-- ---
rdsk/c<lu>d0s<section>
sections 0 to 15, group sys, character entry, rw- r-- ---
display0 For each logical unit, the following special files are installed:
crt<lu> rw- rw- rw-
hilkbd<lu> rw- rw- rw-
hil_<lu>.<addr>
link addresses 1 to 7, rw- rw- rw-
ttyi<lu> rw- -w- -w-
diag/crt<lu> rw- --- ---
dmem dmem rw- --- ---
gpio0/gpio1 For each logical unit, the following special files are installed:
gpio<lu> rw- rw- rw-
diag/gpio<lu> rw- --- ---
instr0 For each logical unit, the following special files are installed:
hpib/<lu> rw- rw- rw-
hpib/<lu>a<addr>
addrs 0 to 30, rw- rw- rw-
diag/hpib/<lu> rw- --- ---
lan0/lan1 For each logical unit, the following special files are installed:
lan<lu> rw- rw- rw-
ether<lu> rw- rw- rw-
diag/lan<lu> rw- --- ---
lpr0/lpr1/lpr2 For each logical unit, the following special files are installed:
lp<lu> owner lp, rw- --- ---
diag/lp<lu> rw- --- ---
meas_drivr meas_drivr rw- rw- rw-
mirconfig rdsk/mirconfig rw- rw- rw-
mm The following special files are installed:
kmem minor 1, group sys, rw- r-- ---
mem minor 0, group sys, rw- r-- ---
null minor 2, rw- rw- rw-
mux0 For each logical unit, the following special files are installed:
tty<lu>p<port>
ports 0 to 5, direct connect, rw- -w- -w-
mux<lu> rw- --- ---
diag/mux<lu> rw- --- ---
mux0_16 For each logical unit, the following special files are installed:
tty<lu>p<port>
ports 0 to 15, direct connect, rw- -w- -w-
mux<lu> rw- --- ---
diag/mux<lu> rw- --- ---
mux2 For each logical unit, the following special files are installed:
tty<lu>p<port>
ports 0 to 7, direct connect, rw- -w- -w-
mux<lu> rw- --- ---
diag/mux<lu> rw- --- ---
pty0 pty<index><number>
indices ‘p’ to ‘r’, numbers 0 to f (hexadecimal), rw- rw- rw-
ptym/pty<index><number>
indices ‘a’ to ‘c’ and ‘e’ to ‘z’, numbers 0 to f (hexadecimal), rw- rw- rw-
ptym/pty<index><number>
indices ‘a’ to ‘c’ and ‘e’ to ‘z’, numbers 00 to 99, rw- rw- rw-
The special files pty* are linked to ptym/pty*.
pty1 tty<indexR><number>
indices ‘p’ to ‘r’, numbers 0 to f (hexadecimal), rw- rw- rw-
pty/tty<indexR><number>
indices ‘a’ to ‘c’ and ‘e’ to ‘z’, numbers 0 to f (hexadecimal), rw- rw- rw-
pty/tty<indexR><number>
indices ‘a’ to ‘c’ and ‘e’ to ‘z’, numbers 00 to 99, rw- rw- rw-
The special files tty* are linked to pty/tty*.
scc1 tty<port>
ports ‘a’ and ‘b’, direct connect, rw- -w- -w-
sy tty rw- rw- rw-
tape1/tape2 For each logical unit, the following special files are installed:
mt/<lu>l
800 bpi, block entry, rw- rw- rw-
mt/<lu>m
1600 bpi, block entry, rw- rw- rw-
mt/<lu>h
6250 bpi, block entry, rw- rw- rw-
mt/<lu>ln
no rewind, 800 bpi, block entry, rw- rw- rw-
mt/<lu>mn
no rewind, 1600 bpi, block entry, rw- rw- rw-
mt/<lu>hn
no rewind, 6250 bpi, block entry, rw- rw- rw-
rmt/<lu>l
800 bpi, character entry, rw- rw- rw-
rmt/<lu>m
1600 bpi, character entry, rw- rw- rw-
rmt/<lu>h
6250 bpi, character entry, rw- rw- rw-
rmt/<lu>hc
6250 bpi, compressed, character entry, rw- rw- rw-
rmt/<lu>ln
no rewind, 800 bpi, character entry, rw- rw- rw-
rmt/<lu>mn
no rewind, 1600 bpi, character entry, rw- rw- rw-
rmt/<lu>hn
no rewind, 6250 bpi, character entry, rw- rw- rw-
diag/mt/<lu>
character entry, rw- --- ---
RETURN VALUE
insf returns 0 upon normal completion and 1 if an error occurred. Warnings result in an exit code of 0, since these are not considered catastrophic.
DIAGNOSTICS
Most of the diagnostic messages from insf are self explanatory. Listed below are some messages deserving further clarification. Errors cause insf to halt immediately while warnings allow the program to continue.
Errors
Lu <lu> already assigned to <driver> at <path>
The lu specified with the −l option is already assigned to another device in the device class. The −f option can be used to force the lu to map to the new device.
Matched more than one new device
A logical unit was explicitly specified with the −l option and insf was unable to match a unique new device. Use some combination of the −d, −C, and −H options to select a unique device in the system.
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 uxgen(1M).
No logical units available for device class <name>
All of the logical units available for the device class are already assigned. Use rmsf(1M) to remove any unneeded devices from the system.
Don’t know how to handle driver <name> − no special files created for <path>
The insf command does not know how to create special files for the specified device driver. A logical unit number is assigned to the device. To create special files for the device use mksf(1M).
EXAMPLES
insf −C tty
Install special files and assign logical units for all new devices belonging to the tty device class.
insf −H 2/4.0.0
Install special files and assign logical unit numbers to the new device added at hardware path 2/4.0.0.
WARNINGS
insf should only be run in single-user mode. It may 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.
AUTHOR
insf was developed by HP.
FILES
/dev/config
/etc/ioconfig
SEE ALSO
lsdev(1M), lssf(1M), mksf(1M), mknod(1M), rmsf(1M), uxgen(1M), ioconfig(4).
Hewlett-Packard Company — HP-UX Release 8.05: June 1991