Thanks everyone for the feedback. I got #3 would be the best way. Kind Regards, John Rama
On 2016/12/16 0:20, Daniel. wrote: > 2016-12-15 12:09 GMT-02:00 Anders Darander <and...@chargestorm.se>: >> Hi, >> >> * John Rama <john.ram...@gmail.com> [161215 02:58]: >> >>> The ideas I can come up with are followings, but those of them are not >>> perfect.. >>> 1. Run the bitbake as root account >>> - would not run as root since the all of generated files are root >>> permission even for the log files. >> >> Never do this. You've got no idea what bitbake might do to your >> computer... >> >> >>> 2. Change UID and GID whenever generating new image >>> - I guess next build would fall into the trouble because of the owner >>> change. >> >> Yes, that'll get you problems later on. >> >>> 3. Untar the tar ball under >>> {YOCTO_BUILD_DIR}//tmp//deploy/image/{TARGET}/*rootfs.tar.bz2 to the >>> export dir >>> - takes additional time.. Not good. >> >> This is the right way to do it. >> >> If it takes to much time, create a script that runs bitbake and then >> untars the rootfs. > > I do this all the time and have faced no problems regarding exploding > the tar. You may want to generate a .tar instead of a .tar.bz2. This > will safe the CPU from decrompressing so it should be faster... > > Regards, >> >> Cheers, >> Anders >> >> -- >> Anders Darander, Senior System Architect >> ChargeStorm AB / eStorm AB >> -- >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto > > > -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto