xref: /titanic_41/usr/src/man/man1m/devfsadm.1m (revision 3fb330b78c0911247d5eee86f7997a64a9a743e5)
te
Copyright (c) 20088888888 Sun Microsystems, Inc. All Rights Reserved.
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
DEVFSADM 1M "Jun 23, 2008"
NAME
devfsadm, devfsadmd - administration command for /dev
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 namespace. 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. Next, devfsadm creates logical links to device nodes in /dev and /devices and loads the device policy.

devfsadmd(1M) is the daemon version of devfsadm(1M). The daemon is started 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 kernel.

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, 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 might 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. This is useful 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 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 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

/dev/.devfsadm_dev.lock

update lock file

/dev/.devfsadm_daemon.lock

daemon lock file

/etc/security/device_policy

device policy file

/etc/security/extra_privs

additional device privileges

SEE ALSO

svcs(1), add_drv(1M), modinfo(1M), modload(1M), modunload(1M), rem_drv(1M), svcadm(1M), tapes(1M), path_to_inst(4), attributes(5), privileges(5), smf(5), devfs(7FS)

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.

devfsadm no longer manages the /devices name space. See devfs(7FS).

The device configuration service is managed by the service management facility, smf(5), under the service identifier, and can be used to start devfsadm during reconfiguration boot by:

svc:/system/device/local:default

Otherwise, devfsadm is started by:

svc:/system/sysevent:default

Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The service's status can be queried using the svcs(1) command.