The Linux Development Board requires several conditions to turn on the Telnet service:
1. File system support Telnet
BusyBox default is to put the Telnet and telnetd function into the, so this step is generally saved.
2. Mount Devpts
To mount the filesystem, you need to create the PTS folder under the Dev folder and mount it as a devpts type.
mkdir/dev/pts
mount-t devpts devpts/dev/pts
These two steps can be written to the run script before the system starts,/etc/init.d/rcs
after multiple experiments, the following conclusions are drawn:
A. Mount pts under Dev This step of the device file required for the Telnet service must not have intermittent login failures after Mdev or Udev services. I have been struggling with this problem for a long time.
B. The mount process hypothesis writes that there may also be intermittent failures in the Fstab file. This may also be because the dynamic hot swap service is in conflict with this.
3. Turn on telnetd service
telnetserver talent must be turned on from client login to Development Board, Telnet Server service is telnetd, able to run after boot
telnetd-l/bin/login
or add this directly to the boot run script RCS inside, be able to boot their own initiative to open the Telnet service.
