On Fri, Jan 02, 2015 at 09:49:45AM -0500, william degnan wrote: >Part of the problem lies with the Apple ///. Ok, no PETSCII issues there. :) >I may also have to play around with the ttyUSB0 port on my linux box, >there may be some things I can do with characters there. There is a >lot about how to tunnel FROM a Raspberry Pi, but not as much about how >to make INBOUND connections via a terminal. With real (non-USB) RS-232 hardware it used to be as simple as editing /etc/inittab to start a getty process on /dev/ttyS0 or such. I used to have a Digital VT220 and later VT420 terminal attached to my Debian GNU/Linux computer in the student dormitory in mid-1990s. With USB, I can imagine that it could be more tricky, even if the ttyUSB0 adapter is plugged in before starting the system. Maybe the udev initialization could interfere with the startup. And it could become different with systemd too. >My goal is to have a general purpose way to connect machines that can >run terminal software directly to the Internet via the Raspberry Pi. Oh, I see. What are you using for a web browser? I would expect elinks to work reasonably well (for those web pages that did not yet catch the javascript virus). Actually I designed one web site lately using HTML4 and CSS (2 or 3, I guess), and I tested it with elinks. It is obviously ignoring all pictures and CSS, but it works pretty well. I used semantic markup, even for the menus where I used CSS tricks to make them look modern. Marko Message was sent through the cbm-hackers mailing listReceived on 2015-01-02 15:02:33
Archive generated by hypermail 2.2.0.