An example, I installed openbox and window switcher on Slacko 5.3.3, restarted x-windows, and got, "sorry, your window manager is not configured, cannot load your window manager, you're out of luck." What? Configured....? Good thing I had pupsave backups.
At least ms windows says, "cannot load windows, do you want to load your last good configuration?" Seems like that would not be hard to implement in puppy.
Incompatible Pets/SFS's
Seems like it would not take much to, say, prevent installation of an incompatible SFS or PET. At least a couple ways:
- all pets/sfs's could have a tag or property indicating which puppy versions they are known to work with. On attempted install, alert user if their puppy version is not known to be compatible.
- have a 'catch-all' menu, where launchers are placed if a pet/sfs tries to write to a menu that does not exist.
- installers make other changes to the OS. Puppy should be "aware" of what the installer is doing, and alert user if the installer is trying to do something inappropriate.
Many of us do manual backups and restores of the pupsave. Would love to see that automated (with manual option). Could be combined with "Last Known Good", above. I compress my backups, since they do compress so small. Even more space could be saved by making them incremental.
http://murga-linux.com/puppy/viewtopic. ... 862#629862
http://murga-linux.com/puppy/viewtopic. ... 865#629865
I think these sorts of protections could help expand puppy's userbase to mainstream, non-expert users-- if that is a goal.
What other breakage-protections and fool-proofing can folks think of?
----
asus eeepc 1001PXB
2x Intel(R) Atom(TM) CPU N450 @ 1.66GHz
2064MB RAM, 1024x600 Display
Detailed HardInfo: https://sites.google.com/site/johnywhy/my-asus-pc
Thank you for Puppy!