From owner-freebsd-questions Tue Sep 23 15:47:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA10608 for questions-outgoing; Tue, 23 Sep 1997 15:47:29 -0700 (PDT) Received: from cerberus.partsnow.com (gatekeeper.partsnow.com [207.155.26.98]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA10596 for ; Tue, 23 Sep 1997 15:47:16 -0700 (PDT) Received: (from bin@localhost) by cerberus.partsnow.com (8.8.5/8.6.9) id PAA19420; Tue, 23 Sep 1997 15:46:03 -0700 (PDT) X-Authentication-Warning: cerberus.partsnow.com: bin set sender to using -f Received: from nouvelle(192.168.100.9) by cerberus.partsnow.com via smap (V2.0) id xma019414; Tue, 23 Sep 97 15:45:52 -0700 Message-ID: <34284662.6179@PartsNow.com> Date: Tue, 23 Sep 1997 15:44:50 -0700 From: Don Wilde Reply-To: don@PartsNow.com Organization: Soligen, Incorporated X-Mailer: Mozilla 3.0C-E-KIT (Win16; I) MIME-Version: 1.0 To: Brian Reichert CC: freebsd-questions@FreeBSD.ORG Subject: Re: serial console: CPU reset? References: <19970923174222.00473@numachi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk If you dare, there's no reason why you can't hardwire an open collector transistor to one of the handshake lines and cause it to pull the reset line, but of course you run the risk of trashing your filesystem since it wouldn't be an orderly shutdown. A better choice would be a running daemon akin to upsd that would initiate shutdown. -- oooOOO O O O o * * * * * * o ___ _________ _________ ________ _________ _________ ___==_ V_=_=_DW ===--- Don Wilde [don@PartsNow.com] [http://www.PartsNow.com ] /oo0000oo-oo--oo-ooo---ooo-ooo---ooo-ooo--ooo-ooo---ooo-ooo---ooo-oo--oo