From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from yow.a-b.xyz ([45.32.152.219]) by ewsd; Thu Jun  4 08:28:01 EDT 2020
Received: 
	by yow.a-b.xyz (OpenSMTPD) with ESMTPSA id c4ec2f59 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO)
	for <9front@9front.org>;
	Thu, 4 Jun 2020 14:27:46 +0200 (CEST)
Message-ID: <7AB11D189863A13031E8FD10D69FD355@a-b.xyz>
To: 9front@9front.org
Subject: Re: [9front] -d option for fshalt
Date: Thu, 4 Jun 2020 14:27:43 +0200
From: kvik@a-b.xyz
In-Reply-To: <9183627795DC5C421772A3CB7E426121@musolino.id.au>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: patented overflow-preventing standard YAML over SSL CMS engine-scale locator 

Seems like a reasonably useful option to have, though I'm inclined to
suggest a standalone dump [fscons ...] utility as an alternative that
one might conveniently use on its own, or combined with a halt:

	dump && fshalt

> Updated patch follows.

While I'd suggest perusing the new and improved getflags(8) to parse
the arguments the patch looks mostly good to me.

Replace the -* while loop with:

	flagfmt = 'd:dump, r:reboot'
	eval `''{aux/getflags $*} || exec aux/usage

And change "yes / no" to "1 / 0" where appropriate.