[indiana-discuss] "no scripting zone" and isaexec(3C) == architectural

Shawn Walker swalker at opensolaris.org
Fri Jun 12 09:44:41 PDT 2009


Moinak Ghosh wrote:
>    While this is good, thinking through the impact it will have on application
>    and layered software packages and providing adequate hooks to take
>    care of configuration issues should have been much higher priority in the
>    IPS development action-items. For eg. there is currently no way to package

I'm fairly certain pkg(5) users preferred the priorities to be on fixing 
performance issues and adding basic functionality.  As you are aware, 
resources are finite, and so the most important items were prioritised. 
    It is regrettable that more resources were not available so that the 
work you are talking about could not have been done sooner, but was 
necessary.

Significant strides have been made in memory usage reduction, 
performance improvements, documentation, publication, repository browser 
user interface, and other areas.

>    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.

Cheers,
-- 
Shawn Walker



More information about the indiana-discuss mailing list