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*"

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
allocate(1)							   User Commands						       allocate(1)

allocate - device allocation SYNOPSIS
allocate [-s] [-w] [-F] [-U uname] [-z zonename] device allocate [-s] [-w] [-F] [-U uname] [-z zonename] -g dev-type DESCRIPTION
The allocate utility manages the ownership of devices through its allocation mechanism. It ensures that each device is used by only one qualified user at a time. The device argument specifies the device to be manipulated. To preserve the integrity of the device's owner, the allocate operation is exe- cuted on all the device special files associated with that device. The default allocate operation allocates the device special files associated with device to the uid of the current process. Only authorized users may allocate a device. The required authorizations are specified in device_allocate(4). When the system is configured with Trusted Extensions, allocate runs the clean program for the device before it grants access to the caller to that device. For devices with removable media that have a mountable file system, allocate mounts the media if the caller chooses. OPTIONS
The following options are supported: -F device Force allocates either free or pre-allocated devices. This option is often used with the -U option to allocate/reallocate devices to a specific user. Only those users that have solaris.device.revoke authorization are allowed to use this option. -g dev-type Allocates devices with a device-type matching dev-type. The dev-type argument specifies the device type to be operated on. -s Silent. Suppresses any diagnostic output. -U uname Uses the user ID uname instead of the user ID of the current process when performing the allocate operation. Only a user with the solaris.device.revoke authorization is permitted to use this option. The following options are supported with Trusted Extensions: -w Runs the device cleaning program in a windowing environment. If a windowing version of the program exists, it is used. Oth- erwise, the standard version is run in a terminal window. -z zonename Allocates device to the zone specified by zonename. OPERANDS
The following operands are supported: device Specifies the name of the device to be allocated. 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/* /etc/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 is Not-an-Interface. SEE ALSO
deallocate(1), list_devices(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 allocate(1)

Featured Tech Videos