MobileRead Forums - View Single Post

knc1 · 08-04-2014, 09:22 AM

With the intent of installing **binary** packages from a standard distribution in a non-standard place, the Kindle's non-writable /etc directory needs to be dealt with.

Note:
The Kindle's /etc directory **can** be written too, but we don't want to alter Amazon's portion of the system image.

One possible answer to be investigated:
http://www.openadk.org/docs/html/man...on_file_system

- - - - -

Our previous and current Kindle add-ons usually handle this situation by copying the original contents to a directory in the user storage sub-tree and then "mount -bind ..." that back over the source directory.

Over time, it has been discovered that the kernel builds provided with the Kindles have a relatively low limit for "-bind" mounts.
It would be nice to avoid that limitation here.

08-04-2014, 09:22 AM	#69
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	With the intent of installing binary packages from a standard distribution in a non-standard place, the Kindle's non-writable /etc directory needs to be dealt with. Note: The Kindle's /etc directory can be written too, but we don't want to alter Amazon's portion of the system image. One possible answer to be investigated: http://www.openadk.org/docs/html/man...on_file_system - - - - - Our previous and current Kindle add-ons usually handle this situation by copying the original contents to a directory in the user storage sub-tree and then "mount -bind ..." that back over the source directory. Over time, it has been discovered that the kernel builds provided with the Kindles have a relatively low limit for "-bind" mounts. It would be nice to avoid that limitation here.