From owner-freebsd-current@FreeBSD.ORG Thu Nov 4 03:01:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C744916A4CE for ; Thu, 4 Nov 2004 03:01:07 +0000 (GMT) Received: from auk1.snu.ac.kr (auk1.snu.ac.kr [147.46.100.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CCAD43D1F for ; Thu, 4 Nov 2004 03:01:07 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: from [147.46.44.181] (spamrefuse@yahoo.com) by auk1.snu.ac.kr (Terrace Internet Messaging Server) with ESMTP id 2004110412:00:55:141124.26774.2921622448 for ; Thu, 04 Nov 2004 12:00:55 +0900 (KST) Message-ID: <41899B6F.6010003@yahoo.com> Date: Thu, 04 Nov 2004 12:01:03 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20041017 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TERRACE-SPAMMARK: NO (SR:2.01) (by Terrace) Subject: 5.3: tip / cu serial communication behaviour changed since 4.10 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 03:01:07 -0000 Hello, I have diskless PCs that I connect to by serial port (using null-modem cable). On the "master" PC I successfully use cu or tip as follows: cu -l /dev/cuaa0 or tip sio0 ---- I use to do this with FreeBSD 4.10 on my master PC. I recently have upgraded to 5.3, and found a different behaviour of tip and cu: 1. The bootup process over serial port used to be disconnected with 4.10, before and after kernel loading (each time I had to restart the cu command). With 5.3 this does not happen anymore and the boot process over serial port continues without any disconnections until the login prompt. This is a very nice improvement indeed! 2. When a long command was executed over the serial port (for example 'make buildworld'), I could disconnect by typing '~.`, while the command itself would continue; at a later stage I could get the command's output text by typing the cu or tip command again. This was 4.10 behaviour. However, with 5.3, when I type '~.', then cu/tip is disconnected but also the running command is terminated. This is rather annoying. Regards, Rob.