Is it possible to format /mnt/us to ext3/4 to block OTA?

[zaoqi]

At least KT3 could support /mnt/base-us in ext3 format.
I have modified /etc/fstab and used mkfs.ext3, it worked, despite some weird bugs (such as unable to transfer files properly with the computer)
I seem to remember that the OTA update does not support ext3, but I don't have KT3 now, so I can't test it.

[knc1]

Originally Posted by zaoqi

At least KT3 could support /mnt/base-us in ext3 format.
I have modified /etc/fstab and used mkfs.ext3, it worked, despite some weird bugs (such as unable to transfer files properly with the computer)
I seem to remember that the OTA update does not support ext3, but I don't have KT3 now, so I can't test it.

Ah, but you evidently never restarted your KT3 ...
The start-up process will discover the "corrupted" (ext3) storage area and reformat it to FAT32 for you.
(And then when the kernel starts up, it will not find the FAT32 setting in /etc/fstab and crash.)
Isn't Amazon so helpful?

[pavel-s]

But why is it not possible to just remove/update the script that responsible for downloading the update (on a rooted kindle)?

[knc1]

Originally Posted by pavel-s

But why is it not possible to just remove/update the script that responsible for downloading the update (on a rooted kindle)?

You only have to recode that part of the initramFS that is bundled with the kernel and then get that kernel build signed with Amazon's private key.
(The newer models (PW4 for example) now have the secure boot hardware feature enabled, one of the reasons people are having trouble trying to boot over the serial port.)

[pavel-s]

Originally Posted by knc1

You only have to recode that part of the initramFS that is bundled with the kernel and then get that kernel build signed with Amazon's private key.
(The newer models (PW4 for example) now have the secure boot hardware feature enabled, one of the reasons people are having trouble trying to boot over the serial port.)

Won't /etc/hosts be helpful then? The kernel itself should make a call via the network, isn't it? If so, there are should be a lot of places where you can block it. Or am I missing something again?

[ezdiy]

It's entirely doable, some years ago I went a bit further relayouted partition altogether on Kindle 2 - so as to prevent the system partition taking up space (poor thing was like 2GB, and fw root few hundreds mb of space used...). File sync then rigged with mtpd (usb) & samba (wifi).

As a method to block OTA it's overkill, as you're already editing initrd to begin with, and you can do far simpler things there to block OTA.

[zaoqi]

Originally Posted by knc1

Ah, but you evidently never restarted your KT3 ...
The start-up process will discover the "corrupted" (ext3) storage area and reformat it to FAT32 for you.
(And then when the kernel starts up, it will not find the FAT32 setting in /etc/fstab and crash.)
Isn't Amazon so helpful?

I used to restarted it and I didn't find these problems

[zaoqi]

Originally Posted by knc1

Ah, but you evidently never restarted your KT3 ...
The start-up process will discover the "corrupted" (ext3) storage area and reformat it to FAT32 for you.
(And then when the kernel starts up, it will not find the FAT32 setting in /etc/fstab and crash.)
Isn't Amazon so helpful?

My parameter settings were wrong at the beginning, Kindle seemed to start normally without mounting /mnt/base-us
Probably because my KT3 was not clever