Notices

Sorry to hijack the discussion concerning pin number and encrypting. I wish to suggest another feature, namely reformatting the optfs from within backupmenu. I know there is the possibility to erase all files on it, but this cannot handle the case when the filesystem structure is really damaged. So, alongside with erasing files, could we have also a mkfs.ext3 command?
I'm asking because this morning I had to reconstruct the optfs this way from an external ubuntu machine connected through usb, in backupmenu's w mode (read/write mass storage mode) before restoring the optfs. The ext3 filesystem was damaged (due to my silly experiments ) to the point it was impossible to write on it unless it was reconstructed from scratch.

Such a command could save from a number of emmc reflashes, too.
Thanks, Ernesto

I figure I'll add that along with parted; I need the package in extras-devel, though.

I've just uploaded Version 0.60!
This version has support for charging(from a wall-charger, and probably USB as well).
It's also had it's loader rebuilt, and this new version should provide more feedback if things go wrong.
You can download an early copy from my website: http://robbiethe1st.afraid.org/Backu...0.60-1_all.deb

I installed backupmenu-multiboot and, of course, my backup menu is left behind. Is there any decent way to keep to date save for waiting for updates to propagate?

Can they ever play nice? Say, BackupMenu could detect multiboot and live together?

I like the multiboot version because it allows me to fallback-boot to stock kernel in case stuff happens. Also, at some point, I intend to go for NITDroid.

To be honest, No.
I don't believe in Multiboot, due to it being a dangerous hack. I suggest asking some people in #maemo if you don't believe me.
If someone gets uBoot working nicely, I will migrate to that instead, and that will provide multiOS the -right- way.

Another option is to use bootmenu-n900 as your launcher, you can bring the default menu back simply by editing /etc/bootmenu.d/backupmenu.item appropriately - Make it a valid bootmenu item file.

Hi RobbieThe1st,

after updating backupmenu from repo I had some weird issue. First point was that desktop didn't react at all any more. Application manager was still working and buttons also still worked, the device also put itself to slepp after a while, but no reaction on desktop. So I decided to restart. After it was running again, I first plugged in USB cable from PC to copy some stuff but N900 only asked whether to go to storage mode but didn't charge. Then I plugged in the wall charger and it just didn't react at all to it. I switched device completely off and then plugged wall charger in again and it booted correctly and loaded the battery. After some ten minutes I plugged off again, waited til device was completely shut down and powerd it up again. now it uses wall charger again.
Maybe some stuff with some libs you are using?

It is not a question of belief, it's just that as a non-Linux user I see no difference between them. We don't have that problem in Windows land, there's one boot loader, and there's a configuration file everyone adds to (boot.ini). Also, there are few issues as all installers newer than 10 years are aware that there are others in that file and correctly adjust. Plus, N900 doesn't have the ability to rescue-boot off a CD and press Enter to fix everything.

Personally I had no issue with uBoot (it's the one that came with Power Kernel 44 or so, with the little penguin, right?) but who knows.

I'll try to document on Multiboot, but frankly, I should be a user, and users shouldn't be grepping developer mailing lists trying to determine which one of the main Kernel contribuitors is right about swappiness.

Oh well.

Thanks for the reply.

since some weeks I get the error on the software-update:

What can I do ? After the last Update of BackupMenu there is no longer the blue screen with the BackupMenu to see.

Update

I uninstalled backupmenu and bootmenu and installed it new. The normal backupmenu-menu is still not there.

Update2
After:
apt-get remove --purge backupmenu
apt-get remove --purge bootmenu-n900

and reinstall the 0.56 Version:
http://robbiethe1st.afraid.org/BackupMenu/

Its to old working one.

@x-lette:
I'm not sure how that could be caused by my app - Nothing of mine runs when Maemo is running - It's -only- run when boot with the KB open.
Possibly one of your other extrtas-devel apps broke it?

@ndi:
The real problem is that multiboot flashes the kernel partition each time you want to boot something different. This partition has no wear levelling, and that -can't- be good for it.
bootmenu-N900 just hijacks the normal Maemo boot.
uBoot requires a custom kernel, IIRC, but only needs to be flashed -once-, and not each time you want to change your booting OS.

@michaelxy:
Hm. Odd.
Now that you've got 0.56 on there, can you try upgrading to 0.60? Let me know of any errors and what screens you see them on.

As always thanks for the update, but it has stopped working on my device

boots like this:

'loading boot menu'

'udev started'

then a boot menu with my internal partiton and not much else