Quote:
Originally Posted by j.p.s
The Voyage is JB.
I'm just reporting that the KOA2 has something leftover from the factory, possibly the FUSE equivalent of an NFS temporary file that is a shell script. It looks to me that charging can be turned off by a user even if the battery isn't fully charged.
|
That might not have been shipped with the device.
That might have been put on the device by the factory-only, production line, Q.A. firmware build that you installed in order to jail break it.
The name is misleading.
There is a FUSE system on the device, it is the fuse layer on top of /mnt/us that actually gets exported to USB driver.
But as long as it is running (or anything is running on /mnt/us) the export over USB can not be made.
Which might be part of its reason for being.
The way you wrote your post made it read as if you made the discovery while preparing to jail break it, not after you did.
And yes, the Kindle system is capable of NFS (both client and server).
You can find threads here on the subject.
The Kindles can also do a network boot from NFS in the initramfs system (before flash gets mounted).
Ah, it also does NBD
You can find some posts here where people played with swap over NBD (which really isn't very stable - that arrangement is subject to a deadlock)
OH, and also CIFS (Windows networking).
You can find posts/threads here on that also.
This is how you learn what filesystems the kernel is built to support:
Code:
[root@kindle us]# cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev tmpfs
nodev inotifyfs
nodev devpts
ext3
ext2
ext4
cramfs
squashfs
nodev ramfs
vfat
msdos
nodev unionfs
nodev nfs
nodev nfs4
nodev mqueue
nodev rpc_pipefs
nodev fuse
fuseblk
nodev fusectl
That is from 5.3.7.3, so of course, 5.9.something may be different.
Hmm...
I don't see CIFS on that list -
Oh well, I will not worry about it - this is just a quick example.