[div align=\"right\"][a href=\"index.php?act=findpost&pid=108889\"][{POST_SNAPBACK}][/a][/div]
Can you clarify question 1? you don't need ipktools package and use xipk-link unless you want to build your own cramfs image. is that what you are trying to do? the xqtapps-setup file for example is xipk-link (in fact most of the xqt*-setup files in the various cramfs images are xipk-link renamed.
[/quote]
Actually, I think I'm a bit confused... if I reset the zaurus, the files just need to be remounted and/or relinked? or is relinking done once, and automounting the cramfs image everytime my SD card is removed and plugged in?
My goal might clarify things. I just want to be able to run XQT and the mozilla package off of my SD card at anytime, regardless of if I removed the card and re-inserting it. That is of course with the intent that my cramfs images reside in the same directory all the time on the SD card.
I've used your automount before it works, but a few times, the sd card did not wake up from suspend, so I uninstalled the automounter. Is this the automounter or a problem inherent to the zaurus or SD card?
Thanks in advance,
Carl
[div align=\"right\"][a href=\"index.php?act=findpost&pid=108947\"][{POST_SNAPBACK}][/a][/div]
[/quote]
The install script will mount the cramfs images and link the files.
Each time you insert or eject the SD card, you need to mount/unmount the cramfs. You do not need to relink again. Also, you need to mount them again after you reboot.
This is all done for you if you have automounter installed (it works on the sharp rom, but disabled the auto mount and unmount of the SD for cacko since its done differently).
The Z will force an unmount of your SD when you suspend. So it should also unmount the cramfs before unmounting the SD. This is OK normally except when the cramfs is in use and cannot be unmounted, ie you are running some X application which is keeping a lock on its files.
When you resume, it normally remounts your SD and then the cramfs, but if it was in a dead lock situation when it suspended, the file handles/locks would had been forcibly killed, but the application would still be in memory and trying to use its existing file lock which doesnt exist anymore. All you need to do is kill the rogue process. A better solution would be to exit all the apps on the SD before you suspend.