Solaris zone devices


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris zone devices
# 1  
Old 08-31-2009
Solaris zone devices

Hello all,

I'm having issue with trying to add device resource to my zone from the global zone.
I did the following

zoncfg -x larryase
add device
set match="/dev/tty*"
end

I get device already set, but in me zone I don't see the device.
Is there a "reboot -- r" command for zones? or is there a zone start the device?

Thanks all.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Solaris 11 zone has no external network access (except to Global Zone)

Hi, hoping someone can help, its been a while since I used Solaris. After creating a NGZ (non global zone), the NGZ can access the GZ (Global Zone) and the GZ can access the NGZ (using ssh, zlogin) However, the NGZ cannot access any other netwqork devices, it can't even see the default router ... (2 Replies)
Discussion started by: GazinLincoln
2 Replies

2. Solaris

Solaris 11 Global zone patching having Solaris 10 branded zone

I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
Discussion started by: amity
2 Replies

3. Solaris

Patching Procedure in Solaris 10 with sun cluster having Solaris zone

Hi Gurus I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow. Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies

4. UNIX for Advanced & Expert Users

Solaris 10: I forgot to detach a zone before zpool export. Uninstall zone?

Dear all, recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes. I did the following: host1: $ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed $ zpool export zone1 host2: $ zpool... (2 Replies)
Discussion started by: custos
2 Replies

5. Solaris

Solaris 10 local zone on Solaris 11 global zone

Hi, A quick question: Can Solaris 10 local zones be moved to a Solaris 11 global zone and work well? Thank you in advance! (5 Replies)
Discussion started by: aixlover
5 Replies

6. Solaris

Sharing devices (tape drive) to local zone

I have to setup a local zone and need to share the fiber attached tape drive that is connected to the global zone. What is the best way to do this? Will sharing the /dev/rmt directory via lofs work? Any help is appreciated! (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

7. Solaris

solaris I/O devices info

Hi, can anyone help in finding the hardware related details of I/O devices of remote solaris machine .Thanks in advance. (7 Replies)
Discussion started by: pratheepv
7 Replies

8. Solaris

Solaris Zone : Non global Zone check failed

Hi All , I try to install some packages in my global zone... On the execution of the installion of the script it quits by saying the error "Non global zone check failed" Kindly help me in this regard Thanks in advance, jeganr (7 Replies)
Discussion started by: jegaraman
7 Replies

9. Solaris

devices in solaris 10

i want to use the devfsadm command and understand its function (3 Replies)
Discussion started by: bondoq
3 Replies
Login or Register to Ask a Question
list_devices(1) 						   User Commands						   list_devices(1)

NAME
list_devices - list allocatable devices SYNOPSIS
list_devices [-s] [-U uid] [-z zonename] [-a [-w]] -l | -n | -u [device] | [-l | -n | -u] -c dev-class list_devices [-s] -d dev-type DESCRIPTION
The list_devices utility lists the allocatable devices in the system according to specified qualifications. The device and all device special files associated with the device are listed. The device argument is optional and, if it is not present, all relevant devices are listed. If dev-class is present, devices belonging to the specified dev-class are listed. There is no default dev- class. OPTIONS
The following options are supported: -l [-c dev-class | device] Lists the pathnames of the device special files associated with the device that are allocatable to the cur- rent process. If dev-class is specified, lists only the files associated with all devices of the specified device class. If device is specified, lists only the files associated with the specified device. -n [-c dev-class | device] Lists the pathnames of the device special files associated with the device that are allocatable to the cur- rent process but are not currently allocated. If dev-class is specified, lists only the files associated with all devices of the specified device class. If device is specified, lists only the files associated with the specified device. -s Silent. Suppresses any diagnostic output. -u [-c dev-class | device] Lists the pathnames of device special files associated with the device that are allocated to the owner of the current process. If dev-class is specified, lists only the files associated with all devices of the specified device class. If device is specified, lists only the files associated with the specified device. -U uid Uses the user ID uid instead of the real user ID of the current process when performing the list_devices operation. Only a user with the solaris.device.revoke authorization can use this option. The following options are supported when the system is configured with Trusted Extensions: -a Lists attributes like authorizations, cleaning programs and labels associated with a device. The list is a single line of semicolon (;) separated key=value pairs for each device in the format: device=device-name;type=device-type; auths=auths;clean=device-exec; device-attributes; files=device-list where device-attributes is the contents of the reserved1 field of device_allocate(4). The field is colon (:) separated.) See device_allocate(4) for a description of these attributes and their format. The -a output has the following keys: auths Specifies the list of authorizations. The value is auths is described in device_allocate(4). clean Specifies the device cleaning script. The value is device-exec as described in device_allocate(4). device Specifies the device name. The value is device-name as described in device_allocate(4). files Specifies the device file paths. The value is device-list as described in device_maps(4). type Specifies the device type. The value is device-type as described in device_allocate(4). -d Displays the system-supplied default attributes for the device types managed by device allocation. If dev-type is specified, it lists the default attributes for only that device type. -w This option can be used with -a to list the current owner of the device as the key value pair owner=value. value is the uid of the current owner of the device. If the device is unallocated, value is /FREE. If the device is in error state, value is /ERROR. This option also suppresses any diagnostic output. -z zonename When specified with the -l option, lists only those non-allocated devices whose label range includes the label of the zone- name, and of the allocated devices, only those that are allocated at the same label as that of zonename. When specified with the -n option, lists only those non-allocated devices whose label range includes the label of the zone- name. When specified with the -u option, lists only those devices that are allocated at the same label as that of zonename. EXAMPLES
Example 1 Listing All Devices The following example lists all devices available to the caller for allocation: % list_devices -l device: audio type: audio files: /dev/audio /dev/audioctl /dev/sound/0 /dev/sound/0ctl Example 2 Listing Attributes of All Devices On a system configured with Trusted Extensions, the following example lists attributes of all devices available to the caller for alloca- tion: % list_devices -al device=audio1;type=audio; auths=solaris.device.allocate; clean=/etc/security/lib/audio_clean; minlabel=admin_low:maxlabel=admin_high; files=/dev/audio1 /dev/audio1ctl /dev/sound/1 /dev/sound/1ctl Example 3 Listing Attributes Including the Device Owner On a system configured with Trusted Extensions, the following example lists attributes including the device owner of all devices allocated to the user: % list_devices -auw device=audio2;type=audio;auths=solaris.device.allocate; clean=/etc/security/lib/audio_clean; minlabel=admin_low:maxlabel=admin_high:zone=public; owner=1234; files=/dev/audio2 /dev/audio2ctl /dev/sound/2 /dev/sound/2ctl EXIT STATUS
The following exit values are returned: 0 Successful completion. 20 No entry for the specified device. other value An error occurred. FILES
/etc/security/device_allocate /etc/security/device_maps /etc/security/dev/* /usr/security/lib/* ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |See below. | +-----------------------------+-----------------------------+ The invocation is Uncommitted. The options are Uncommitted. The output from the -a and -w options is Uncommitted. All other output is Not- an-Interface. SEE ALSO
allocate(1), deallocate(1), bsmconv(1M), dminfo(1M), mkdevalloc(1M), mkdevmaps(1M), device_allocate(4), device_maps(4), attributes(5) Controlling Access to Devices 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. /etc/security/dev, mkdevalloc(1M), and mkdevmaps(1M) might not be supported in a future release of the Solaris Operating Environment. SunOS 5.11 30 Apr 2008 list_devices(1)