All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Anstrom boot hang with MACHINE=i686-generic and DISTRO=anstrom-2010.x
Date: Wed, 09 Nov 2011 11:18:37 +0100	[thread overview]
Message-ID: <j9dk1t$994$1@dough.gmane.org> (raw)
In-Reply-To: <loom.20111109T001647-942@post.gmane.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 09-11-11 00:19, Greg Kogut schreef:
> Greg Kogut <gkogut <at> yahoo.com> writes:
> 
>> 
>> I've tried both console-image and x11-image.
> 
> 
> Edit:
> 
> I was able to to boot fully after appending "-o rw" to the "root" kernel
> parameter.
> 
> I suspect the issue was that the read-only mount was not allowing udev to
> correctly populate /dev with the tty devices passed to getty, and getty
> was flummoxed.
> 
> So I'm amending my question:  Help a n00b -what's the standard practice
> with respect to maintaining an embedded-safe read-only rootfs while
> allowing udev to do its thang?   Separate partition for /dev?

You're still following the deprecated OE-classic workflow. If you follow the
instructions at http://www.angstrom-distribution.org/building-angstrom you
will get the updated angstrom configs that work with RO /

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFOulN9MkyGM64RGpERAgkLAJsHQ6t7GR+JUBu5BeaTVz/YYK/KpQCguTWU
XMTgjD846DcyqCIr9B7JUhc=
=3H0D
-----END PGP SIGNATURE-----




      parent reply	other threads:[~2011-11-09 10:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 22:05 Anstrom boot hang with MACHINE=i686-generic and DISTRO=anstrom-2010.x Greg Kogut
2011-11-08 23:19 ` Greg Kogut
2011-11-09  1:28   ` Anstrom boot hang with MACHINE=i686-generic and?DISTRO=anstrom-2010.x Denys Dmytriyenko
2011-11-09 10:18   ` Koen Kooi [this message]

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='j9dk1t$994$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-devel@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 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.