Server refused to start a shell/command (Buildroot - RPi)

Kevin Hill dropbear at procountsoftware.co.uk
Thu Jan 15 00:18:45 AWST 2015


I think we're getting closer to a solution....

http://gumstix-users.narkive.com/0r65Sz7n/server-refused-to-allocate-pty-2-6-15-putty-connection-over-bt

I don't think I have udev enabled, so I'll have to put it somewhere 
else, but I'll experiment tonight.

Thanks,
Kevin.

On 2015-01-14 16:11, Kevin Hill wrote:
> Well, I think that is my problem. /dev/pts did not exist.
> I didn't start from a default buildroot system, but one that was
> already cutdown for NOOBS, and probably one that did not need any
> PTYs.
> So I guess my next question is which options in buildroot do I need
> to enable in order to support PTYs?
>
> Is it sufficient to do 'mknod -m 0666 /dev/ptmx c 5 2' ?
>
> I have also discovered there may be some information to be gleaned
> from /proc/sys/kernal/pty/max and /proc/sys.kernel/pty/nr, so I will
> look at those too.
>
> Cheers,
> Kevin
>
>
> On 2015-01-14 16:00, Peter Korsgaard wrote:
>>>>>>> "Matt" == Matt Johnston <matt at ucc.asn.au> writes:
>>
>>  > Thinking a bit further, try doing:
>>  > mount -t devpts devpts /dev/pts
>>
>>  > That special filesystem probably needs to be mounted for openpty 
>> to
>>  > work. I’m not sure how that works with buildroot by default.
>>
>> /dev/pts gets mkdir'ed and mounted by default in Buildroot since 
>> atleast
>> 2010, so unless Kevin has tweaked anything it should be fine.



More information about the Dropbear mailing list