From owner-freebsd-questions Mon Mar 3 03:28:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA22773 for questions-outgoing; Mon, 3 Mar 1997 03:28:04 -0800 (PST) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA22700 for ; Mon, 3 Mar 1997 03:27:59 -0800 (PST) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id BAA00384; Tue, 4 Mar 1997 01:30:52 +0800 (WST) Date: Tue, 4 Mar 1997 01:30:52 +0800 (WST) From: Adrian Chadd To: questions@freebsd.org cc: steve howe Subject: Re: bugs? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > b) i use "cu" to dial up a vt100 connection. for a long time i > > couldn't figure out how to set vt100 emulation up with "cu". > > (i don't see how "tip" is any better and don't find "cu" as bad as > > people say!). anyway - my connection to this vt100 terminal would > > always close because it would not detect vt100 on my end. the only > > way i could "trick" my set-up was to enter: > > modem none network vt100 on Try running cu inside "screen", screen's termcap entry is very much like the vt100 entry. Try running screen, then before running cu, type : export TERM=vt100 (sh or bash) or whatever it is for your shell. Then run cu, and tell me what happens. (Remember to exit screen when you've finished with it *grin*) Or, try running it inside pcvt for X, and use the vt100 termcap (obviously you'll need X running anyway). Cya. Adrian Chadd