Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Qi.Chen@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V5 04/10] populate-volatile.sh: use $ROOT_DIR/var/volatile/tmp as TMPDIR
Date: Fri, 09 Aug 2013 14:34:39 -0700	[thread overview]
Message-ID: <5205606F.4020002@linux.intel.com> (raw)
In-Reply-To: <6bab50b7175af465199fd8efd3f1ff402b7e375d.1375941355.git.Qi.Chen@windriver.com>

On 08/07/2013 11:16 PM, Qi.Chen@windriver.com wrote:
> From: Chen Qi <Qi.Chen@windriver.com>
>
> It's possible that a 'No such directory' error occurs when doing
> check_requirement in populate-volatile.sh at rootfs time. This is
> because the $ROOT_DIR/var/tmp might be a dead link.
>
> Use $ROOT_DIR/var/volatile/tmp as the TMPDIR instead to avoid this
> error.
>
Can you use /run here instead it should be mounted early in the process 
also?

Sau!

> [YOCTO #4883]
> [YOCTO #4103]
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
>   .../initscripts-1.0/populate-volatile.sh           |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/initscripts/initscripts-1.0/populate-volatile.sh b/meta/recipes-core/initscripts/initscripts-1.0/populate-volatile.sh
> index 392879f..253fe1b 100755
> --- a/meta/recipes-core/initscripts/initscripts-1.0/populate-volatile.sh
> +++ b/meta/recipes-core/initscripts/initscripts-1.0/populate-volatile.sh
> @@ -23,7 +23,7 @@ ROOTFS_READ_ONLY=`is_rootfs_readonly`
>   [ "$ROOTFS_READ_ONLY" = "yes" ] && VOLATILE_ENABLE_CACHE=no
>
>   CFGDIR="${ROOT_DIR}/etc/default/volatiles"
> -TMPROOT="${ROOT_DIR}/var/tmp"
> +TMPROOT="${ROOT_DIR}/var/volatile/tmp"
>   COREDEF="00_core"
>
>   [ "${VERBOSE}" != "no" ] && echo "Populating volatile Filesystems."
>


  reply	other threads:[~2013-08-09 21:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08  6:15 [PATCH V5 00/10] Make read-only rootfs work with live images Qi.Chen
2013-08-08  6:15 ` [PATCH V5 01/10] init-live.sh: make $ROOT_MOUNT/media writable when necessary Qi.Chen
2013-08-08  6:15 ` [PATCH V5 02/10] use a uniform way to determine whether rootfs is read-only Qi.Chen
2013-08-08  6:16 ` [PATCH V5 03/10] udev: remove implicit dependency on initscripts Qi.Chen
2013-08-08  6:16 ` [PATCH V5 04/10] populate-volatile.sh: use $ROOT_DIR/var/volatile/tmp as TMPDIR Qi.Chen
2013-08-09 21:34   ` Saul Wold [this message]
2013-08-08  6:16 ` [PATCH V5 05/10] populate-volatile.sh: don't spawn background process at rootfs time Qi.Chen
2013-08-08  6:16 ` [PATCH V5 06/10] runqemu-internal: fix to start X correctly in live images Qi.Chen
2013-08-08  6:16 ` [PATCH V5 07/10] initscripts: use a uniform way to handle directories in read-only rootfs Qi.Chen
2013-08-08  6:16 ` [PATCH V5 08/10] populate-volatile.sh: use 'cp -a' to avoid potential problem Qi.Chen
2013-08-08  6:16 ` [PATCH V5 09/10] irda-utils: fix for read-only rootfs Qi.Chen
2013-08-08  6:16 ` [PATCH V5 10/10] openssh: " Qi.Chen
2013-08-16 17:43 ` [PATCH V5 00/10] Make read-only rootfs work with live images Saul Wold
2013-08-19  2:15   ` ChenQi

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=5205606F.4020002@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=Qi.Chen@windriver.com \
    --cc=openembedded-core@lists.openembedded.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