Thanks for the heads up! I remember experiencing something similar to this too during development, but I can't seem to reproduce it now by:Removing all history files Downgrade to 1.18.5power3 Type some commands (and verify that they're in the history file) Upgrade to 1.19.0power2 Type some new commands which resulted in the new commands being appended to the history file as they're supposed to be. I'd love to hear back from other people whether their history is/was stuck too. If so, I might push out 1.19.0power3 to unstuck the history by some postinst magic. I'm also having an issue with swapoff with the busybox-power 1.19.0 series, which seems to be the result of a parsing error of the options passed to it. However, busybox-power doesn't touch (i.e. patch or otherwise modify) swapoff.c and getopt32.c of BusyBox. If possible, I'd like to receive some confirmation from another busybox-power user (one or two confirmations will suffice) whether swapoff works or not for him/her. If not, I'll dig deeper in this. Update: it seems like something broke upstream: swapoff fails with the same message using vanilla source on my laptop too. The bugreport can be found here. I don't need to receive confirmation anymore regarding swapoff in busybox-power.