Hi Ethan,
Per our conversation Friday. The DDU should probably be the
prefered way to install drivers and do device detection (anything it
doesn't do should be filed as an RFE for it).
This opposed to using derived manifests, as otherwise, we end up
forcing our customers to continue to roll-their-own solutions opposed to
our being able to make our out-of-box experience better and more
integrated.
However, with all the other possible examples for Use Cases
including another idea instead of #3 would be good. I don't recall what
all was envisioned but connecting to a hypothetical Configuration
Management DB could be good; perhaps investigating what was installed on
the machine before?
Thank you,
Clay
On Fri, 30 Apr 2010, Ethan Quach wrote:
On 04/26/10 15:44, [email protected] wrote:
One last comment. Shouldn't the last use case be covered by the DDU? As one
shouldn't need to specify device packages necessarily?
No, I think they are different cases. DDU specifically allows addition
of packages into the live booted AI boot image so that install can
proceed. Derivation would allow for specifying packages into
the pkglist to install into the target.
The result of using DDU functionality would end up also installing
the packages into the target, so there's some overlap there, but
the use case is different.
-ethan
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
