Issues specific to upgrading to the latest version. To be updated so as to always address the latest version of Puppy as new versions come out. Especially issues re upgrading from the penultimate version of Puppy to the latest.
Boot the new CD and Puppy will automatically perform any required upgrading of your personal storage file/partition (usually pup_save.2fs file).
Upgrading a multi-sessionLiveCD
???
Upgrading a Full hard drive install
In the Normal Full Install Puppy Linux is being installed to its own ext2 or ext3 partition on the hard drive.
Some Caution should be observed during this process. Read the release notes!
Back up any data you wish to save. Its better to be safe than sorry.
Boot the computer from the latest Live CD of the Puppy you wish to upgrade to.
Type "puppy pfix=ram" at the prompt.
The Live CD will ask you to configure the Keyboard and Monitor settings. Once you see the initial Puppy Desktop perform an installation as you would with a normal install to HD.
EXCEPTION
During the installation you will be given the option in a dialog box to UPGRADE or WIPE.
Click on UPGRADE. Follow the rest of the steps as you would with a normal installation to HD. Be patient even though it may seem like nothing is happening the upgrade is proceeding. Eventually the prompt to install Grub will appear.
When you are finished configuring Grub and you are returned to the desktop, shut down the Puppy Linux Live CD session and do not save the live session.
Reboot the computer, eject the cd, and launch Puppy from the HD using Grub.
If you are successful, all your data and settings should be untouched.
Delete the pup_217.sfs and zdrv_217.sfs off the hard drive.
Then either:
Boot the 2.17.1 CD with this option:
pfix=clean
or
Set /etc/puppyversion back to '216' before rebooting.
Upgrading from alpha or beta versions of 2.17
It is extremely important that you get rid of any old pup_217.sfs and zdrv_217.sfs files that may be found alongside the "pup_save" file on the hard drive (in /mnt/home).
Boot an old version of Puppy or a different operating system to do this -- or, you can boot the new CD with the boot parameter:
puppy pfix=ram
After you have removed these old files, boot Puppy 2.17 live-CD and type the boot parameter
puppy pfix=clean
so that a proper upgrade of the latest version will occur.
If you want to be extra cautious, make a backup of the pup_save.2fs file before upgrading!
Puppy 2.15CE to 2.16, to 2.17 - Mail and internet conneciton settings were retained. No personal data was lost.
Upgrading Previous Versions
Issues specific to upgrading yet older versions.
Some cautions should be observed during the "Normal" "Full Install" to Hard Drive Upgrade between versions. In the Normal Full Install Puppy Linux is being installed to its own ext2 or ext3 partition on the hard drive.
Puppy 2.15 to 2.16, to 2.17 - Observed minimal or no apparant negative consequences of the upgrade. Mail and internet conneciton settings were retained. No personal data was lost.
Puppy 2.xx to 3.01 - Observed minimal or no apparant negative consequences of the upgrade. Mail and internet conneciton settings were retained. No personal data was lost.
Recommendation -
a. This is the first slackware compatible version of puppy. There are enough improvements to make a full installation using the "Wipe" option worthwhile. Backup mail and data and use "Wipe" option during the full installation.
b. Using the "Upgrade" option was successful. Observed minimal or no apparant negative consequences of the upgrade. Mail and internet conneciton settings were retained. No personal data was lost.
Puppy 3.01 to 4.x - Observed that Seamonkey "mail" is replaced by Sylpheed. Mail data appeared to have been lost.
Recommendation - There are enough improvements to make a full installation using the "Wipe" option worthwhile. Backup mail and personal data and use "Wipe" option during the full installation. Note that re-installing Grub, rather than updating it is easier to follow. The Grub "update option" requires the user to make manual textual changes to the menu.lst whereas the re-installation of Grub uses the standard installer.
