On (08/24/07 08:05), James Carlson wrote: > Artem Kachitchkine writes: > > > > > while these files may be shipped r/w, they are typically shipped > > > read-only. Check out CRs 6396173 and 6430731. > > > > The bge/e1000g are not typical cases. Thanks all the same %) > > I think characterizing it as "typically" is fair. Evidence: > > % uname -a > SunOS phorcys 5.11 snv_71 i86pc i386 i86pc > % egrep 'kernel.*\.conf f ' /var/sadm/install/contents | wc -l > 146 > % egrep 'kernel.*\.conf e ' /var/sadm/install/contents | wc -l > 23
Of these 23, I believe only e1000g and nxge are networking drivers. In any case, even though it is not typical, I think the actual concern is handling the carrying forward of customized driver.conf edits across an upgrade for the "e" cases. For these handful of cases the suitable i.* scripts will be provided to account for any changes in syntax introduced for public properties. Since mac_get_prop() also does a ddi_get_prop() as a last-resort lookup, the custom setting should be picked up after the upgrade (with some warning messages issued about usage of the driver.conf interface instead of dladm). --Sowmini
