So am I really looking at a maintenance image to update a /usr (which will later be shared RO among guests), and then copying rpm-written files from that maintenance image's /var and /etc to each of the images?
Or is there a way I can rpm -Uhv on each of the images though /usr is shared RO? Or maybe hack up the rpm file to exclude anything in the /usr tree for the images sharing /usr. Is there a converse of rpm2cpio, or do RPMS have to be rebuilt from a .spec and source? > Is there a generally accepted "best way" to upgrade/install packages > with RPM with a shared RO /usr across multiple images? Management is > leaning toward all guests having the same software installed, where > service A would be running on one image, and service B on another, > though the software is installed on both. The RPM database across > images would be identical. I do not see a "clean" or "easy" > way to deal > with upgrading each img, because of their differences in /etc > and /var, > while respecting /usr. Thanks, ~ Daniel ----------------------------------------------------------------------- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.
