View Single Post
joerg_rw's Avatar
Posts: 2,222 | Thanked: 12,651 times | Joined on Mar 2010 @ SOL 3
#1242
Hi RobbieThe1st,

I wondered if it's high time to implement a logic into BM restore that checks kernel in /dev/mtd3 against any kernel modules in a backup about to get restored, and WARNS resp offers an option to not restore kernel modules if they don't match.
We seen zillions of users ending with a complete reflash and even maybe not able to restore at all (due to lack of proper guidance how to proceed) just because they did a BM backup and then installed powerkernel or uBoot. I think it should be rather easy for BM to test for and catch those problem cases, and even offer proper guidance:
Code:
PROBLEM during RESTORE detected:
Your system has kernel foo but backup has kernel modules for bar, which will most likely conflict and render your system unbootable!
Do you want to 
a) exclude the bar components from restore (may or may not work)
b) abort the restore and replace your foo kernel by bar manually, then restart the restore  (recommended)
c) ignore the conflict and restore anyway, probably risking a bootloop? (you should know exactly what you're doing to choose this option)
What do you think? If you plan to implement such function, don't hesitate to ping me for help.
Many thanks for what's undoubtly the most useful and important app on fremantle ever :-)

cheers
jOERG
__________________
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member

EX Hildon Foundation approved
Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/

IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N
 

The Following 14 Users Say Thank You to joerg_rw For This Useful Post: