On 02/ 8/10 11:39 AM, Darren Reed wrote: > Dave Miner wrote: >> On 02/ 8/10 10:59 AM, Darren Reed wrote: >>> Dave Miner wrote: >>>> On 02/ 6/10 08:35 PM, Mike Gerdts wrote: >>>>> On Sat, Feb 6, 2010 at 7:11 PM, Darren Reed<Darren.Reed at sun.com> >>>>> wrote: >>>> ... >>>>>> I have one question for you and this proposal from Sanjay: >>>>>> >>>>>> What happens when an application stores peristent data >>>>>> under a shared directory in /var and there are multiple BEs >>>>>> that have their own version of this application and the >>>>>> binary data format is not compatible? >>>>> >>>>> <sarcasm>You write a postinstall script that does the conversion as >>>>> the relevant package is installed.</sarcasm> >>>>> >>>> >>>> You provide a conversion method that's run as an SMF actuator! :-) >>>> >>>>> More seriously, I'm not really sure. I think that a snapshot is >>>>> important to be able to provide fallback for when things go wrong and >>>>> for when some sort of a data conversion is required and fallback is >>>>> needed. This should not be as encumbered as a boot environment >>>>> snapshot/clone. Hopefully the occurrences where such conversions are >>>>> needed are kept to a minimum. Does data exist to suggest that this is >>>>> a frequent occurrence? Does it typically happen with data in /var or >>>>> data that is more likely to be kept in a pool other than rpool? >>>>> >>>> >>>> It seems to be very infrequent, and there are other options, such as >>>> the apache/apache2 scheme, that allow you to perhaps create a new >>>> configuration based on the existing without disturbing the existing. >>> >>> On what basis do you say "very infrequent"? >>> How many 3rd party applications have you surveyed? >>> How many 3rd party applications that use /var have you surveyed? >>> >> >> On the basis of the proposal, which is for a limited set of things >> that have been quite stable over time to be moved into the shared dataset. > > Having read your response, to me it sounds like there has not been > enough research to warrant the entirity of /var being shared and that > Sanjay's proposed approach (of making known, safe, data shared) is a > much wiser approach. >
That is the approach we are proposing. Nothing I have written is meant to advocate or imply otherwise. Dave
