Notices

Ok now it works.

I have tried before with a symbolic link to tar and it hasn't worked and then with real copy and it has worked.

Published the correct guide here : http://talk.maemo.org/showpost.php?p...&postcount=197

Mind you, the tracking isn't being done device side - it's being done server side. You can always "opt out" by closing the window before it connects, or install it manually, or install it with internet access off... But hey, if you want to have a nice easy-to-install method, it's not like it costs you anything. :P
Also, I honestly expected a *large* backlash when I first released it a version ago. Yet you are the first person to comment negatively on it - I've had several people come up to me proud of the fact they are one of the ones counted.



Symbolic link wise, of /course/ it doesn't work. Original file is in the Optfs, which *isn't mounted* when BMLauncher is run. So it has to be copied somewhere on the rootfs(and symlinked if it's not in my folder) to work!

Hey, personally, I don't have anything against fact, that my device send a info about installing Your program. Ho ever, I just stand on position that every user - even if he is not "tinker" should for 100% know that this gonna happen after installation. Just as good practice.

I really don't imply that you're harming anyone by any means. Still, informing in package description doesn't harm either, and promote 100% clear way of doing things like that

---

Fabry, many thanks for it! Was waiting for guide like that for ages, recently even to the point of moving my a** and trying to figure it out myself Thanks to You, I don't have to.

Sure, I'll put it in the package description; why not. I didn't really know of a good place to put such info, and aside from actually *asking* the user(which I'm betting lots would say no, just because it's a question) I wasn't sure where to put it. So yea...

Speaking of which, I've passed 650 installs of 1.1, and I got my first donation($5) in months! :P

thanks again for your work, couple of suggestions here:

can you please add an option in the menu to continue booting / return to bootmenu/multiboot?

it's basically reversing what you did at the start:

killall udevd # this is important !!
mountroot
busybox pivot_root /tmp/mnt/rootfs/ /tmp/disk/
exec chroot /tmp/mnt/rootfs/ ash /sbin/preinit

executing /sbin/preinit will either boot maemo or launch boot menu or multiboot depending on which is installed and the keyboard slider state.

I have tried this with multiboot installed.

there is just one problem with the maemo boot up process, when rebooting maemo doesn't always start, due to DSME or BME shutting down for some weird reason, same applies here, some times maemo starts, some times it just shutdowns, I will try finding out how DSME state gets set during bootup.

also please comment out the line which keeps echoing the battery state in charge.sh script (last line), it makes the terminal harder to use.

one last thing, about the menu becoming unusable after returning from the terminal, once it's quit you can clear the screen and use printf to print the menu items to the console instead of text2screen.

thanks in advance.

First bit, that's very useful, thanks!
Hm... When you switch to R&D mode, a number of things happen differently. I wonder if it'd be possible to create a "virtual" R&D mode from within BM, by setting a few variables or somesuch?


I'll change it from echoing status to echoing it into a file, so you can check if it's running. When I setup that script, i had no idea that'd actually be seen in BM :P

As far as using printf... Not really. It's a good idea, but it'd involve(at least) two sets of text lines, doubling the size of the file.
I could switch to printf completely... but that would exclude users of the stock kernel - not something I want to do.

This app is the best, thanks Robbie!

wen i rouched the top menu bar line i can see only two applets in my n900 i.e volume option and battery percentage option... i cant see the all applets like fm transmetter,shortuts,internet,clock,bluetooth etc... the default also went off...how to get it back

+1 please! (for bootmenu -- I don't personally use multiboot)

This is a useful tool. But on my test N900 I make heavy use of bootmenu to boot various roots which I keep on SD cards (so I can easily test installing my packages on PR1.1, PR 1.2, clean systems, replacing various older versions of my software, with different configurations, etc). The features in BackupMenu would be useful to have available but I would only use them rarely: I would really like to have BackupMenu available as just another option from my bootmenu, instead of replacing it.

I *may* be able to get it to continue booting - Preliminary testing with ivyking's 4-line "patch" only gets me "Kernel panic - attempted to kill init", so I'm obviously doing something wrong as of yet.