Excellent, thank you! On Tue, Nov 20, 2012 at 4:42 PM, Rob Weir <[email protected]> wrote:
> On Tue, Nov 20, 2012 at 4:07 AM, Zack Glennie <[email protected]> > wrote: > > The Apache pages warn against running Dev-AOO on a production machine, > and > > suggest a spare computer or virtualization through Virtualbox. > > > > In my current situation, core OS corruption would be inconvenient but not > > disastrous. I am tempted to just run Dev-AOO directly. If am comfortable > > doing this if the odds of OS corruption are less than 1% per week (or, > > around 1% per 10 hours of using AOO). > > > > OS-corruption would be very rare. More likely would be corrupting > your AOO install. When this happens a normal uninstall of the > application may not work. You might need to manually clean up the > installation, delete the OpenOffice profile directory, etc. Using a > VM makes this kind of cleanup trivial, since you can quickly roll back > to a clean OS image. So you are always starting from a well-defined > state. > > Occasional problems you'll run into are AOO crashes and writing out > corrupted documents. That is why you want to avoid doing "real work" > on a test build. You don't want to risk editing important personal or > business documents on a test build. > > > So, given this level of risk tolerance, should I install Dev-AOO > directly? > > > > I think the risk of OS corruption is very low. > > -Rob > > > > Zack > > > > -- > > tel:+972 054 2914692 > > http://zglen.com > -- tel:+972 054 2914692 http://zglen.com
