>> b. It is also needed to create the devfs minor node of a VLAN link (if >> the assgined physical name is a ppa hack name), so that we can create >> a symbol link of the /dev node in the local zone. >> >> As part of vanity naming, we could do an implied "dladm create-vlan" >> as part of exclusive-zone boot, and that VLAN's devfs minor node will >> be created then, therefore requirement (b) is no longer needed. > > For an implicit/legacy VLAN name such as bge32000, something would need > to tell GLD to create the devfs node? > What I mean is to *explicitly" create that VLAN (that is added by the vanity naming project). As a result, the devfs node will be created.
> Today the knowledge of this name only exists in the zonecfg xml file. > > Are you saying that zoneadm/zoneadmd would do a 'dladm create-vlan > bge32000' as part of booting the zone. > > That would require know which name is a vlan and which isn't. AFAIK > zoneadm/zoneadmd doesn't have that knowledge today. > Yes, that would be a problem. We have to make zoneadm know that this is a VLAN ppa hack name so that it knows to create a VLAN 32 over bge0. I guess I will keep those ioctls as is. [ I vaguely remembered that Nicolas commented long before maybe we should introduce syntax like "physical = bge0 vlanid = 32". I say his point only now. Sign. ] Thanks - Cathy
