From: Dmitry Vinokurov <d.vinokuroff@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Wrong content of /dev directory
Date: Sat, 23 Jan 2010 21:31:04 +0500 [thread overview]
Message-ID: <4B5B2448.1050202@gmail.com> (raw)
In-Reply-To: <4B5B1BDB.7050100@gmail.com>
Seems I can answer by myself, all this devices was created by
/etc/rcS.d/S05devices based on /etc/device_table
On 23.01.2010 20:55 Dmitry Vinokurov wrote:
> Hello,
>
> I work on non-udev image (IMAGE_DEV_MANAGER = ""), device table is set
> via IMAGE_DEVICE_TABLES =
> "recipes/images/cgv-image/device_table_phy3250-cgv.txt".
>
> Result rootfs image got all needed files, but when I run board, /dev
> dir is absolutely different, I can't see my files there, but many
> unnecessary. Seems like some dev manager worked.
>
> Could anybody explain this thing? It's really strange and unexpected.
>
> Thanks
>
--
Best Regards,
Dmitry Vinokurov
<d.vinokuroff@gmail.com>
prev parent reply other threads:[~2010-01-23 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 15:55 Wrong content of /dev directory Dmitry Vinokurov
2010-01-23 16:31 ` Dmitry Vinokurov [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=4B5B2448.1050202@gmail.com \
--to=d.vinokuroff@gmail.com \
--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