Notices

Hm, this is interesting, because this is exactly what it used to do to me, which was why I only recently updated the bootmenu module to work with backupmenu "correctly".

Try a apt-get update && apt-get upgrade, see if it still does it after upgrading to 1.2.

My primary n900 is running battery drain tests at the moment, so I do not wish to interrupt them by rebooting.

I can report a couple things...

My backup n900 (clean PR1.3) installed and ran backupmenu-1.2.0-1 just installing from HAM.

Restoring/cloning this n900 with root/opt images from my primary then "apt-get remove --purge backupmenu && apt-get install backupmenu" to get backupmenu-1.2.0-1 installed worked successfully (able to reboot and inspect backupmenu's backup/restore items in bootmenu).

I will update this with results from my primary n900 in a few days.

Update...
My on my problematic n900, I ran "apt-get update; apt-get remove --purge backupmenu && apt-get install backupmenu" to upgrade to backupmenu-1.2.0-1. This worked successfully.

I had the same problem as you with the newest versions of bootmenu and backupmenu - that the device would shut down shortly after loading backupmenu. I did this same purge and reinstallation and can confirm it worked. Backing up as we speak!

Ah, /that/ makes sense - It's considering the /etc/bootmenu files to be 'config' files, and thus won't overwrite them. However, well, we need them overwritten...

Thank you for the program. Can i change background to black and text to white?

So, after a rather large mess, I have a small request.

Can you setup an option so that after a backup (or restore) completes the device will auto-reboot? I ask this because I went to do a full backup, then forgot about things since it takes sometime, and 3 hours later returned to a dead device and a corrupted backup.

Having it auto-reboot would allow one to setup a backup at night, plug it in, and when it finishes it can just reboot and start charging again.

For a while now I've been meaning to suggest a it plays sound when a long operation has completed.

The reboot thing should be an option if it is implemented, because there are times when it's unhelpful. Case study:
The first time I tried to install CSSU-thumb the device refused to boot into maemo. Luckily I'd already backed up, and could restore my backups, but I still needed to flash the kernel before I tried to reboot.

I am struggling in backing up my 10GB optfs to an ext3-formatted sdcard. Is this supposed to work at all???
The menu offers to backup to the sdcard as it would to a fat-formatted card, but the tar process is not starting.
Or is it starting in the background, but not providing visual feedback?

Just restored a backup and it took forever (almost :-) ). The problem was timestamps of files lying in the future. Is it necessary to check for timestamps and log them as error?

They're just logged, but shouldn't affect speed. I've been restoring backups on devices with wrong time (due to internal battery keeping clock alive is discharged in most N900's now) and it was never slower due to errors - they just look scary unless You read their actual content

Anyway, I agree, that completely ignoring timestamps error wouldn't hurt.

/Estel