Saving /etc/sysconfig/iptables - Read-only

[sgmoore]

I have a jail-broken Kindle Voyage and when I try to save /etc/sysconfig/iptables I get a message telling me that it is a Read-only file system.

I am sshing into the kindle and then issuing the command mntroot rw which means I am able to write to the /mnt/us folder , but still can not write to the /etc/sysconfig folder.

How do I do this?

[j.p.s]

mntroot rw has nothing to do with writing to /mnt/us

If you can not write to /etc/ after running mntroot rw then it is likely that the command failed because the emmc (flash memory) is failing and can only be mounted readonly.

[sgmoore]

Originally Posted by j.p.s

... then it is likely that the command failed because the emmc (flash memory) is failing and can only be mounted readonly.

Any way I can tell if that is the cause? (I don't get any errors when running mntroot rw.)

If it is failing, does that mean my whole device is likely to stop working soon, or is it possible to keep working in readonly mode for some time?

And why can I write to /mnt/us? I thought they were just different partitions on the same 'disk' ?

(Sorry for all the questions!)

[j.p.s]

/mnt/us is complicated. In mass storage mode it is exported as a FAT format partition. In that mode, I don't think it can be written from a terminal or ssh over wifi. I don't have a terminal installed or use wifi so I don't know. I always have USB networking on and /mnt/us is writable without using mntroot rw.

It is true that all the flash memory is on one chip.

Adding, deleting, opening, paging, and closing books modifies the database /var/local/cc.db and if such changes don't persist across a restart that is an indication the flash memory is wearing out. (New books don't show up, deleted books don't go away.)

After mntroot rw can you do something like
touch /etc/my-test-file

[sgmoore]

Originally Posted by j.p.s

After mntroot rw can you do something like
touch /etc/my-test-file

Weird.
I was able to do this and also running cat /etc/mtab | awk '/\/dev\/root \/ / { print $4 }' said that it was rw and then when I re-tried it a few minutes later it said it was ro!

So I was able to update /etc/sysconfig/iptables by first creating the new file in /mnt/us (no problems doing this via ssh over wifi) and then running mntroot rw and then copying the new iptables file from /mnt/us to /etc/sysconfig/iptables before the system switch back to read only again.

[NiLuJe]

Check dmesg, it'll log I/O errors, and if the kernel actually decided to remount a fs ro because of said IO errors.

[sgmoore]

Originally Posted by NiLuJe

Check dmesg, it'll log I/O errors, and if the kernel actually decided to remount a fs ro because of said IO errors.

No errors!

When I issue the mntroot rw command I get a line added

EXT3-fs (mmcblk0p1): using internal journal

but I don't get anything added when it becomes read-only.