From: Darren Hart <dvhart@linux.intel.com>
To: "Paul D. DeRocco" <pderocco@ix.netcom.com>
Cc: yocto@yoctoproject.org
Subject: Re: This one can't be me...
Date: Thu, 04 Apr 2013 10:17:14 -0700 [thread overview]
Message-ID: <515DB59A.9080805@linux.intel.com> (raw)
In-Reply-To: <60B6B6AA6C0244FCB462853CE0D3D80E@PAULD>
On 04/03/2013 05:32 PM, Paul D. DeRocco wrote:
>> From: Bodke, Kishore K
>>
>> It's surprising that you don't see anything under
>> /home/pauld/yocto-atom/build/tmp/work/cedartrail_nopvr-poky-li
> nux/linux-yoct
>> o-3.0.32+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+1e79e
> 03d115ed177882
>> ab53909a4f3555e434833-r4.1/linux-cedartrail-nopvr-standard-build
>>
>> It means that Kernel is not getting build for you?
>> How come you were able to generate the .hddimg and trying to boot?
>>
>> Do you have the rootfs under
>> build/tmp/work/Cedartrail*/core-image-sato/?
>
> Some gremlin made that first directory go away. I've successfully rebuilt
> it.
>
> There is a rootfs directory in the second directory, and it contains things
> like /dev/ram?. I captured a tree listing of my build a while back, and it
> had those device nodes, too.
>
> If I loop mount the .ext3 file that my panicking build produced, it has
> /dev/ram? device nodes, too.
>
I believe those are generated by devtmpfs anyway.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2013-04-04 17:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 21:27 This one can't be me Paul D. DeRocco
2013-04-02 23:57 ` Paul D. DeRocco
2013-04-03 16:04 ` Marc Ferland
2013-04-03 15:38 ` Darren Hart
2013-04-03 17:47 ` Bodke, Kishore K
2013-04-03 19:57 ` Paul D. DeRocco
2013-04-03 20:24 ` Darren Hart
2013-04-03 20:50 ` Paul D. DeRocco
2013-04-03 22:01 ` Bodke, Kishore K
2013-04-04 0:32 ` Paul D. DeRocco
2013-04-04 17:17 ` Darren Hart [this message]
2013-04-03 22:09 ` Darren Hart
2013-04-04 0:21 ` Paul D. DeRocco
2013-04-04 17:18 ` Darren Hart
2013-04-04 18:31 ` Bodke, Kishore K
2013-04-04 19:14 ` Bodke, Kishore K
2013-06-20 14:58 ` Darren Hart
[not found] ` <13F417252F8B4CB5BB755BB07928D20C@PAULD>
[not found] ` <D956029D25CF204F948EA0FB515E1EE258405AC4@ORSMSX105.amr.corp.intel.com>
[not found] ` <2FD1BA69DE1E491C839CA26A7D2CA32A@PAULD>
[not found] ` <D956029D25CF204F948EA0FB515E1EE258405C96@ORSMSX105.amr.corp.intel.com>
2013-04-05 17:06 ` Paul D. DeRocco
2013-04-05 18:15 ` Bodke, Kishore K
2013-04-05 18:48 ` Paul D. DeRocco
2013-04-05 22:32 ` Bodke, Kishore K
2013-04-05 22:45 ` Paul D. DeRocco
2013-04-05 23:17 ` Sean Liming
2013-04-05 23:54 ` Paul D. DeRocco
2013-04-05 23:34 ` Tom Zanussi
2013-04-06 4:03 ` Tom Zanussi
2013-04-06 4:15 ` Paul D. DeRocco
2013-04-06 4:48 ` Tom Zanussi
2013-04-06 5:55 ` Bruce Ashfield
2013-04-06 14:00 ` Tom Zanussi
2013-04-06 18:20 ` Paul D. DeRocco
2013-04-06 19:20 ` Tom Zanussi
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=515DB59A.9080805@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=pderocco@ix.netcom.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.