From: ChenQi <Qi.Chen@windriver.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: Zhenfeng.Zhao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2 4/5] populate-volatile.sh: improve the handling of link config items
Date: Wed, 20 Feb 2013 17:28:45 +0800 [thread overview]
Message-ID: <5124974D.2000908@windriver.com> (raw)
In-Reply-To: <CAC1BbcSWORfZ9x835DZ1f9oOdiqXFdGbFPYHNh3vTtmpdH-FHQ@mail.gmail.com>
On 02/20/2013 05:18 PM, Bernhard Reutner-Fischer wrote:
> On 20 February 2013 08:16, ChenQi <Qi.Chen@windriver.com> wrote:
>> On 02/20/2013 03:10 PM, Bernhard Reutner-Fischer wrote:
>>> On 20 February 2013 06:55:33 <Qi.Chen@windriver.com> wrote:
>>>> From: Chen Qi <Qi.Chen@windriver.com>
>>>>
>>>> Previously, if there's a link config item in the config file like
>>>>
>>>> l root root 1777 /tmp /var/tmp
>>>>
>>>> and /tmp has existed, the symlink will not be created correctly.
>>>>
>>>> Another example is the /run directory. If /run directory has been
>>>> created by some recipe or script before populate-volatile.sh runs,
>>>> the symlink of /run to /var/run will not be created correctly.
>>>>
>>>> This patch ensures that the system creates symlinks exactly as the
>>>> config file tells it.
>>>
>>> This one also has bugs in background handling, it seems.
>>
>> What's the bug?
> - link_file "${TSOURCE}" "${TNAME}" &
> - }
> + [ "${VERBOSE}" != "no" ] && echo "Creating
> link -${TNAME}- pointing to -${TSOURCE}-."
> + link_file "${TSOURCE}" "${TNAME}"
>
> missing '&' after the link_file.
Thanks. I'll resend out this patch.
>>
>>> Can't you massage stderr redirection when setting EXIT instead?
>>
>> Could you please be more specific?
> I meant EXEC.
> Can't you put the > /dev/null 2>&1 into the relevant parts of _all_
> the EXEC instead, in the whole series?
>
I don't think so :(
Only in case of running at rootfs time can we ignore the errors.
Best Regards,
Chen Qi
>>>> [YOCTO #3404]
>>>> [YOCTO #3406]
>
next prev parent reply other threads:[~2013-02-20 9:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 5:55 [PATCH V2 0/5] Read-only rootfs followup patches Qi.Chen
2013-02-20 5:55 ` [PATCH V2 1/5] image.bbclass: add a hook funtion to support readonly rootfs Qi.Chen
2013-02-20 5:55 ` [PATCH V2 2/5] core-image.bbclass: support read-only rootfs Qi.Chen
2013-02-20 5:55 ` [PATCH V2 3/5] populate-volatile.sh: add ROOT_DIR variable to support running at rootfs time Qi.Chen
2013-02-20 5:55 ` [PATCH V2 4/5] populate-volatile.sh: improve the handling of link config items Qi.Chen
2013-02-20 7:10 ` Bernhard Reutner-Fischer
2013-02-20 7:16 ` ChenQi
2013-02-20 9:18 ` Bernhard Reutner-Fischer
2013-02-20 9:28 ` ChenQi [this message]
2013-02-20 5:55 ` [PATCH V2 5/5] populate-volatile.sh: remove trailing whitespaces Qi.Chen
2013-02-20 14:19 ` Bernhard Reutner-Fischer
2013-02-21 2:31 ` ChenQi
2013-02-21 7:20 ` Bernhard Reutner-Fischer
[not found] <cover.1361352762.git.Qi.Chen@windriver.com>
2013-02-20 9:36 ` [PATCH V2 4/5] populate-volatile.sh: improve the handling of link config items Qi.Chen
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=5124974D.2000908@windriver.com \
--to=qi.chen@windriver.com \
--cc=Zhenfeng.Zhao@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rep.dot.nop@gmail.com \
/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