From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu, 19 Jan 2012 08:13:15 -0500
To: 9fans@9fans.net
Message-ID: <775c7c1b939e51d3388833c7ac553712@chula.quanstro.net>
In-Reply-To: <20120119123025.2b8ce9a3@wks-ddc.exosec.local>
References: <647a5922-dfbd-45d2-b9ec-829523b7f2d1@k10g2000yqk.googlegroups.com>
	<20120119123025.2b8ce9a3@wks-ddc.exosec.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] issuing fshalt shuts down rio and gives the following
Topicbox-Message-UUID: 5eb9ae40-ead7-11e9-9d60-3106f5b1d025

On Thu Jan 19 06:31:30 EST 2012, 0intro@gmail.com wrote:
> > Recently, I noticed a change from what I do not recall to be the
> > behavoiur I saw some time ago
> >
> > When I issue an fshalt, it shuts down rio and give the following
> > outside rio
> > init: starting /bin/rc
> > term%
>
> Yes, I got surprised when I first saw this change in may 2011,
> but it's just normal behavior.
>
> It kills rio and get back to cga mode to be able to reboot properly.

given that output, it is not clear that fshalt is really halting.
(expect, using kernel $fu...)

can you still run normal commands afterwards, or has your fs
shut down?  you may wish to sprinkle some echoes in the
fshalt script and see where things fail.

- erik