Sean McEnroe writes:
> On 2008綛\xB409\xE6\x9C\x8817\xE6\x97\xA5 10:33, James Carlson wrote:
> > (In other words, seeing "snv_97" at some point won't necessarily tell
> > you what's the newest available for your system, because packages will
> > be versioned independently.)
> >
> Often the firmware version must be matched to a vendor driver version
> especially with a 3rd party driver. We really need to enhance modinfo to
> output the real driver version string as modinfo does for a loaded
> driver. We should make solaris easier to use for driver writers and IT
> folks, not harder. I see no problem in modinfo being enhanced to output
> all of the afore mentioned solutions plus the real driver version such
> as v1.2.3 which may be more meaningful to a 3rd party driver writer IMHO.
Include what you want in modinfo, but:
- you don't have SCCS to kick around anymore
and:
- it's up to package authors to include versioning that makes
administrative sense
and:
- regardless of what third parties may or may not contribute to the
driver, it's the packaged software that the user installs, not
some random driver version number.
The administrative unit on OpenSolaris (using IPS) is the versioned
package, and I think that's where we should be headed in terms of
administrative practice. At least as long as the discussion is on
'[email protected]'. ;-}
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
