On Mon, Mar 9, 2015 at 11:50 AM, Tom Metro tmetro+...@gmail.com wrote:
I was looking to do a dry run test with do-release-upgrade to see if a
system could successfully be upgraded from 12.04 to 14.04 after some
changes had been made. (An earlier attempted failed to map packages from
the old
I was looking to do a dry run test with do-release-upgrade to see if a
system could successfully be upgraded from 12.04 to 14.04 after some
changes had been made. (An earlier attempted failed to map packages from
the old release to the new release.)
do-release-upgrade doesn't have a dry run
Tom Metro tmetro+...@gmail.com writes:
I was looking to do a dry run test with do-release-upgrade to see if a
system could successfully be upgraded from 12.04 to 14.04 after some
changes had been made. (An earlier attempted failed to map packages from
the old release to the new release.)
...
On 03/09/2015 11:50 AM, Tom Metro wrote:
I was looking to do a dry run test with do-release-upgrade to see if a
system could successfully be upgraded from 12.04 to 14.04 after some
changes had been made. (An earlier attempted failed to map packages from
the old release to the new release.)
On 3/9/2015 4:03 PM, Matthew Gillen wrote:
I think I'm convincing myself that if you want to roll back, use VMs.
/boot is too complicated to deal with.
No, you have the right idea. It's possible to roll back with LVM but the
problem with this is that you /must/ eventually roll back or
Tom I would not trust the sandbox feature for reasons you outlined.
I have managed multiple versions of multiple distros for a dev workstation
using lvm. it is by no means painless. I did learn the grub2 command line.
It is not a painless plan!
*A much better plan is to make a copy onto new
