xref: /titanic_41/usr/src/man/man4/device_maps.4 (revision 6d24d8e5e4f6a2d14992d9392981d8a16d695aec)
te
Copyright (c) 2008, 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]
DEVICE_MAPS 4 "Apr 30, 2008"
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 characters.

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 `\e' 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 `\e'.

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

The device_maps file must be created by the system administrator bef\eore 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:\e
rmt:\e
/dev/rst21 /dev/nrst21 /dev/rst5 /dev/nrst5 /dev/rst13 \e
/dev/nrst13 /dev/rst29 /dev/nrst29 /dev/rmt/1l /dev/rmt/1m \e
/dev/rmt/1 /dev/rmt/1h /dev/rmt/1u /dev/rmt/1ln /dev/rmt/1mn \e
/dev/rmt/1n /dev/rmt/1hn /dev/rmt/1un /dev/rmt/1b /dev/rmt/1bn:\e
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 information.

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.