Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-handheld][PATCH 2/3] udev: add bbappend and disable device cache as default.
Date: Thu, 03 Nov 2011 09:36:17 +0100	[thread overview]
Message-ID: <j8tjq1$o2$1@dough.gmane.org> (raw)
In-Reply-To: <2904446.7I7DN7edGu@helios>

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

Op 02-11-11 22:00, Paul Eggleton schreef:
> On Monday 17 October 2011 01:26:50 Andrea Adami wrote:
>> * For some reasons when the cache is created root can still be ro *
>> and as solution you would be obliged to add 'rw' to your commandline.
>> * There are patches in openembedded-classic to correct this * (and
>> those are still pending for meta-oe). * Until a solution is found
>> disable the creation of the device cache on boot.
>> 
>> Signed-off-by: Andrea Adami <andrea.adami@gmail.com> --- 
>> recipes-core/udev/udev/default      |    4 ++++ 
>> recipes-core/udev/udev_173.bbappend |    1 + 2 files changed, 5 
>> insertions(+), 0 deletions(-) create mode 100644 
>> recipes-core/udev/udev/default create mode 100644 
>> recipes-core/udev/udev_173.bbappend
>> 
>> diff --git a/recipes-core/udev/udev/default 
>> b/recipes-core/udev/udev/default new file mode 100644 index 
>> 0000000..ba2867e --- /dev/null +++ b/recipes-core/udev/udev/default @@ 
>> -0,0 +1,4 @@ +# Default for /etc/init.d/udev + +# Uncomment this out
>> to enable device cache +#DEVCACHE="/etc/dev.tar" diff --git 
>> a/recipes-core/udev/udev_173.bbappend 
>> b/recipes-core/udev/udev_173.bbappend new file mode 100644 index 
>> 0000000..72d991c --- /dev/null +++ 
>> b/recipes-core/udev/udev_173.bbappend @@ -0,0 +1 @@ 
>> +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> 
> I think this is going to cause problems for distros such as Angstrom
> that enable this layer without always using it. Can we just disable the
> dev cache for the machines in meta-handheld?

Or get with the program and use udev 174 with systemd, no need for a device
cache in that case!

regards,

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

iD8DBQFOslKBMkyGM64RGpERApRuAKCrFvkx2Ndu72tpP0DZSRXARyj1kgCgjPKR
uITbHbzYgtHKi/k2aEpRS+4=
=D6Yf
-----END PGP SIGNATURE-----




  reply	other threads:[~2011-11-03  8:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-16 23:26 [meta-handheld][PATCH 1/3] formfactor: initial commit of collie, poodle and tosa machconfig Andrea Adami
2011-10-16 23:26 ` [meta-handheld][PATCH 2/3] udev: add bbappend and disable device cache as default Andrea Adami
2011-11-02 21:00   ` Paul Eggleton
2011-11-03  8:36     ` Koen Kooi [this message]
2011-11-03  9:09       ` Andrea Adami
2011-11-03  9:22         ` Andrea Adami
2011-11-03  9:24           ` Koen Kooi
2011-11-03  9:25         ` Koen Kooi
2011-11-03 10:08           ` Andrea Adami
2011-10-16 23:26 ` [meta-handheld][PATCH 3/3] xserver-xf86-config: add more xorg.conf for other Zaurus devices Andrea Adami
2011-10-20 22:25 ` [meta-handheld][PATCH V2 " Andrea Adami
2011-11-02 21:02 ` [meta-handheld][PATCH 1/3] formfactor: initial commit of collie, poodle and tosa machconfig Paul Eggleton
2011-11-03  8:51   ` Koen Kooi
2011-11-03 10:10     ` Paul Eggleton
2011-11-23 20:35       ` Khem Raj

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='j8tjq1$o2$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox