From: Upholder@uiuc.edu (THE Upholder of Truth) Subject: Re: SLIP and X386 Date: Tue, 8 Sep 1992 17:17:03 GMT
rick@ee.uwm.edu (Rick Miller) writes:
>In article <55pnpxd.genie@netcom.com> genie@netcom.com (The Genie) writes:
>>Is it possible to use SLIP and X Windows together?
In a word, yes. ka9q can allow remote Xclients over SLIP (provided you have
issued 'start x' sometime that session or in startup.net)
>>With packages like ka9q, is it possible to redirect all
>>tcp/ip packets to the serial modem? A true SLIP
>>connection would allow things like xhosting, etc.
>ka9q is like a boat. Just as a boat is no good for driving around town,
>but can cross a river where there's no bridge, ka9q is no good for inter-
>process communication, but it can communicate on the net without the help
>of kernel TCP/IP.
>The same way, 'xhost' needs kernel TCP/IP. It cannot use the ka9q package,
>because ka9q is suited only to serving a single USER, not other processes.
as I understand it, xhost currently doesn't work because it relies on TCP/IP
code that doesn't exist in your average linux kernel. If you are interested
in limiting connections to your X display under slip, it will need to be done
INSIDE ka9q.
I don't know how to do this, I haven't tried. As it is, I either don't
'start x' for security reasons, or do 'start x' when I'm just messing around.
(I hope that was a more direct answer to your question).
-- The Upholder of Truth I am not only ready to Upholder@uiuc.edu (BSD/ASCII mail) retract this, but also jar42733@sumter.cso.uiuc.edu (NeXT mail) deny I said anything. =) wi.4173@wizvax.methuen.ma.us (anon. mail) This is *NOT* CCSO's opinion.