From: Darren Hart <dvhart@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH 0/2] Fully support ext3/ext4 rootfs generation
Date: Mon, 04 Mar 2013 08:09:32 -0800 [thread overview]
Message-ID: <5134C73C.2000300@linux.intel.com> (raw)
In-Reply-To: <1362406238.29587.28.camel@ted>
On 03/04/2013 06:10 AM, Richard Purdie wrote:
> On Mon, 2013-03-04 at 21:42 +0800, Robert Yang wrote:
>>
>> On 03/04/2013 02:21 AM, Darren Hart wrote:
>>>
>>>
>>> On 03/03/2013 09:15 AM, Darren Hart wrote:
>
>> Yes, we do have hard links in the rootfs, e.g: core-image-sato and
>> core-image-sato-sdk:
>>
>> # The sato
>> $ find core-image-sato/1.0-r0/rootfs/ -type f -printf "%p %i %n\n" | grep -v '1$'
>> core-image-sato/1.0-r0/rootfs/etc/terminfo/v/vt200 26977609 2
>> core-image-sato/1.0-r0/rootfs/etc/terminfo/v/vt220 26977609 2
>> core-image-sato/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld.bfd 26978690 2
>> core-image-sato/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld 26978690 2
>
> What if the count was 11? or 21? I'm just mentioning we need to improve
> that command!
Yes a -v ' 1$' would be better.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2013-03-04 16:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 10:46 [RFC PATCH 0/2] Fully support ext3/ext4 rootfs generation Robert Yang
2013-03-02 10:46 ` [RFC PATCH 1/2] e2fsprogs: add populate-extfs.sh Robert Yang
2013-03-02 10:46 ` [RFC PATCH 2/2] image_types.bbclass: replace genext2fs with populate-extfs.sh Robert Yang
2013-03-02 11:39 ` [RFC PATCH 0/2] Fully support ext3/ext4 rootfs generation Richard Purdie
2013-03-03 17:15 ` Darren Hart
2013-03-03 18:21 ` Darren Hart
2013-03-04 13:42 ` Robert Yang
2013-03-04 14:09 ` Robert Yang
2013-03-04 14:10 ` Richard Purdie
2013-03-04 16:09 ` Darren Hart [this message]
2013-03-05 8:24 ` Robert Yang
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=5134C73C.2000300@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox