Fail to start dropbear

Fail to start dropbear

[axel lin]

hi list,
I got below messages when start dropbear... ( config is angstrom/mainstone)
how to fix this?

root@mainstone:/$ /etc/init.d/dropbear start
Starting Dropbear SSH server: Will output 1024 bit rsa secret key to
'/etc/dropbear/dropbear_rsa_host_key'
Generating key, this may take a while...
Exited: couldn't open random device

Thanks for your help.
Axel

Re: Fail to start dropbear

[Marcin Juszkiewicz]

Dnia środa, 18 października 2006 08:17, axel lin napisał:

> I got below messages when start dropbear... ( config is
> angstrom/mainstone) how to fix this?

> root@mainstone:/$ /etc/init.d/dropbear start
> Starting Dropbear SSH server: Will output 1024 bit rsa secret key to
> '/etc/dropbear/dropbear_rsa_host_key'
> Generating key, this may take a while...
> Exited: couldn't open random device

Looks like your machine system lack /dev/(u)random

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

               Heavy, adj.:
               	Seduced by the chocolate side of the Force.

Re: Fail to start dropbear

[axel lin]

2006/10/18, Marcin Juszkiewicz <openembedded@hrw.one.pl>:
> Dnia środa, 18 października 2006 08:17, axel lin napisał:
>
> > I got below messages when start dropbear... ( config is
> > angstrom/mainstone) how to fix this?
>
> > root@mainstone:/$ /etc/init.d/dropbear start
> > Starting Dropbear SSH server: Will output 1024 bit rsa secret key to
> > '/etc/dropbear/dropbear_rsa_host_key'
> > Generating key, this may take a while...
> > Exited: couldn't open random device
>
> Looks like your machine system lack /dev/(u)random
>
> --
> JID: hrw-jabber.org
> OpenEmbedded developer/consultant
>
>                Heavy, adj.:
>                 Seduced by the chocolate side of the Force.
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

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.

Regards,
Axel

Re: Fail to start dropbear

[Jamie Lenehan]

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>

Re: Fail to start dropbear

[Erik Hovland]

On Thu, Oct 19, 2006 at 06:34:53AM +1000, Jamie Lenehan wrote:
> 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

I seem to recall that /dev/zero and /dev/console have to be made
manually just to boot an initrd enabled image. Just to give you an idea
of an exception to the rule. Otherwise, I definitely agree.

E

-- 
Erik Hovland
mail: erik AT hovland DOT org
web: http://hovland.org/
PGP/GPG public key available on request

Re: Fail to start dropbear

[axel lin]

Thank you, Jamie.
I found the root cause of missing /dev/(u)random issue.
It is caused by missing "tmpfs" support in my kernel, as a result the
udev doesn't work.

Regards,
Axel


2006/10/19, Jamie Lenehan <lenehan@twibble.org>:
> 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>
>