From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Angstrom, ep93xx, broken rootfs
Date: Sun, 22 Feb 2009 20:19:36 +0100 [thread overview]
Message-ID: <gns8g9$4tg$1@ger.gmane.org> (raw)
In-Reply-To: <d741b6090902221034t224cd1e5ja6b3e863fd54bbda@mail.gmail.com>
On 22-02-09 19:34, Alex Williams wrote:
> Hello!
> I decided to update my OpenEmbedded from git today. Result: broken
> rootfs, many applications lost such as busybox and many other files,
> symlinks. Tried to build minimal-image... One week before update I had
> perfect rootfs and everything work fine... Resetting many commits
> since last week did not helped me.
> Details here: http://pastebin.com/m7ddd3941
That should be solved now, thanks for spotting!
/me grumbles at += vs _append " "
next prev parent reply other threads:[~2009-02-22 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 18:34 Angstrom, ep93xx, broken rootfs Alex Williams
2009-02-22 19:19 ` Koen Kooi [this message]
2009-02-22 22:44 ` Alex Williams
2009-02-22 21:43 ` ep93xx, ts72xx, gesbc-9302 and more (was Re: Angstrom, ep93xx, broken rootfs) Christian Gagneraud
2009-02-23 1:54 ` Christian Gagneraud
2009-02-23 17:52 ` Theodore A. Roth
2009-06-08 14:00 ` Marcin Juszkiewicz
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='gns8g9$4tg$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 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.