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?
Cheers,
--
Shawn Walker
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
