From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: About having a static /dev
Date: Thu, 22 Apr 2010 14:34:38 +0200 [thread overview]
Message-ID: <hqpfou$igp$1@dough.gmane.org> (raw)
In-Reply-To: <20100422134322.f79d1365.ospite@studenti.unina.it>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 22-04-10 13:43, Antonio Ospite wrote:
> For my machine (a780) I'd like to have a static /dev whatever image I
> build, I tried setting:
> IMAGE_DEV_MANAGER = ""
> IMAGE_DEVICE_TABLES = "files/device_table-minimal.txt \
> files/device_table-ezx.txt"
>
> But this is still not enough:
> 1. the 'devices' script from initscripts keeps rewriting /dev at each
> boot, and with a layout different than one would expect by having
> IMAGE_DEVICE_TABLES set, see also
> http://bugs.openembedded.org/show_bug.cgi?id=3593
The right answer would be to have image.bbclass create /etc/device_table
from the IMAGE_DEVICE_TABLES vars during do_rootfs.
And of course mark /etc/device_table as CONFFILES in the initscripts
recipe to keep the changes on package upgrades.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFL0EJeMkyGM64RGpERAmH7AJ9bEXPhkuaX0Rvo9n8nUE4ds5niNQCfXnVx
cWUbHwV6xcBe5hSoQpGkMIA=
=vw6J
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-04-22 12:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 11:43 About having a static /dev Antonio Ospite
2010-04-22 11:55 ` Phil Blundell
2010-04-22 12:46 ` Antonio Ospite
2010-04-22 12:54 ` Dr. Michael Lauer
2010-04-22 13:22 ` Phil Blundell
2010-04-22 14:22 ` Koen Kooi
2010-04-22 12:34 ` Koen Kooi [this message]
2010-04-26 15:36 ` [PATCH] image.bbclass: create /etc/device_table from IMAGE_DEVICE_TABLES Antonio Ospite
2010-04-26 16:34 ` Koen Kooi
2010-04-28 16:14 ` Antonio Ospite
2010-04-28 16:25 ` Koen Kooi
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='hqpfou$igp$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.