Quote:
Originally Posted by sam.vanratt
Wouldn't it be reasonable to create swap with fdisk (or as a file) and then enable swap via fstab instead of userland workarounds?
|
You are writing about one of the early generation (prior to touchscreen) Kindles.
Updates where incremental, there was (still is but unused) a system manifest with a list of the files and their md5sum.
If one of the update fragments found a file (such as fstab) different, the update would fail and most likely the device would brick.
That used to be 80% of the traffic on this site - how to un-brick a Kindle.
Ah, the post I replied to DID create the swap area as a file.
The mention of fdisk implies making the swap area as a partition.
There are other "sanity checks" during the boot-up process that would fail if the storage partitions where not as expected.
Just another way to brick the device.
SO:
Put the file (of all zeros) on /var/local (which is always available, unlike the fuse exported area),
run mkswap on it,
manually run the swapon/swapoff as required.