MobileRead Forums - View Single Post

ericshliao · 10-24-2010, 03:53 AM

I see that people are concerned about how to survive their iLiad even after iDS goes down, so I am going to share some of my thinkings here.

1. Backup your iLiad.
If iDS goes down, we can't update FW anymore. So, making a backup of your iLiad is quite important.
The most important files resides in /usr , /mnt/registry, /home. Command "tar czf" can be used to create a compressed backup of files.
Developer's package (shell access previlege) and mobipocket reader are also affected if iDS goes down. They are explained in the following.

2. Install developer's package and backup registry.xml so that shell access right can be re-installed when doing a re-flash.
The so-called developer's package makes it possible to install non-official software. In fact, when we retrieve a developer's package from iDS, it just adds an entry to "registry.xml" to enable shell script can be executed through ContentLister. At boot-up, ContentLister reads "registry.xml " to find the appropriate application to launch when certain document is tapped by users, eg, ipdf for ".pdf", mobi_reader for ".prc" or ."mobi". Only after developer's package got installed, files with ".sh" extension can be executed through ContentLister.
According to some other thread, when doing re-flash, putting "registry.xml" in CF will copy it your iLiad. So, having a backup of "registry.xml" after developer's package installed is a must-have.

3. Backup Mobipocket Reader.
IIRC, the reflash content from iRex does not include Mobipocket Reader. We have to get it through iDS. If iDS goes down, out iLiad will lose mobipcoket reader after re-flashing.
Mobipocket Reader and Tao's JVM resides in "/home".

I wrote the above text by my memory. I can't be sure if they are all correct.

10-24-2010, 03:53 AM	#12
ericshliao Guru Posts: 976 Karma: 687 Join Date: Nov 2007 Device: Dell X51v; iLiad v2	I see that people are concerned about how to survive their iLiad even after iDS goes down, so I am going to share some of my thinkings here. 1. Backup your iLiad. If iDS goes down, we can't update FW anymore. So, making a backup of your iLiad is quite important. The most important files resides in /usr , /mnt/registry, /home. Command "tar czf" can be used to create a compressed backup of files. Developer's package (shell access previlege) and mobipocket reader are also affected if iDS goes down. They are explained in the following. 2. Install developer's package and backup registry.xml so that shell access right can be re-installed when doing a re-flash. The so-called developer's package makes it possible to install non-official software. In fact, when we retrieve a developer's package from iDS, it just adds an entry to "registry.xml" to enable shell script can be executed through ContentLister. At boot-up, ContentLister reads "registry.xml " to find the appropriate application to launch when certain document is tapped by users, eg, ipdf for ".pdf", mobi_reader for ".prc" or ."mobi". Only after developer's package got installed, files with ".sh" extension can be executed through ContentLister. According to some other thread, when doing re-flash, putting "registry.xml" in CF will copy it your iLiad. So, having a backup of "registry.xml" after developer's package installed is a must-have. 3. Backup Mobipocket Reader. IIRC, the reflash content from iRex does not include Mobipocket Reader. We have to get it through iDS. If iDS goes down, out iLiad will lose mobipcoket reader after re-flashing. Mobipocket Reader and Tao's JVM resides in "/home". I wrote the above text by my memory. I can't be sure if they are all correct.