On Mon, 4 Sep 2000, Tom Massey wrote:
Perhaps if you were able to start a painstakingly slow pppd over that
serial link, you could use the remote-x facilities. Maybe something low
bandwidth like VNC, lbx, or perhaps ssh-x-forwarding.
> Just thinking about this some more, I don't think that you'll be able to
> run X on a PC running terminal emulation and connecting over a serial
> port (I think this is what you want to do). Connecting a text only
> terminal on a serial port is pretty easy to do, you just have to add a
> line to /etc/inittab to run a getty on the serial port, then hook up the
> pc with a null modem cable, run some terminal emulation software and
> make sure the settings in your terminal emulation software match those
> set up in the getty on the Linux box you're connecting to. Problem is -
> I can't think of any terminal emulation software that would be able to
> understand X codes. I know that there are terminals that can do this -
> after all X was designed to run on a central machine and display on many
> terminals (it actually works much better/faster this way then the way
> it's currently often used on Linux boxen with a single user at a time -
> as an aside to anybody who doesn't think X runs very well on their
> machine: it wasn't designed to be run the way it often is on a Linux
> box). Sorry if I'm rambling a bit here... My point is that when you hook
> up a PC to your Linux box on the serial port, and run terminal emulation
> software on it, then all you've got on the PC running emulation is the
> capabilities of the terminal it's emulating. Generally this doesn't
> include the ability to run X. eg If you've got it running VT100
> emulation (pretty much the most popular), then all the PC will
> understand is VT100 codes, which don't include X. If you've got
> reasonable hardware (say 486 and above) you'd be better off installing
> Linux on it properly, and sticking a NIC in.
>
--
Regards,
Ellick Chan
[EMAIL PROTECTED]
Sep 4
