Originally Posted by DaSilva (Post 756579)

Do you plan to release this nice script to extras-devel which makes it easier to stay up2date and to install it?

Originally Posted by RobbieThe1st (Post 756443)

Sounds like there's an error in the code - Make sure that you -save- my file(right-click, save-as) versus opening it and then saving it, or copy-pasting the contents into a file.
Just get a new copy from my link in the first post, try again. If its still giving you trouble, let me know.

Originally Posted by RobbieThe1st (Post 756586)

Actually, yes. But I'm not entirely sure how to make it a package - especially since all it is is a file that needs to be copied to a certain location. I've seen a couple of tutorials, but they were all vague and talked about setting compile options etc for the (source) code inside...

Can one of you nice people show me a quick way to do it?

Originally Posted by Dany-69 (Post 756661)

Perfect :)
Now it work :D
But i have a question ... Where the kernel is allocated? In the rootfs?? Or somewhere in some chip? o.O

I'm going to flash my n900 (with Titan kernel) with the fiasco image...infact i want to try to restore e backup just made through your script... But flashing with the fiasco image even the kernel should be flashed...

And, if it isn't allocated in the rootfs, i think there should be some problems restoring the system with the backup created with the script... because the system "thinks" to have the power kernel .. there are configuration files and even some files that serve to deinstall the kernel...

So how it works? o.o

PS: excuse me for my english .. :(

Edit: infact the kernel can be flashed even with the maemo-flasher... so i think it isn't in the root.... :/
How can we solve it? I have to deinstall the kernel e do the backup again?

Originally Posted by zement (Post 756693)

actually i don´t believe that this is the correct way (flasher -r "raw rootfs image" from PC) for recovering rootfs.

i tested the szenario on my device and my test ended up with a bricked rootfs. so i did some research and found that the correct format of flashing rootfs in this case (=from PC) is ubifs!
conclusion: i have to convert the raw image into ubifs format for successful flashing of rootfs via PC according to this post
can anyone confirm this conclusion or post his success story including all steps (flasher -r..)?

greets

Originally Posted by RobbieThe1st (Post 754837)

Since before I got my N900 a couple weeks ago, I've been trying to figure out a way to backup and restore a full OS image on the N900.
With a PC, you can use a program like Norton Ghost, or any number of free alternatives, and make a full image of everything you have. You screw the OS up, all you have to do is take your backup image, wait a couple hours for it to load, and you have everything back to how it was before.

With the N900, all you have is a "settings backup" tool(which also keeps a list of installed programs). If you have custom applications or settings -not- backed up... Good luck.

Until now.

I have created an application which allows you to make full backups of the RootFS(OS), and OptFS(extra programs), and then restore said backups. These backups(at least the RootFS ones) are also compatible with Nokia's Flasher utility, so you can restore directly, if you manage to make your N900 not even boot.
Do note that this is a bootloader-based application(backup not possible with the full OS running), so you have to reboot the N900 to use it.

Screenshots:


How to install:
1. Install 'bootmenu-n900' from the extras-devel repository.
2. Download BackupMenu.item and copy it to "/etc/bootmenu.d/" on your N900(requires root).

How to use:
Reboot the N900 with the keyboard open.


Notes:
I have, occasionally, run into restore errors when restoring the RootFS. If things are majorly F'ed up(and I have done it a lot), sometimes it won't restore to a bootable condition.
In these cases, you need to:
1. Using the Flasher, flash the PR1.2 FIASCO image("flasher-3.5 -F *imagename*.img -f")
2. With the N900 still in flashing mode, flash your RootFS image with the flasher("flasher-3.5 -r rootfs-image.img -f")
This has solved the problem in all cases.

Originally Posted by PipoXtreme (Post 757126)

sorry I'm a noob in this case how I can swap this script / item to desktop.d ??

Originally Posted by RobbieThe1st (Post 757536)

Bit of an update: I finally figured out how to deb-ify my script! Now you can install it via a .deb package.

I also applied to be able to upload to extras-devel, so hopefully in a couple of days it will be up there, for your easy-update pleasure.

Edit:
Gees, this stuff's complicated. I got access to Extras-Devel, but now I need a .changes file, and apparently I can't upload the .deb file I made using this howto...

Originally Posted by Bratag (Post 757870)

Robbie. I am running into conflicts between bootmenu-n900 and multiboot (for NIT). Do you know if your app is compatible with multiboot?

Originally Posted by RobbieThe1st (Post 756545)

I just took a look at it - it probably -won't-, at least not by copying it into /etc/multiboot.d/.
You can -probably- get it to work the same by:
1. at the boot prompt, press C for console.
2. type "/path/to/BackupMenu.item"
If that doesn't work, make sure its marked as executable by running:
"chmod +x /path/to/BackupMenu.item".

Now, someone well versed in writing item files for MultiBoot -might- be able to convince it to drop to a shell and then excecute it, but I can't do it.

Either way, go ahead and experiment - Though the latter is fairly unlikely.

-Rob