Erm, sure, but it wouldn't be much usable for anyopne except me - those are things like making ext4 instead of ext3 during partition recreation, mounting as ext4 instead of ext3 while doing backup, (both because I was too lazy to modify backupmenu a way that would make it detect filesystem used and ask which one to create while restoring) charging via kernel-power module bq2415x_charger instead of i2c scripts, etc. Ah, and while using compressed backup, lzma'ing it instead of .tar.gz (smaller filesize). Frankly, I don't even completely remember what I've modified, and did everything to custom, so it wouldn't be too wise to throw it at anyone. For sure all my changes are kernel-power-only compatible. Also, I've sent one of my first changes (in regular backupmenu form, not dependent on kernel-power) to robbiethe1st, ages ago - it was the lzma thing. He never included it, so I wasn't much motivated to keep compatibility with "upstream" backupmenu --- In list of things that I would like to do One Day When I Got Free Time(tm), (which is, probably, something about 40 years in future... Maybe.) is to rewrite Backupmenu entirely dropping text2screen, using framebuffer output only - loaded even earlier than current Backupmenu (as The Very First Thing[tm] in /sbin/preinit, like Mentalist Traceur's recovery console, which I'm using, too), with CL interface. Until that, I'm anyway using only backup, restore, and recovery shell functions from backupmenu (issuing fsck's from recovery terminal, as I was too lazy to modify backupmenu's fsck scripts, too), and in case of something broken earlier, a preinit recovery console, mentioned earlier. /Estel