If you boot into the new tree and determine that something is wrong, you can invoke .
One of the major goals of the OSTree project is that operating system content should be versioned and integration tested together.
Having said that, there were always processes you could follow with varying levels of success (based on straying from the official repositories and how customized your setup and package list was).
We have run through this process now about a half dozen times, with varying levels of success, so let’s talk about some of the successes and failures.
Open a command prompt and type the following to see output similar to what we show below: $ sudo preupg Preupg tool doesn't do the actual upgrade.
Please ensure you have backed up your system and/or data in the event of a failed upgrade that would require a full re-install of the system from installation media. y/n y Gathering logs used by preupgrade assistant: All installed packages : 01/10 ...finished (time s) All changed files : 02/10 ...finished (time s) Changed config files : 03/10 ...finished (time s) All users : 04/10 ...finished (time s) ...
default) repositories as the only method of installing software works most of the time.
It neither performs the upgrade nor helps you mitigate any of the issues that it finds.042/100 ..(samba shared directories selinux) 043/100 ..(CUPS Browsing/Browse Poll configuration) 044/100 ..(CVS Package Split) ...|samba shared directories selinux |notapplicable | |CUPS Browsing/Browse Poll configuration |notapplicable | |CVS Package Split |notapplicable | ...It’s pretty obvious that this is something entirely new for the Cent OS maintainers and like anything else, is going through growing pains.Let’s ignore all this for now and walk through the official process of completing the upgrade. On a freshly installed and then updated to latest version copy of Cent OS 6.5, you run a program that will scan your system and determine what your upgrade status is (called the Preupgrade Assistant).