We can look into it, my guess is that an existing script now has new and/or different parameters. Perhaps it could be adjusted to be backward compatible so people can reboot at their leisure. All just guesswork. On Mar 27, 2013 9:21 PM, "Marcus Sorensen" <shadow...@gmail.com> wrote:
> Hard to say. Sometimes functionality/implementation changes even though > the feature is the same. > On Mar 27, 2013 9:20 PM, "David Nalley" <da...@gnsa.us> wrote: > >> On Wed, Mar 27, 2013 at 11:13 PM, Marcus Sorensen <shadow...@gmail.com> >> wrote: >> > Just to clarify a step further, this should have been the case with 3.x >> to >> > 4.0 as well. We had all of these new vpc scripts that added brand new >> > functionality that needed to go on the virtual routers. The system VM >> > template stayed the same, even though new scripts were added via >> > systemvm.iso. >> >> >> That said, why would new functionality make existing functionality >> stop working in a system VM. >> >> --David >> >
