TS3.03ce - Prevent accidental version upgrades

[2byte]

To be fair, Puppy 3.01 already addresses this situation to some extent. These tweaks make it almost impossible to bork an existing pup_save. You have to enter 'Puppy pfix=upgrd' before Puppy will upgrade an existing pup_save. This is really handy when you have multiple pup_saves and you accidentally choose the wrong one.

Note. These files are for information only. The init script does not contain MUs bug fixes described here -
http://www.murga-linux.com/puppy/viewto ... 8dac45efea

Tweaks to the init script from initrd.gz of Puppy 3.01 adds the boot parameter 'Puppy pfix=upgrd'

Tweaked isolinux.cfg to increase the display time of the boot screen to 30 seconds.

Tweaked boot.msg to add the new parameter to the boot screen and new wait time.

[ecomoney]

Personally ive never had much luck with the version update process, but Ive often borked up installation files by booting with the wrong disk. I totally agree this process shouldnt be automatic, and should give some feedback. Perhaps an upgrade wizard which makes a renamed copy of the pup_save.2fs file after confirmation?

Good suggestion 2byte

[ecomoney]

Thanks 2byte, this will be very useful. Could you tell me what would happen if the user booted say 2.14r cd with a 2.17 pup_save.2fs file? Also, the would you make the text read

When puppy boots and the first screen is shown, enter

puppy pfix=ram :- to start the computer just from the cd, ignoring the pup_save.2fs file on the disk

puppy pfix=upgrd :- to attempt an "upgrade". Always a good idea to make a copy of the pup_save file first! (Hint: use the option above)

Ive found its a good idea to clear the screen before showing a message like this, as some of the boot messages can be confusing (end users read from the top downwards!). Pizzasgood Pebble bootscreen should help with this, as boot messages will not be displayed by default anyway.