Danek Duvall wrote:
Liane Praza wrote:
Wyllys Ingersoll wrote:
Liane Praza wrote:
- Similarly, driver bindings are handled by actions in IPS manifests
and today are added by the OpenSolaris distribution team.
Does the above statement include updating the ACPI tables for x86
and running the "add_drv" command for packages that contain new
device drivers (sparc and x86) ?
add_drv, yes.
No, no add_drv.
I should have been clear that since we were talking (I believe) about ON
postinstall scripts, I was referring to what add_drv -b does (i.e. the
non-live image case).
I was very careful to make sure that modules weren't
actually loaded on installation. Since then, that's proven to be a less
than optimal choice, so what we're going to do is to operate as we
currently do -- modifying config files only -- and then actually load the
module in the post-execute stage, so that if we're going to panic, at least
we've laid all the files down correctly.
If you're updating a driver (or doing anything else that forces the actions
to happen on a non-live image), then obviously nothing will get loaded
until you boot the other boot environment
In other words, today driver packages must be reboot-required in order to
have the module loaded. In the future, that won't be necessary. Either
way, an ON developer is not currently expected to do anything special to
their SVR4 package to ensure correct operation on OpenSolaris.
(Of course, once we're natively generating IPS packages, the story will be
different, but I'll document those steps in the general advice about
generating native IPS packages from ON, as they're unhelpful now.)
liane
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
