Quote:
Originally Posted by knc1
Simple actually,
You change the file system setup so that to the machine it is OTG exported to, it looks like (and is) VFAT;
While it looks like (and is) an inode file system to the Kindle.
Also, the same system can be mounted by both machines at the same time without conflicts.
I will put writing up that "HowTo" on my to-do list but don't anyone wait for me to get it finished, no ETA possible, too busy with other things.
@GM: You go ahead and do the that write-up yourself if you want to, it will be sometime before I can get around to it.
|
That is outside my experience. I was not aware that this COULD be done. But knowing that something CAN be done is usually all it takes for me to figure out HOW to do it once I apply myself to it. It sounds like you are suggesting some sort of dynamic translation layer (or whatever terminology is used for this process). My problem is a lack of time, which will get worse soon... Big things happening here...
EDIT: If you are suggesting that the /mnt/us partition be formatted in a non-vfat (inode) format, the startup scripts would fail to mount it because they force the type to vfat. They automatically reformat the USB drive and repopulate it from /opt if they cannot mount it. Your solution may work until you reboot, but then it would get reformatted as vfat. Of course, you can alter the startup scripts and config files, but that could cause OTA updates to fail. There may be additional complications to deal with as well. It would be a lot safer and easier to create these symlinks in /tmp as needed, instead of changing the usb drive format to support symlinks. And your suggestion to export an "inode-formatted" usb drive as a fake vfat drive would not work when exporting the drive from the diags menu or from serial port recovery mode. Making deep changes to the main and diags linux kernels and boot partitions to support an "inode" usb drive in recovery modes could also break OTA updates.