 |
» |
|
|
|
NAMEinsf — 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] /sbin/insf
-L
[-v] DESCRIPTIONThe
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.
Both the legacy and persistent device special files (see
intro(7))
are created, unless specified. 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. With the
-L
option,
insf
enables the legacy naming model.
If the
-v
option is included,
insf
also displays the current mode, legacy, or agile without changing
the current mode. Optionsinsf
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.
In the agile view (see
intro(7)),
the devices will have new hardware path formats,
which can be displayed using the
ioscan
command with
-N
option (see
ioscan(1M)). - -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. - -L
Enable the legacy naming model.
This command reinstalls the legacy I/O nodes and legacy device special
files which might have been removed with
rmsf -L
(see
rmsf(1M)).
When used with the
-v
option,
insf
reports on whether legacy mode is enabled or disabled. - -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. - -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 ConventionsSome special files follow a
classinstance
naming convention, where class is the driver class,
and instance is the instance number assigned
by the operating system to the device. Many other 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. - 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 FilesThis subsection shows which special files are created
and the permissions for each of the supported device drivers. 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:
Device Driver Special Files and Description- arp
The following special file is installed:
- asio0
For the built-in serial port, the following special files are installed for
each card instance:
- ttycardp0
rw--w--w- bin bin Direct connect
- asio0
For the SAS console ports, the following special files are installed for
each card instance:
- ttycardp0
rw--w--w- bin bin local console port (direct connect) - ttycardp1
rw--w--w- bin bin remote session port (direct connect) - sassy
rw------- root sys internal console port (direct connect) - ttycard+1p0
rw--w--w- bin bin UPS port (direct connect) - ttycard+1p1
rw--w--w- bin bin local session port (direct connect)
- asyncdsk
The following special files are installed:
- asyncdsk
rw-rw-rw- bin bin - async
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
- beep
The following special file is installed:
- CentIf
For each card instance, the following special file is installed.
- ccardttargetddevice_lp
rw-rw-rw- lp bin Handshake mode 2, character entry
- consp1
For each card instance, the following special files are installed:
- ttycardp0
rw--w--w- bin bin Direct connect
- 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
- c8xx
The following persistent special file is installed:
- c8xxinstance
crw-rw-rw- bin sys
- dev_config
The following special file is installed:
- 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
- disc3 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 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
For disk instances that are partitioned, the following additional special files are installed:
- dsk/ccardttargetddevicespartition
rw-r----- bin sys Block entry - rdsk/ccardttargetddevicespartition
rw-r----- bin sys Character entry
- 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:
- echo
The following special file is installed:
- eschgr
The following persistent special file is installed:
- rchgr/autochinstance
rw-r----- bin sys
- esctl
The following persistent special file is installed:
- pt/ptinstance
rw-r----- bin bin
- esdisk
For each driver instances of
esdisk,
the following persistent special
files are installed:
- disk/diskinstance
rw-r----- bin sys Block entry - rdisk/diskinstance
rw-r----- bin sys Character entry
For disk instances that are partitioned, the following additional
persistent special files are installed:
- disk/diskinstance_ppartition
rw-r----- bin sys Block entry - rdisk/diskinstance_ppartition
rw-r----- bin sys Character entry
- estape
For each driver instances of
estape,
the following persistent special
files are installed:
- rtape/tapeinstance_BEST
rw-rw-rw- bin bin Character entry - rtape/tapeinstance_BESTb
rw-rw-rw- bin bin Character entry - rtape/tapeinstance_BESTn
rw-rw-rw- bin bin Character entry - rtape/tapeinstance_BEST_nb
rw-rw-rw- bin bin Character entry
- fddi
The following special file is installed:
- 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
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
- ip
The following special file is installed:
- kepd
The following special file is installed:
- klog
The following special file is installed:
- 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
- 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
- mpt
The following persistent special files are installed:
- mptinstance
crw-rw-rw- bin sys
- 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
- netqa
The following special file is installed:
- nuls
The following special file is installed:
- pci_mux0 pci_mux1
For each instance of a PCI mux card,
the following "Direct Connect" special files are created.
The term
card
below refers to the instance number of the mux card.
- ttycardport_module port
rw--w--w- bin bin port_module:
a
to
p,
port module name port:
1
to
16,
port number - muxcard
rw------- bin bin - diag/muxcard
rw------- bin bin - diag/muxcard_1
rw------- bin bin - diag/muxcard_2
rw------- bin bin
- 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:
- 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
and
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
s,
u
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
s,
u
to
z,
a
to
c,
e
to
o;
number:
00
to
99 - ptym/ptyindexnumber
rw-rw-rw- bin bin index:
p
to
s,
u
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
s,
u
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
s,
u
to
z,
a
to
c,
e
to
o;
number:
00
to
99 - pty/ttyindexnumber
rw-rw-rw- bin bin index:
p
to
s,
u
to
z,
a
to
c,
e
to
o;
number:
000
to
999
- rawip
The following special file is installed:
- root
The following special files are installed:
- root
rw-r----- bin sys - rroot
rw-r----- bin sys
- sad
The following special file is installed:
- sastty
For each card instance, the following special files are installed:
- ttycardpport
rw--w--w- bin bin port:
0
to
1,
direct connect
- schgr
Special file names for
schgr
use the format: ccardttargetddevice For each autochanger device,
the following special file is installed:
- rac/ccardttargetddevice
rw------- bin sys Character entry
- sctl
The following special files are installed:
- rscsi/ccardttargetddevice
rw-r----- bin sys Character entry
- sdisk
See
disc3. - sflop
See
pflop. - side
The following persistent special file is installed:
- sideinstance
crw-rw-rw- bin sys
- stape 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). 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
tape2
only,
diagnostic access, character entry
- stcpmap
The following special file is installed:
- stcpmap
rw-rw-rw- root sys
- strlog
The following special file is installed:
- sy
The following special file is installed:
- tape2
See
stape. - tcp
The following special file is installed:
- td
The following persistent special files are installed:
- tdinstance
crw-rw-rw- bin sys
- telm
The following special file is installed:
- telnetm
rw-rw-rw- root sys
- tels
The following special files are installed:
- pts/tnumber
rw-rw-rw- root sys number:
0
to
59
- tlclts
The following special file is installed:
- tlcots
The following special file is installed:
- tlcotsod
The following special file is installed:
- tlcotsod
rw-rw-rw- root sys
- token2
The following special file is installed:
- udp
The following special file is installed:
- 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 VALUEinsf
exits with one of the following values:
- 0
Successful completion, including warning diagnostics. - 1
Failure.
DIAGNOSTICSMost diagnostic messages from
insf
are self-explanatory.
Listed below are some messages deserving further clarification. WarningsDevice 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
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
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)).
EXAMPLESInstall special files for all new devices belonging to the
disk
device class claimed by
sdisk
driver:
Install special files to the new device added at hardware path
2/4.0.0:
Install persistent special files to the new device added at the
hardware path
64000/0xfa00/0x3:
Reinstall persistent special files for all the devices belonging to the
esdisk
device driver:
Enable legacy mode (reinstalls all legacy I/O nodes and
legacy device special files):
Find out if legacy mode is enabled or disabled:
WARNINGSinsf
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. Hence
insf
is recommended to be run in single-user mode. Many commands and subsystems assume their device
files are in
/dev,
therefore the use of the
-D
option is discouraged. AUTHORinsf
was developed by HP. FILES- /dev/config
I/O system special file - /etc/ioconfig
I/O system configuration database - /etc/ext_ioconfig
I/O system configuration database
|
Printable version
