devfsadm(1M)

NAME

     devfsadm, devfsadmd - administration command  for  /dev  and
     /devices

SYNOPSIS

     /usr/sbin/devfsadm [-C] [-c device_class] [-i driver_name] [
     -n] [-r root_dir] [-s] [-t table_file] [-v]

     /usr/lib/devfsadm/devfsadmd

DESCRIPTION

     devfsadm(1M) maintains the /dev and /devices namespaces.  It
     replaces  the  previous  suite of devfs administration tools
     including drvconfig(1M),  disks(1M),  tapes(1M),  ports(1M),
     audlinks(1M), and devlinks(1M).

     The default operation is to attempt to load every driver  in
     the  system  and  attach  to  all possible device instances.
     devfsadm then creates device special files in  /devices  and
     logical links in /dev.

     devfsadmd(1M) is the daemon  version  of  devfsadm(1M).  The
     daemon  is  started  by  the  /etc/rc* scripts during system
     startup and is responsible for handling both reconfiguration
     boot  processing  and updating /dev and /devices in response
     to dynamic reconfiguration event notifications from the ker-
     nel.

     For  compatibility   purposes,   drvconfig(1M),   disks(1M),
     tapes(1M),  ports(1M),  audlinks(1M),  and  devlinks(1M) are
     implemented as links to devfsadm.

     In addition to managing /dev  and  /devices,  devfsadm  also
     maintains the path_to_inst(4) database.

OPTIONS

     The following options are supported:

     -C     Cleanup mode. Prompt  devfsadm  to  cleanup  dangling
           /dev  links  that  are not normally removed. If the -c
           option is also used, devfsadm only cleans up  for  the
           listed devices' classes.

     -c device_class
           Restrict operations to devices of class  device_class.
           Solaris defines the following values for device_class:
           disk, tape, port, audio, and pseudo. This  option  may
           be specified more than once to specify multiple device
           classes.

     -i driver_name
           Configure only  the  devices  for  the  named  driver,
           driver_name.

     -n    Do not attempt to load drivers or add new nodes to the
           kernel device tree.

     -s    Suppress any changes to /dev or /devices. This is use-
           ful with the -v option for debugging.

     -t table_file

           Read an alternate devlink.tab file. devfsadm  normally
           reads /etc/devlink.tab.

     -r root_dir
           Presume that the /dev and /devices directory trees are
           found  under root_dir, not directly under root (/). No
           other use or assumptions are made about root_dir.

     -v    Print changes to /dev and /devices in verbose mode.

EXIT STATUS

     The following exit values are returned:

     0     Successful completion.

     1     An error occurred.

FILES

     /devices
           device nodes directory

     /dev  logical symbolic links to /devices

     /usr/lib/devfsadm/devfsadmd
           devfsadm daemon

     /etc/init.d/devfsadm
           daemon start/stop script

     /etc/rcS.d/S50devfsadm
           link to init.d script

     /etc/rc0.d/K83devfsadm
           link to init.d script

     /dev/.devfsadm_dev.lock
           update lock file

     /dev/.devfsadm_daemon.lock
           daemon lock file

ATTRIBUTES

     See attributes(5) for descriptions of the  following  attri-
     butes:

     ____________________________________________________________
    |       ATTRIBUTE TYPE        |       ATTRIBUTE VALUE       |
    |_____________________________|_____________________________|
    | Availability                | SUNWcsu                     |
    |_____________________________|_____________________________|

SEE ALSO

     add_drv(1M),   devlinks(1M),    disks(1M),    drvconfig(1M),
     modinfo(1M),    modload(1M),    modunload(1M),    ports(1M),
     rem_drv(1M), tapes(1M), path_to_inst(4), attributes(5)

NOTES

     This document does  not  constitute  an  API.  The  /devices
     directory  might  not exist or might have different contents
     or interpretations in a future  release.  The  existence  of
     this notice does not imply that any other documentation that
     lacks this notice constitutes an API.