From: Jamie Lenehan <lenehan@twibble.org>
To: axel lin <axel.lin@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Fail to start dropbear
Date: Thu, 19 Oct 2006 06:34:53 +1000 [thread overview]
Message-ID: <20061018203453.GA29721@twibble.org> (raw)
In-Reply-To: <427d64720610180022p431603abpd3c035f0c79b8f5c@mail.gmail.com>
On Wed, Oct 18, 2006 at 03:22:41PM +0800, "axel lin" wrote:
[...]
> Thanks, Marcin.
> I fixed it by manually create the device file.
> How to config OE to add a device file, then I don't have to manually add it.
If you are using udev then udev should be creating /dev/random and
/dev/urandom (along with lots of other stuff). I don't think anything
special is required to get udev to created this.
If you really do want to add device nodes manually (which is probably wrong)
then see the "Device (/dev) nodes" section of the "image_ipkg class"
in the user manual:
http://www.openembedded.org/user-manual&dpage=ch07s05
--
Jamie Lenehan <lenehan@twibble.org>
next prev parent reply other threads:[~2006-10-18 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 6:17 Fail to start dropbear axel lin
2006-10-18 6:27 ` Marcin Juszkiewicz
2006-10-18 7:22 ` axel lin
2006-10-18 20:34 ` Jamie Lenehan [this message]
2006-10-18 21:44 ` Erik Hovland
2006-10-19 9:40 ` axel lin
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=20061018203453.GA29721@twibble.org \
--to=lenehan@twibble.org \
--cc=axel.lin@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 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.