Quote:
Originally Posted by yifanlu
Could you give an example of rootfs usage other than copying an init script? I would rather manually implement anything that requires access to rootfs than let all scripts modify it. That's one of the main problems I have, after a while, I don't know what files on thr FS are modified. Especially since I lost the uninstaller scripts.
|
For example the freedownload hack needs to modify /opt/amazon/ebook/config/wrs.ini, the localization hacks need to inject translation strings into /opt/amazon/ebook/ JARs, the webpatch hack needs to replace libwebkit.so .
I admit everything can be done with mount-binds instead of root fs modification and many hacks do it like that. Couldn't even the jailbreak just mount-bind the keys instead of overwriting them ?
Nevertheless, the package system should provide an API (shell functions) to make the root fs modification/mount-bind-overlay easy, safe and traceable.
Actually you can't stop anybody from modifying the root fs but at least you can offer hackers a convenient API that allows them to do it properly.
All changes to the root fs would then be registered in one place and there would be a generic restore-all procedure.
That's way more important than the install.sh and uninstall.sh hooks.