[Replicant] the minimal effort needed for a minimal change in initramfs?
user468362 at 0w.se
user468362 at 0w.se
Tue Oct 27 10:47:10 UTC 2015
Hello Denis,
Thanks for your help.
On Mon, Oct 26, 2015 at 11:52:28PM +0100, Denis 'GNUtoo' Carikli wrote:
> > Is there any easier way? None of the many descriptions and
> > "repack"-tools which I could locate on the net correspond to the
> > structure of boot.img.
> The FSO/SHR and Replicant/Paul Kocialkowski projects ported some Android
> specific tools to GNU/Linux, such as:
> * ADB
> * fastboot
> * mkbootimg
> In that same repository, someone also wrote an unpacking tool:
> * unbootimg
I did find various tools with these names :) but they seemed
to address images of a format other than I had at hand.
Never mind.
I sacrificed 60GB disk space (and quite a few [MG]bytes net traffic)
and several hours x86_64 CPU time, to replace a handful of tiny files.
This is apparently the threshold to be able to tinker with Replicant.
Besides that, I rebuilt the kernel too, changing one line in the config.
OT:
Nevertheless, the effort was worth it, now I have got Coda file system
accessible on Replicant (global name space, consistent caching,
protection, disconnected operation).
In other words, Coda when properly used removes the need to "sync"
data between the multiple devices - you just use the same data under
/coda/...../something and Coda gives you the same view, no matter which
computer or phone you use for the moment.
(There is no installer, nor any access rights GUI integration, until
somebody writes it, but this works nicely as a proof of concept.)
Cheers,
Anru
More information about the Replicant
mailing list