I'm derailing this case there appears to be a very strong consensus from
those that have commented on the case that:
a) it doesn't solve the root causes of the problem
b) it could actually make it worse in some cases
c) makes Solaris look like it needs tuning for enterprise use.
While the case technical content is obvious it is highly controversial.
I've thought about this more and I now feel so strongly about this case
that I would actually vote against it despite my previous comments.
We need to stop "patching" and "hacking" around this issue and solve the
issue with the boot archive inconsistency once and for all. Either by
removing the use of the boot archive completely when booting from disk
(assuming doing so doesn't introduce a boot time regression) or by
ensuring that it is never out of date. The solution to this should
assume that at the time of uadmin we can't write to the root filesystem.
I have rebuilt many many boot archives and not once have I ever been in
a situation where anything other than "svcadm clear boot-archive" or
boot from the failsafe and update it were the correct solution. Sure
this is a kernel developers view but an admin has even less chance of
knowing if there is another solution.
--
Darren J Moffat
