From: John Rama <john.rama01@gmail.com>
To: yocto@yoctoproject.org
Subject: Re: NFS rootfs: mount: only root can mount proc on /proc
Date: Mon, 19 Dec 2016 19:50:25 +0900 [thread overview]
Message-ID: <5857BB71.8010206@gmail.com> (raw)
In-Reply-To: <CAF3SDA5yne+Qz=K9dt7_t_1KmUa73qbgVZM96n8OK-gUk8N6zg@mail.gmail.com>
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 <anders@chargestorm.se>:
>> Hi,
>>
>> * John Rama <john.rama01@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
>
>
>
prev parent reply other threads:[~2016-12-19 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 1:27 NFS rootfs: mount: only root can mount proc on /proc John Rama
2016-12-15 2:13 ` Khem Raj
2016-12-15 14:09 ` Anders Darander
2016-12-15 15:20 ` Daniel.
2016-12-19 10:50 ` John Rama [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5857BB71.8010206@gmail.com \
--to=john.rama01@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.