Remote shell problems.

Jonathan Andrews jon at jonshouse.co.uk
Wed Feb 1 11:56:14 UTC 2012


To help me develop a few things on a arm board i'm tring to get a remote
shell working.

Firstly I tried to set the arm board up for telnet

The kernel config has this
CONFIG_UNIX98_PTYS=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y

Kernel 2.6.36.4

Busybox 1.19.2
config has this :
CONFIG_FEATURE_DEVPTS=y


The arm board itself after boot and laughably small rc script.
# mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw,relatime,errors=continue)
/proc on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)

# telnetd -l /bin/bash -F
telnetd: can't find free pty

Oh dear ... Can anyone help here.




Never mind I say to myself I can always use netcat .. :-( Nope !
# nc -l -p 2222 -e /bin/bash


>From remote host ......
[jon at jonspc ~]$ telnet 10.10.10.111 2222
Trying 10.10.10.111...
Connected to 10.10.10.111.
Escape character is '^]'.

/bin/bash: line 1: $'\r': command not found

/bin/bash: line 2: $'\r': command not found
ls -l
's: invalid option -- '
BusyBox v1.19.2 (2012-01-21 23:57:00 GMT) multi-call binary.

Usage: ls [-1AaCxdLHRFplinsehrSXvctu] [-w WIDTH] [FILE]...


etc etc etc, seems to be some strange line expansion thing going on, I
don't understand. Help welcome :-)

/bin/bash is a statically linked bash 4.2, /bin/ash is a link to a
working busybox. Both shells behave the same.

Thanks,
Jon





More information about the busybox mailing list