> This is one place where he might have a half valid > point. There should be some better mechanism to > patch a zone without having to bring it up. There
Agreed which is why in Solaris 10 1/06 it doesn't actually boot the zone if it's not running - instead, it "mounts" the zone's file systems and patches them without bring the zone up to single-user mode. > cluster situations). A patch from the global zone > should be able to be installed in a non-running local > zone by fiddling with the filesystem. Actually, fiddling with a zone's file system directly from the global zone is inherently unsafe - imagine the case where a malicious but privileged user in a non-global zone replaced a file to be patched with a symbolic link to a critical file such as /etc/passwd - if the global zone manipulated the zone's file, it actually would end up modifying the global zone's own /etc/passwd. That's the reason that Solaris 10 3/05 used to boot non-running zones single-user and in 1/06, a new "scratch zone" mechanism was introduced that eliminates the "boot" itself. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
