home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!spool.mu.edu!yale.edu!jvnc.net!princeton!rutgers!igor.rutgers.edu!athos.rutgers.edu!hedrick
- From: hedrick@athos.rutgers.edu (Charles Hedrick)
- Newsgroups: comp.os.linux
- Subject: Re: SLIP and X386
- Message-ID: <Sep.6.23.07.01.1992.12536@athos.rutgers.edu>
- Date: 7 Sep 92 03:07:02 GMT
- References: <55pnpxd.genie@netcom.com>
- Organization: Rutgers Univ., New Brunswick, N.J.
- Lines: 27
-
- genie@netcom.com (The Genie) writes:
-
- >Hi.
- >Now that tcp/ip is available for Linux, I'd like to know if
- >this combination is possible.
-
- >Is it possible to use SLIP and X Windows together? 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.
-
- >Actually, for SLIP, we would not even need the
- >new tcp/ip beta support, just the ka9q package?
-
- As far as I can tell, the new TCP/IP does not yet support SLIP. KA9Q
- does implement SLIP. It does not need the beta TCP/IP code -- it does
- TCP/IP at user level. You can use it with X. Just say "start x".
- However starting an X window is painful at 9600 bps. I recommend
- using a normal telnet session for most interactive work, and starting
- an X session only for applications that need it. One reasonable
- approach would be to start two telnet sessions, and set the DISPLAY
- variable in only one of them. Then you could use that session for
- stuff that needs X. You could use the other session for normal
- interactive work. You want a separate session because once you set
- the DISPLAY variable, every time you call emacs, it will try to create
- an X window. There's a READ.ME with KA9Q that explains how to set up
- SLIP, as much as it can be explained.
-