Bug 11141 - runqemu ignores the environment variables KERNEL,MACHINE, and ROOTFS
Summary: runqemu ignores the environment variables KERNEL,MACHINE, and ROOTFS
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: Scripts and Tools (show other bugs)
Version: 2.3
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.3 M4
Assignee: Robert Yang
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-03-09 23:15 UTC by brian avery
Modified: 2017-04-13 01:32 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description brian avery 2017-03-09 23:15:03 UTC 
Usage: you can run this script with any valid combination  
of the following environment variables (in any order):  
  KERNEL - the kernel image file to use  
  ROOTFS - the rootfs image file or nfsroot directory to use  
  MACHINE - the machine name (optional, autodetected from KERNEL filename if unspecified)  

--- but setting any of these in the environment has no effect on what runqemu actually does.
Comment 1 Paul Eggleton 2017-03-16 03:51:03 UTC 
It's funny, I never noticed that it mentioned "environment variables" here - I had always read this as a list of named parameters to the script. I wonder what was intended? I guess we'd have to check back with the shell-based version to be sure.
Comment 2 Robert Yang 2017-03-16 06:31:13 UTC 
Hi Paul, the shell runqemu does support environment variables.