1. Run them under VirtualBox or Zones, but if you go with Solaris 10 as a
global running on the hardware, make sure you run the updatemanger or smpatch
update with your sunsovle.sun.com account then you should be able to run any OS
supported w. VirtualBox (I'm running 2.1) then 2008.11, snv_104.
2. Another consideration is from a HW device support, your best chance is with
snv_b105 note has less in snv_b104 is supported with a view exceptions when
comparted with 2008.11 (Graphical desktop look great), device support that is
not in snv_b105 for example:
# diff driver_aliases2008.11_sorted driver_aliases_snv_b105_sorted |grep '<'
< audioixp "pci1002,4341"
< bnx "pci14e4,1639"
< bnx "pci14e4,163a"
< qlc "pciex1077,2532"
< xnbo "xnb"
# diff driver_aliases2008.11_sorted driver_aliases_snv_b104_sorted |grep '<'
< audioixp "pci1002,4341"
< bnx "pci14e4,1639"
< bnx "pci14e4,163a"
< iwh "pciex8086,4232"
< iwh "pciex8086,4235"
< qlc "pciex1077,2532"
< xnbo "xnb"
#
Look how OpenSolaris has impacted each of the Solaris's version. these vendor
id and device id has not made it in OpenSolaris snv driver builds for some
reason, for example the 2008.11 and 2008.5 bugid are not making it up the food
chain this is worry some trend, for OpenSolaris in that Solaris Express
Community Edition and OpenSolaris 2008.11 versions diverge the more the
maintenance costs for contributors and SUN support costs go up for validation
and think that not all changes are made use of, which can impact the quality of
code.
Where as if you look at the number of device supported so in each version:
wc -l dr* |grep -v
808 driver_aliases10u6
887 driver_aliases2008.11
1039 driver_aliases_snv_b104
1043 driver_aliases_snv_b105
So one should try out and request RFE's for there venderid and device id
(/usr/X11/bin/scanpuc or prtconf -Dpv) if support is needed for each device.
So I hope that the changes that are submitted in 2008.11 make it back into
OpenSolaris and then Soalris down the road and not get lost.
--
This message posted from opensolaris.org