Quote:
Originally Posted by Analogus
I have:
Voyage FW 5.8.7
With this tutorial I got READING-access for the file system. I use a MAC, Transmit as client and Telnet.
I wanted to edit some file in opt/amazon/ebook/...
I struggled with write-access until I figured out to use Telnet:
I startet Telnet in a Terminal-window ' telnet 192.168.15.244'.
Then read the info comming at the beginning:
' Rootfs is mounted read-only. Invoke mntroot rw...'
Ok, typing in the terminal ' mntroot rw' solved the problem! Hurra - writing-access. Problem solved.
Until now... I want to edit this path:
/urs/java/lib/fonts/...
Doing the Voodoo above --> no writing-access. This behaviour is very frustrating for me! 
Any ideas and hints?
Thank you! |
It is the sort of filesystem that it is, not what you are doing.
Linux and MacOSx has the same system heritage, including their file system plan.
Windows is a multi-root file system, each device is the root of its own file system.
*nix systems are a single-root file system, each device holds a file system of its own that can take part in any (other than root**) location of the file tree.
You can see the similarities at the level of the command line (a terminal in MacOSx, kTerm on the Kindle).
**IF** the *nix file tree was entirely on a single device, then changing the r/w permission of that single storage device would change entire tree.
But such a permission of the physical device mounted (anywhere) does not propagate to other devices mounted elsewhere in the tree.
Might sound complex, but that is the simple overview.
One other thing needed to answer your question -
Linux (and probably MacOSx) implements a layered storage system.
One of the (optional, per mount) layers that can be used is a layer that (logically) translates a file into a logical device.
Which allows the contents of that file to be another file system.
The file == a physical storage device
The contents == the file system written on a physical device.
Now, from the above, the script (it is, you can read it):
mntroot rw
mntroot ro
only effects the root of the file system's mount point.
Its effect does not propagate to other devices mounted into the tree.
Now, the answer to your question -
run the command (either MacOSx or Kindle):
Some point along the path:
/usr/java/lib/fonts
will be found to be another file system, with a different backing store (which might be a file remember).
Depending on the Kindle model / Firmware version -
that will be either a cramfs or a squashfs type file system.
A property of those file types is that they do not support write operations.
They can be created, they can be read, but they can't be written (delete is a type of write).
Capture the output of the above command on the Kindle system your interested in -
cut&paste it between 'code' tags here -
someone here will read it and tell you what you have to do to modify files in that part of the tree.
** an over-simplification, but good enough for this purpose.