Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

devfs.conf(5) [freebsd man page]

DEVFS.CONF(5)						      BSD File Formats Manual						     DEVFS.CONF(5)

NAME

     devfs.conf -- boot-time devfs configuration information

DESCRIPTION

     The devfs.conf file provides an easy way to set ownership and permissions, or create links for devices available at boot.

     It does not work for devices plugged in and out after the system is up and running, e.g. USB devices.  See devfs.rules(5) for setting owner-
     ship and permissions for all device nodes, and devd.conf(5) for actions to be taken when devices are attached or detached.

     Lines starting with a hash sign ('#') and empty lines are ignored.  The lines that specify devfs.conf rules consist of three parameters sepa-
     rated by whitespace:

     action  The action to take for the device.  The action names are only significant to the first unique character.

     devname
	     The name of the device created by devfs(5).

     arg     The argument of the action.

     The actions currently supported are:

     link    This action creates a symbolic link named arg that points to devname, the name of the device created by devfs(5).

     own     This action changes the ownership of devname.  The arg parameter must be in the form of an owner:group pair, in the same format used
	     by chown(8).

     perm    This action changes the permissions of devname.  The arg parameter must be a mode as explained in chmod(1).

FILES

     /etc/devfs.conf
     /usr/share/examples/etc/devfs.conf

EXAMPLES

     To create a /dev/cdrom link that points to the first SCSI(4) CD-ROM, the following may be added to devfs.conf:

	   link    cd0	   cdrom

     Similarly, to link /dev/cdrom to the first ATAPI CD-ROM device, the following action may be used:

	   link    acd0    cdrom

     To set the owner of a device, the own action may be specified:

	   own	   cd0	   root:cdrom

     To set the permissions of a device, a perm action should be used:

	   perm    cd0	   0660

SEE ALSO

     chmod(1), devd.conf(5), devfs(5), devfs.rules(5), chown(8)

AUTHORS

     This manual page was written by Roland Smith <rsmith@xs4all.nl>.

BSD
								   May 17, 2005 							       BSD

Check Out this Related Man Page

devfs(7FS)                                                         File Systems                                                         devfs(7FS)

NAME

       devfs - Devices file system

DESCRIPTION

       The devfs filesystem manages a name space of all devices under the Solaris operating environment and is mounted during boot on the /devices
       name space.

       The /devices name space is dynamic and reflects the current state of accessible devices under the Solaris operating environment. The  names
       of all attached device instances are present under /devices.

       The content under /devices is under the exclusive control of the devfs filesystem and cannot be changed.

       The system may be configured to include a device in one of two ways:

                 By means of dynamic reconfiguration (DR), using, for example, cfgadm(1M).

                 For  devices driven by driver.conf(4) enumeration, edit the driver.conf file to add a new entry, then use update_drv(1M) to cause
                 the system to re-read the driver.conf file and thereby enumerate the instance.

       The device may be attached through a number of system calls and programs, including open(2), stat(2) and ls(1). During device  attach,  the
       device  driver typically creates minor nodes corresponding to the device via ddi_create_minor_node(9F). If the attach is successful, one or
       more minor nodes referring to the device are created under /devices.

       Operations like mknod(2), mkdir(2) and creat(2) are not supported in /devices.

FILES

       /devices        Mount point for devfs file system

SEE ALSO

       devfsadm(1M), vfstab(4), attach(9E)

NOTES

       The /devices name space cannot be unmounted.

       All content at or below the /devices name space is an implementation artifact and subject to incompatible change or removal without notifi-
       cation.

SunOS 5.10                                                          26 Oct 2004                                                         devfs(7FS)
Man Page