On 7/9/14, 11:46 AM, "Saul Wold" wrote:
>On 07/09/2014 08:18 AM, Christopher Larson wrote:
>> On Wed, Jul 9, 2014 at 7:37 AM, Bollinger, Seth
>>
>> wrote:
>>
>>> I recently ran into a problem where I had trouble determining why the
>>> set
Hello,
I recently ran into a problem where I had trouble determining why the setgid
bit was set in my rootfs. It turns out that debian has this bit set on
/usr/local (where I was building from), and thus inherited this bit from that
directory tree. This surprised me, so I thought I would pass
>I'm not sure without digging into it further (which I'm unable to do at
>the
>moment, perhaps someone else can.)
Just as an FYI for anyone who might find this thread interesting, I fixed
the problem by adding another hook into poky/lib/oe/image.py before the
IMAGE_CMD hook.
It defaults to doin
>Are you sure? IMAGE_POSTPROCESS_COMMAND runs after all of the image files
>have
>been created; at that time, the contents of the image has already been
>compressed or otherwise combined into the final output file(s), so I
>would think
>that would be too late to modify the contents.
I just unzi
>It looks like the POSTPROCESS commands are run too early. Subsequent
>actions depend on that directory structure (pre-linking, etc.). It looks
>like I would need some way to hook _cleanup() in the RootFS subclass.
Actually scratch the above comment. I wasn¹t reading the log spew
correctly. T
>You could just delete these within a function added to
>ROOTFS_POSTPROCESS_COMMAND, and that's probably the way to deal with it
>for
>now; however for the future I do think the build system ought to be able
>to
>clean these files up itself if they aren't supposed to be there. I've
>created a
>
>I guess I didn¹t think about using a full image as I would need to remove
>a bunch of stuff, but maybe that is the best way. That way I can keep the
>flexibility of defining recipes that would be installed to my data
>partition image. I will give it a try.
So I created an empty image without a
>Make bitbake give you a tar.bz2 and then create the partitions etc.
>yourself
>using an additional script. Wether it could be integrate I do not know.
I guess I didn¹t think about using a full image as I would need to remove
a bunch of stuff, but maybe that is the best way. That way I can keep
Hello All,
I need to generate a new file system for an alternate partition (not rootfs).
What’s the best way to go about this? I may need to create files with all
different users/permission (perhaps root). Do I need to use pseudo? Are there
any examples of this out there?
Thanks!
Seth
--
Hello All,
We’re trying to share a DL_DIR over NFS so all developers don’t have to
re-download source files every time they want to do a clean build.
Unfortunately we’re running into problems with lock files that are left behind
by (sometimes) terminated processes. This will block users who a
10 matches
Mail list logo
