Moinak Ghosh wrote:
On Fri, Jun 12, 2009 at 11:32 PM, Shawn Walker<[email protected]> wrote:
Moinak Ghosh wrote:
On Fri, Jun 12, 2009 at 10:33 PM, Shawn Walker<[email protected]>
wrote:
Moinak Ghosh wrote:
On Fri, Jun 12, 2009 at 10:14 PM, Shawn Walker<[email protected]>
wrote:
Moinak Ghosh wrote:
the following HP driver with IPS and have it working properly:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=3186080&prodNameId=3288103&swEnvOID=2023&swLang=8&mode=2&taskId=135&swItem=MTX-30012bd09e11426b9b289142e4
It modifies a bunch of configuration files.
Actually, after looking at that particular driver's
postinstall/checkinstall, etc. scripts, it doesn't appear to do
anything
more than add a driver to the system or remove it. Nothing stands out
as
requiring scripting, and I don't see it modifying any true
"configuration
files". The few scripting items that are there don't apply to
OpenSolaris
2009.06, including, the bootenv.rc changes, and the jumpstart
preparation.
Regardless, you are right that there are some specific cases that will
have
to be dealt with.
I have found in practice that the driver does not work unless the
class-action
scripts are allowed to execute.
There is a difference between driver installation for IPS and for SVR4.
Namely, installing an SVR4 package would load a driver immediately,
while
IPS purposefully does not (currently). To activate, you must reboot, or
manually load the driver.
We have been discussing this particular behaviour. There have been
concerns
about having just-delivered code run at package install time. The
compromise
may be that have the post-execute phase of the driver install loads all
drivers that had been added or updated, so that at least all bits are on
the
system before the potential panic.
Could this be why you believe the class-action scripts are necessary?
No. This particular driver *requires* a reboot to work even when using
SVR4. So IPS not loading drivers immediately after install is not an
issue. If all the files are not updated as needed then the driver does
not work at all.
Can you indicate which specific files can not be updated by an equivalent
IPS package for this driver? IPS supports a driver action that should
handle everything this package needs. The only configuration files that I
saw the scripts for the SVR4 package altering that are needed for
OpenSolaris 2009.x were driver related files.
IPS does not handle the actions performed by these scripts:
You say that without showing specifics. I looked at these same files,
and see nothing that our driver action cannot do that the driver needs.
You need to convince me that this won't work ;)
i.bootenv.rc
bootenv.rc does not apply to Solaris 10 after update 1 or to OpenSolaris
2009.06 at all. See the comments in the file itself.
i.devlink
i.master
> r.devlink
> r.master
The driver action provides these as far as I know.
The only reasoning you've provided so far, are "there are scripts so it
won't work." Again, I see nothing in those scripts *that is actually
needed for the driver to work on 2009.06* that IPS does not provide.
Cheers,
--
Shawn Walker
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
