Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: scott.garman@intel.com,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] runqemu: Ensure ROOTFS path is absolute
Date: Fri, 21 Feb 2014 21:57:37 -0800	[thread overview]
Message-ID: <42DC4075-3C8F-4D01-AFDB-82AD3357C709@gmail.com> (raw)
In-Reply-To: <1392929845-23411-1-git-send-email-sgw@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 996 bytes --]


On Feb 20, 2014, at 12:57 PM, Saul Wold <sgw@linux.intel.com> wrote:

> There is a problem if a relative path is passed to the kernel for NFS usage
> that it will not correctly find it, so ensure that the ROOTFS path is absolute.
> 
> [YOCTO #2807]
> 
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
> scripts/runqemu | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/scripts/runqemu b/scripts/runqemu
> index 0db7ad6..57c5de4 100755
> --- a/scripts/runqemu
> +++ b/scripts/runqemu
> @@ -462,7 +462,9 @@ if [ -z "$ROOTFS" -a "x$FSTYPE" != "xvmdk" ]; then
>         error "Unable to determine default rootfs for MACHINE [$MACHINE]"
>     fi
> fi
> -# ROOTFS is now set for all cases
> +# ROOTFS is now set for all cases, now expand it to be an absolute path, it should exist at this point
> +
> +ROOTFS=`realpath $ROOTFS`

I think this change also means we need to add dependency on realpath package as prerequisite for build host.



[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

  reply	other threads:[~2014-02-22  5:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 20:57 [PATCH] runqemu: Ensure ROOTFS path is absolute Saul Wold
2014-02-22  5:57 ` Khem Raj [this message]
2014-02-22 12:55   ` Paul Eggleton
2014-02-22 16:21     ` Paul Barker
2014-02-22 16:34     ` Khem Raj
2014-02-25 15:10       ` Alexandru Palalau
2014-02-25 15:16         ` Alexandru Palalau

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=42DC4075-3C8F-4D01-AFDB-82AD3357C709@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=scott.garman@intel.com \
    --cc=sgw@linux.intel.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