NetNews Usenet Archive 1992 #20/NN_1992_20.iso/spool/comp/os/linux/10754

Text File | 1992-09-15 | 1.7 KB | 40 lines

Newsgroups: comp.os.linux
Path: sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!sdd.hp.com!uakari.primate.wisc.edu!usenet.coe.montana.edu!news.u.washington.edu!serval!poly!hlu
From: [e-mail] (H.J. Lu)
Subject: Re: Can you access a virtual console directly?
Message-ID: <[e-mail]>
Sender: hlu@poly (H.J. Lu)
Organization: Washington State University
References: <[e-mail]> <[e-mail]> <[e-mail]> <[e-mail]>
Date: Tue, 15 Sep 92 18:52:53 GMT
Lines: 28

In article <[e-mail]>, [e-mail] (Kenneth Falck) writes:
|> In article <[e-mail]> [e-mail] (Theodore Y. Ts'o) writes:
|> >Speaking of which, why do you want to write your own terminal program?
|> >What's wrong with kermit that you want to re-invent your own wheel?
|> >
|> >                        - Ted
|>
|> I don't like kermit, I'd like something like Telix for Linux. I'd
|> be happy to try and write one, but using the termcap/curses interface
|> doesn't feel so good, if there is another way. Maybe it wouldn't
|> even be that slow in practice, but theoretically I just don't like
|> the idea of first decoding the incoming VT100 codes, storing the
|> data in a temporary buffer, and then updating that buffer to the
|> console screen by means of some more VT100 codes....
|>
|> I know there is pcomm, but after trying it I decided even kermit
|> or XComm was better. (I compiled pcomm myself though, so maybe I
|> broke something in it that made it behave strangely. Don't
|> remember what happened exactly anymore.)
|>
|> --
|> [e-mail]
|>


Have your tried minicom?

H.J.