Could some SMFers please weigh in on 6725004 and give some opinions on how best to address it?
Here's a summary of the problem: Sun Update Connection Enterprise attempts to install "single-user" patches using an rcS.d script. This has historically been a problem, since zone roots may not have been mounted yet. Patchadd was recently changed to partially work around this problem, by enabling system/filesystem/local, but when that mechanism is triggered from an rcS.d script (or, presumably, from a service on which milestone/single-user depends), it yields a deadlock - system/filesystem/local can't be run, because milestone/single-user hasn't been reached. (This is, I believe, in addition to the technical issues surrounding performing SMF operations from an rcS.d script.) I believe that the most truly correct way to address this problem is to have a deferred patching service that depends on system/filesystem/local, and on which all other later services depend. However, I think the only way to implement such a service would be to modify the dependencies of those later services, and that seems awkward. (One could also rename system/filesystem/local, retain the original name as something of a milestone, and insert the deferred patching service as a new service between the renamed s/f/l and the original s/f/l, but that seems quite ugly.)
