[BusyBox] more over telnet unpredictable behaviour

Steve Dover sw0rdf1sh at sbcglobal.net
Sat Jan 3 19:36:55 UTC 2004


With a combo of Busybox-1.00-pre5 and uClibc-0.9.25,
if I telnet in (even via 127.0.0.1), and then run
/bin/more on a file I'm seeing unpredictable behaviour.

Sometimes, it takes pairs of CRs to get the next line,
sometimes, it take more than two CRs to get it to go,
but in that case it takes a bunch (the # depends upon
the size of the file), but then the entire file is
dumped and I get my shell prompt back.
I've also seen cases where I had to enter pairs of 'q's
to quit, and then the second 'q' ended up on my shell cmdline.
Sometimes it works as expected at first, but then fails
later, and once it fails, it remains broke.

Sometimes it seems totally dead, and even the multiple CRs
or multiple Spacebars never dumps the output even on small files.
In that case, even 'q' does not work.  Must ^C to get shell.



More information about the busybox mailing list