insf.1m (2010 09)

i
insf(1M) insf(1M)
pts/tnumber rw-rw-rw- root sys
number: 0 to 59
tlclts
The following special file is installed:
tlclts rw-rw-rw- root sys
tlcots
The following special file is installed:
tlcots rw-rw-rw- root sys
tlcotsod
The following special file is installed:
tlcotsod rw-rw-rw- root sys
token2
The following special file is installed:
lancard rw-rw-rw- bin bin
udp The following special file is installed:
udp rw-rw-rw- root sys
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 dev-
ice class can be added to the kernel using kcmodule.
No instance number available for device class name
All of the instance numbers available for the device class are already assigned. Use the
rmsf com-
mand 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
disk device class claimed by sdisk driver:
insf -C disk
Install special files to the new device added at hardware path 2/4.0.0:
insf -H 2/4.0.0
Install persistent special files to the new device added at the hardware path 64000/0xfa00/0x3:
HP-UX 11i Version 3: September 2010 − 11 − Hewlett-Packard Company 11