Paul,
> GARY> Hummm, I wonder what Paul's trying to fix that's beyond the
> GARY> suggested fixes that I gave for
> GARY> 6384568 SUNWcsr postinstall may be too aggressive with the audit
> GARY> service in zones
> GARY> 6381337 bsmconv(1M) may not completely work for an alternate
> GARY> root
>
> The main problem that was observed in bug 6381337 is that the auditd
> service is not started when an alternative root is used, because the
> bsmconv script attempts to enable the service on the host that the
> script is running on, rather than the host that is represented by the
> mounted filesystem that is being changed. The suggested fix of adding
> the SMF command to enable this service to the upgrade profile seems
> like a resonable solution to this problem (assuming we can continue
> using the interface).
>
> However, comments added to the bug by Ric Aleshire and also an
> inspection of the code that was done by me suggest that there are a
> number of other things in this script which do not work as expected
> when an alternate root is used.
It looks like TX hopelessly broke bsmconv for itself. I've
filed a bug. Fortunately it doesn't seem to be the case for
``regular'' Solaris.
I agree with Liane. The only thing that can go into the upgrade
file is SMF related stuff. When the file goes away because
it's no longer needed, the other stuff just wouldn't work any
more, so it's better never to permit it to be there in the
first place.
> Further examples are the running of '/usr/sbin/devfsadm -e' when TX is
> installed (as pointed out by Ric) and the use of 'mkdevalloc' and
> 'mkdevmaps' to initialise device allocation (which, as I understand
This is TX specific. Please leave the TX project team work
out how to fix what they broke here. I suspect if they fix that
there might not be be anything to put in the upgrade file for TX.
Anyhow, IMO, fixing 6381337 and 6384568 for Solaris is a first
step. TX can build on that.
Thankx,
Gary..
