devfsadmd should probably be managed by SMF rather than syseventd
At present, devfsadmd is started and restarted by syseventd when it receives a message destined for devfsadm, rather than by SMF. Assuming this is a hack from the days before SMF it should be adjusted such that SMF manages the service, and the new service depends on sysevent.
This is minorly less resilient (in that the user could succeed in disabling devfsadmd), so perhaps the messages regarding it being absent (which are currently debug messages, I think) should be console messages, similar to the whining when syslogd isn't running.
No data to display