From owner-freebsd-chat Tue Feb 15 14: 3:12 2000 Delivered-To: freebsd-chat@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by builder.freebsd.org (Postfix) with ESMTP id 234774CBF for ; Tue, 15 Feb 2000 13:28:22 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id NAA03680; Tue, 15 Feb 2000 13:56:13 -0800 (PST) Date: Tue, 15 Feb 2000 13:56:13 -0800 From: Alfred Perlstein To: "Matthew N. Dodd" Cc: Brooks Davis , David Scheidt , Troy Settle , freebsd-chat@FreeBSD.ORG Subject: Re: Gimme FreeBSD anyday! Message-ID: <20000215135613.M17536@fw.wintelcom.net> References: <20000214185255.E17536@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from winter@jurai.net on Tue, Feb 15, 2000 at 12:31:59PM -0500 Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Matthew N. Dodd [000215 09:59] wrote: > On Mon, 14 Feb 2000, Alfred Perlstein wrote: > > uh you mean where it misinterprets disconnect as break? > > FreeBSD does the same exact thing! > > (with options BREAK_TO_DEBUGGER that is.) > > Figure it could have anything to do with how 'break' is done on a serial > line? > > If you've got people rebooting your console servers then you've got other > problems. Er, it doesn't on my machines. I sort of remeber this happening a while back on FreeBSD but that was over a year ago, are you sure it still applies? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message