I am not certain excatly how the driver installation scripts for the add-on card make their devices and links. But, the actual devices appear in /devices and symlinks (presumably created by the installer) are placed in /dev in the global zone. I don't think that devfsadm does it; I believe the installer for the driver may put them there itself.

If I actually create the device node in $zoneroot/dev then I can grant the device to the zone. But this seems a really convoluted way around this.

Is this the only way to make this work? Seems like there are probably other peripheral devices that don't build their device links via devfsadm that would be safe and/or useful in a non-global zone.


Edward Pilatowicz wrote:
On Mon, Aug 28, 2006 at 10:01:49AM -0400, Scott Dickson - Systems Engineer 
I am working with a customer to try to access tty devices from within a
zone.  They are using a custom interface card for their tty devices, but
it appears to create pretty standard device nodes and links from
/dev/tty and /dev/cua to the devices.

As a first test, just to verify the ability to add a tty to a zone, I
created a second symlink, /dev/cua/b, that pointed to the same location
as /dev/cua/a.  I then added this device to the zone using add device,
set match=/dev/cua/b and restarted the zone.  I did not see the new tty
in the zone.

that is correct.  hand created symlinks can not be added to a zone via
zonecfg(1M).  zonecfg(1M) will only add /dev devices to a zone that have
been generated by the system.

assuming that /dev/cua/a existed on the system before you started
creating links in /dev then adding that to the zone should work.

The customer wants to take this a step further, since they use a large
number of these tty ports in their applications.  They want to allocate
/dev/cua/ devices to different zones.

Why is this failing?  I am able to access /dev/ttya just fine in a zone.

how are the /dev entries for their devices being created?

zones-discuss mailing list

Reply via email to