After logging in successfully the following log messages are indicative
of my problem:
pty_allocate: openpty: No space left on device
No pty was allocated, couldn't execute
Exit (root): Exited normally.
PuTTY gets the messages:
Server refused to allocate pty
Server refused to start a shell/comm
Peter,
I think it is 2013.02 - the same one used for NOOBS.
So I guess it is also quite old, but I didn't want to upgrade and break
the rest of the system. I'm still taking baby steps...
If I can't get this version working, I'll consider upgrading to
buildroot 2014.11
Thanks for the info.
K
> "dropbear@procountsoftware" == dropbear@procountsoftware co uk
> writes:
> I have a minimalistic buildroot system for the Raspberry Pi and would like
> to add a dropbear ssh server to it that is started and is available from
> boot, but for now I'm just trying to enable it manually
Hi,
If you run “dropbear -F -E” (kill the existing server process first) then it
will run in the foreground and print logging. That should suggest what’s going
wrong. Alternatively it might already be logging to somewhere in /var/log
depending if syslog is running.
Cheers,
Matt
> On Tue 13/1/
I have a minimalistic buildroot system for the Raspberry Pi and would like
to add a dropbear ssh server to it that is started and is available from
boot, but for now I'm just trying to enable it manually and I'm having a
few problems.
I enabled dropbear within 'make menuconfig' and rebuilt buildro
