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 16:22:05 +0200 [thread overview]
Message-ID: <hqpm2d$d7p$1@dough.gmane.org> (raw)
In-Reply-To: <20100422144638.7c78d45c.ospite@studenti.unina.it>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 22-04-10 14:46, Antonio Ospite wrote:
> On Thu, 22 Apr 2010 12:55:43 +0100
> Phil Blundell <philb@gnu.org> wrote:
>
>> On Thu, 2010-04-22 at 13:43 +0200, Antonio Ospite wrote:
>>> 2. If I install any package which depends on udev then udev is brought
>>> in and the static layout is gone at the next boot.
>>
>> I think your best option is probably to make udev be a DISTRO_FEATURE
>> and not set it for your own distribution.
>>
>> If you genuinely want udev to be selected (for your particular DISTRO)
>> on a per-MACHINE basis then you'll have to invent some way to nobble its
>> startup script so that it just doesn't do anything on machines where it
>> isn't wanted.
>>
>
> A per-MACHINE way would be better IMHO
That would break the case where you want static devs for one image (e.g.
initramfs, rescue fs), but other options (e.g. udev, devtempfs, mdev,
something else) for other images on the same machine.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFL0FuNMkyGM64RGpERAs2oAJ9bxwZhqGcesRA3EpEoMJ6vR9rwCACgjEcq
as1zs5zE8iuE806tNVdekBU=
=85tD
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-04-22 14:25 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 [this message]
2010-04-22 12:34 ` Koen Kooi
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='hqpm2d$d7p$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.