Danek Duvall wrote:
On Thu, Apr 30, 2009 at 01:59:24PM +0200, Ramshankar wrote:
It seems to be pkg(5) touches the various boot archive files for loading
the driver (name_to_major, devlink.tab etc.) but does not really load
the driver.
Is there any facility in pkg(5) for simply loading the driver like:
add_drv (-i if needed) -m'* 0666 root sys' driver
devfsadm -i driver
If so could any post the pkgsend action for this?
The "add driver perm" doesn't load the driver just seems to update the
config files.
Bart and I are debating this. The drivers are intentionally not loaded,
since I was (and am still) paranoid about having just-delivered code run at
package install time. We may compromise and have the post-execute phase of
the driver install load all drivers that had been added or updated, so that
at least all bits are on the system before the potential panic.
Another thing we need is an example / instructions on how to 'emulate' a
SRv4 postinstall/preremove script with pkg(5); I understand I need to use
SMF service for this.
After digging a bit I found this:
http://markmail.org/message/wldyadbrqmtpgnq6
Is there any documentation on "actuators" ?
man -s5 pkg, as of build 111. If you don't have that,
http://src.opensolaris.org/source/xref/pkg/gate/src/man/pkg.5.txt
If I understood right, even actuators don't "enable" a service on
installation right?
Correct.
Danek
Could we now use the "disable_fmri" actuator to disable a service
*prior* to installing new files and enable the service after installing?
If so are there any examples of something that does this already? Would
save us some time.
Regards,
Ram.
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
