Jordan Vaughan wrote: > Hello Experts, > > I'm one of two engineers working on the Solaris 10 Containers project > (http://opensolaris.org/os/project/s10brand). I'm in charge of evaluating > exclusive-stack Solaris 10 Containers and determining which changes will need > to be made to the emulation layer to allow such zones to work. Nicolas Droux > told me that most physical NICs still appear in /dev, but not all. UV does not change that. After UV, all physical links and implicitly created VLANs still have their /dev links. For data-links that are created using vanity name, for example, if you create an aggregation using "dladm create-aggr -l bge0 -l bge1 aggr1", then that aggregation does not have the /dev link since it does not have a legacy name.
As I recall, Aurna moved around some of the code which creates the legacy /dev links for non-global zones from vplat.c to linkprop.c, but the /dev links should still be supported. Then Crossbow removed the support for implicitly-created VLANs. Even after that, the /dev link for physical links should still be there. Thanks - Cathy > I wanted to confirm that this is the case and ask if there was anything else > that Clearview changed that makes OpenSolaris networking incompatible with > Solaris 10 userlands. (In other words, if I were to run a Solaris 10 > userland within a zone on top of OpenSolaris, would anything that Clearview > introduced or changed prevent the Solaris 10 userland from using NWIFs that I > provide to the zone?) If some physical NICs won't appear in /dev in addition > to /dev/net, then what would you suggest that we do to allow Solaris 10 > applications that depend on the presence of the NICs in /dev to work? > > Thanks, > Jordan Vaughan > Solaris Zones >
