Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   20652 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

device_maps(4)			 File Formats			device_maps(4)

NAME
       device_maps - device_maps file

SYNOPSIS
       /etc/security/device_maps

DESCRIPTION
       The  device_maps	 file  contains	 access control information about each
       physical device. Each device is represented by a one line entry of  the
       form:

	 device-name : device-type : device-list :

       where

       device-name

	   This	 is an arbitrary ASCII string naming the physical device. This
	   field contains no embedded white space or non-printable characters.

       device-type

	   This is an arbitrary ASCII string naming the generic	 device	 type.
	   This	 field	identifies  and	 groups together devices of like type.
	   This field contains no embedded white space or non-printable	 char‐
	   acters.

       device-list

	   This	 is  a	list  of  the device special files associated with the
	   physical device. This field contains valid device special file path
	   names separated by white space.

       The device_maps file is an ASCII file that resides in the /etc/security
       directory.

       Lines in device_maps can end with a `\' to continue  an	entry  on  the
       next line.

       Comments	 may  also  be	included. A `#' makes a comment of all further
       text until the next NEWLINE not immediately preceded by a `\'.

       Leading and trailing blanks are allowed in any of the fields.

       The device_maps file  must  be  created	by  the	 system	 administrator
       bef\ore device allocation is enabled.

       This file is owned by root, with a group of sys, and a mode of 0644.

EXAMPLES
       Example 1 A Sample device_maps File

       The following is a sample device_maps file:

	 # scsi tape
	 st1:\
	 rmt:\
	 /dev/rst21 /dev/nrst21 /dev/rst5 /dev/nrst5 /dev/rst13 \
	 /dev/nrst13 /dev/rst29 /dev/nrst29 /dev/rmt/1l /dev/rmt/1m \
	 /dev/rmt/1 /dev/rmt/1h /dev/rmt/1u /dev/rmt/1ln /dev/rmt/1mn \
	 /dev/rmt/1n /dev/rmt/1hn /dev/rmt/1un /dev/rmt/1b /dev/rmt/1bn:\

FILES
       /etc/security/device_maps    Contains  access  control  information for
				    devices.

ATTRIBUTES
       See attributes(5) for descriptions of the following attributes:

       ┌─────────────────────────────┬─────────────────────────────┐
       │      ATTRIBUTE TYPE	     │	    ATTRIBUTE VALUE	   │
       ├─────────────────────────────┼─────────────────────────────┤
       │Interface Stability	     │Uncommitted		   │
       └─────────────────────────────┴─────────────────────────────┘

SEE ALSO
       allocate(1), bsmconv(1M), deallocate(1),	 list_devices(1),  dminfo(1M),
       device_allocate(4), attributes(5)

NOTES
       The  functionality  described  in  this	man  page is available only if
       Solaris Auditing has been enabled. See bsmconv(1M)  for	more  informa‐
       tion.

       On  systems  configured	with  Trusted Extensions, the functionality is
       enabled by default. On such systems,  the  device_allocate(4)  file  is
       updated automatically by the system.

SunOS 5.10			  30 Apr 2008			device_maps(4)

Vote for polarhome