Finally I figured out: http://geek.co.il/2010/03/14/how-to-build-a-chroot-jail-environment-for-centos
losetup -o 101711872 /dev/loop0 BBB-eMMC-flasher-ubuntu-13.10-2014-02-16-2gb.img mount /dev/loop0 image sudo mount --bind /dev image/dev sudo mount --bind /proc image/proc mkdir image/run/resolvconf cp /run/resolvconf/resolv.conf image/run/resolvconf/resolv.conf That fixed chroot network problems. I also decided to build new images on device (no qemu at all) in chrooted environment in "continuous integration" mode. Thanks. On Thursday, April 3, 2014 8:29:48 AM UTC+1, Boris Rybalkin wrote: > > Hi, > > Qemu static means you do not run vm, it is just chroot into > /path/to/arm/root/filesystem > having qemu-arm-static in /path/to/arm/root/filesystem/usr/bin > > You provided argument for qemu vm which is second option in my question > and I have no network issues there, only uboot question. > > Thanks. > > On Thursday, April 3, 2014 12:37:42 AM UTC+1, Nuno wrote: >> >> On 04/02/2014 06:05 PM, Boris Rybalkin wrote: >> > roblem here I have no network: >> >> You might want to try adding something like the following to your qemu >> calling parameters: >> >> -net nic,model=rtl8139 -net user >> >> regards, >> Nuno >> >> -- >> http://aeminium.org/nuno/ >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
