All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org, Scott Rifenbark <srifenbark@gmail.com>
Subject: Re: Live images?
Date: Thu, 05 Jun 2014 13:10:00 -0600	[thread overview]
Message-ID: <5390C088.2020006@mlbassoc.com> (raw)
In-Reply-To: <6944853.hSHdg7euvW@peggleto-mobl5.ger.corp.intel.com>

On 2014-06-05 11:24, Paul Eggleton wrote:
> On Thursday 05 June 2014 11:16:55 Gary Thomas wrote:
>> On 2014-06-05 09:07, Paul Eggleton wrote:
>>> On Thursday 05 June 2014 08:41:57 Gary Thomas wrote:
>>>> On 2014-06-05 08:32, Paul Eggleton wrote:
>>>>> On Thursday 05 June 2014 15:26:28 Paul Eggleton wrote:
>>>>>> Hi Gary,
>>>>>>
>>>>>> On Thursday 05 June 2014 07:07:34 Gary Thomas wrote:
>>>>>>> Looking through the Poky/Yocto sources, there seems to be
>>>>>>> some support for Live CD/USB images.  However, I can't find
>>>>>>> any examples nor documentation for how to use this.
>>>>>>>
>>>>>>> Can anyone provide some pointers?
>>>>>>
>>>>>> You're right, we seem to be missing that in our documentation; I'm not
>>>>>> sure
>>>>>> where the best place to document it would be though.
>>>>>>
>>>>>> FYI, you should just need to ensure "live" is in IMAGE_FSTYPES; then
>>>>>> you
>>>>>> should get a .directdisk image that you can just dd to a USB stick.
>>>>>
>>>>> Of course I meant to say .hddimg, not .directdisk.
>>>>
>>>> Thanks, I'll give that a try.
>>>>
>>>> What if I needed to boot from an actual CD?  I have an old
>>>> box here I'd like to try, but it doesn't boot from USB.
>>>
>>> We can produce ISO images but I don't think that they work quite as well,
>>> e.g.:
>>>
>>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=5282
>>>
>>> You could always try it though.
>>
>> Bummer, when I tried to build core-image-minimal and/or core-image-x11, it
> failed:
>> | DEBUG: Executing shell function read_only_rootfs_hook
>> | sed: can't read
>> | /home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image
>> | -minimal-initramfs/1.0-r0/rootfs/etc/fstab: No such file or directory
>> | WARNING:
>> | /home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image
>> | -minimal-initramfs/1.0-r0/temp/run.read_only_rootfs_hook.30446:1 exit 2
>> | from|
>> |   sed -i -e
>> |   '/^[#[:space:]]*\/dev\/root/{s/defaults/ro/;s/\([[:space:]]*[[:digit:]]
>> |   \)\([[:space:]]*\)[[:digit:]]$/\1\20/}'
>> /home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image-mi
>> nimal-initramfs/1.0-r0/rootfs/etc/fstab
>> | DEBUG: Python function do_rootfs finished
>> | ERROR: Function failed: read_only_rootfs_hook (log file is located at
>>
>> /home/local/x86_live_2014-06-05/tmp/work/genericx86-poky-linux/core-image-mi
>> nimal-initramfs/1.0-r0/temp/log.do_rootfs.30446)
>>
>> Using these settings:
>> Build Configuration:
>> BB_VERSION        = "1.23.1"
>> BUILD_SYS         = "i686-linux"
>> NATIVELSBSTRING   = "Fedora-13"
>> TARGET_SYS        = "i586-poky-linux"
>> MACHINE           = "genericx86"
>> DISTRO            = "poky"
>> DISTRO_VERSION    = "1.6+snapshot-20140605"
>> TUNE_FEATURES     = "m32 core2"
>> TARGET_FPU        = ""
>> meta
>> meta-yocto
>> meta-yocto-bsp    = "master:e7114046be6e71fb326477dc882adb814ef6a751"
>>
>> Extra settings in conf/local.conf
>> # Live CD setup
>> IMAGE_FSTYPES_append = " hddimg live"
>
> "hddimg" isn't a valid IMAGE_FSTYPES item.
>
> Also, try IMAGE_FSTYPES += rather than _append, that allows the initramfs
> image to have its own value (because it's not really valid to make a live
> initramfs...)

Sorry, I misread/misapplied your previous suggestions.

>
>> IMAGE_FEATURES_append = " read-only-rootfs"
>
> Try EXTRA_IMAGE_FEATURES += instead of IMAGE_FEATURES_append

I've changed both of these and it still fails if I enable the
read-only-rootfs.

If I leave that option out, I can build an .hddimg which I dd'd
to my USB stick.  It tried to boot, finds /vmlinuz but fails to
find /initrd

My local.conf settings are now:
# Live CD setup
IMAGE_FSTYPES += " live"
#IMAGE_FEATURES += " read-only-rootfs"
CORE_IMAGE_EXTRA_INSTALL += " python-core python-modules"

Finally, during one of my builds, I ended up with a core-image-minimal*.iso
I tried burning this to a CD an it booted up, albeit with a couple of
complaints about a read-only rootfs.  Sadly, I no longer get any .iso
results when I 'bitbake core-image-minimal'

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2014-06-05 19:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 13:07 Live images? Gary Thomas
2014-06-05 14:26 ` Paul Eggleton
2014-06-05 14:32   ` Paul Eggleton
2014-06-05 14:41     ` Gary Thomas
2014-06-05 15:07       ` Paul Eggleton
2014-06-05 17:16         ` Gary Thomas
2014-06-05 17:24           ` Paul Eggleton
2014-06-05 19:10             ` Gary Thomas [this message]
2014-06-05 22:08               ` Gary Thomas
2014-06-06 16:42                 ` Gary Thomas
2014-06-16 13:14               ` Paul Eggleton

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=5390C088.2020006@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=srifenbark@gmail.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.