Bart Smaalders wrote: > Philip Brown wrote: >> >> Sounds like "a postinstall script, that doesnt have to use >> chroot $PKG_INSTALL_ROOT >> any more". > >... > > chroot $PKG_INSTALL_ROOT > > will only work for images that are the exact duplicate of the hostmachine, > and will fail spectacularly on diskless machines, cross-architecture > images, > etc.
Errr... If that will fail for a diskless machine, then pkgadd -R /some/path ..... will also fail for a diskless machine... Given that sort of situation, the sysadmins must either have some kind of workable method to add/delete packages, or they perhaps "build an image" on a normal machine, and dup it over. Whatever kind of mechanisms work "now", they can also use successfully for the above, one would presume? >>> Because we avoid running unknown scripts as root in installation >>> context, we will able to install pkgs into zones w/o having >>> to boot each one as we do today; instead we can do all the >>> pkgs ops on zone clones... this will greatly speed up zone >>> packaging/patching operations. >> >> I dont see what the big fuss is about "unknown scripts in installation >> context", compared to "unknown scripts being run through an SMF harness". >> > > Have you ever patched a zone? yes. well, more specifically, I patched the global, and it trickled down, if I recall. It was very irritating when a zone was "configured, but not active", or something like that. The patch bombed, if I recall, for that zone. This is certainly a problem, I agree. But what does that have to do with "unknown scripts"? _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
