[11:21] <hvn2> hi, is there a difference between kernels on arm and x86, apart from the cpu ? My custom kernel 3.10.18 runs mostly fine on both, but apt-get downloads, verifies, gets deps and at point of installing, it hangs/stalls. On x86, same kernel, all goes fine.
[17:40] <ndec> hi ogra_ , how do you write the ubuntu 'rootfs' image file? with fastboot? how do you manage large  partition size?
[17:40] <ogra_> are you talking about ubuntu touch ?
[17:44] <ndec> yes.
[17:45] <ndec> these days, i am using a board that has fastboot only, and I need to flash ubuntu .img onto it.
[17:45] <ndec> my images are not ubuntu touch.. but that doesn't matter for flashing
[17:45] <ndec> ogra_: ^
[17:46] <ogra_> well, touch uses a very special initrd which kind of does parts of the container setup
[17:47] <ndec> but how do you flash the ubuntu rootfs?
[17:47] <ndec> and how big is it
[17:48] <ogra_> bzr branch lp:project-rootstock-ng
[17:48] <ogra_> take a look at rootstock-touch-install
[17:51] <ndec> ogra_: so you don't use fastboot flash?
[17:51] <ogra_> only for recovery
[17:52] <ogra_> (well, boot.img and recovery in fact)
[17:52] <ogra_> the installer is "source: goget-ubuntu-touch binary: ubuntu-device-flash"
[17:53] <ndec> ogra_: the ubuntu FS resides on userdata?
[17:53] <ogra_> in case you want to see the actual install process (but that wont help you without the knowledge from rootstock which shows how the ubuntu-system.img is assembled)
[17:53] <ogra_> the ubuntu fs is a loop mounted img file in userdata
[17:54] <ndec> ok. i see.
[17:55] <ndec> why is that, btw. why do you need a file and loop mount, vs putting the content in userdata?
[18:19] <ogra_> nethe OTA system uses img diffs
[18:19] <ogra_> *the
[18:20] <ogra_> we used the loop mounted imgs because you cant really force people to repartition ... it wont be like that for *real* ubuntu phones
[18:21] <ogra_> as long as we offer nexus installs these go with loop mounts