9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Alex Musolino <alex@musolino.id.au>
To: 9front@9front.org
Subject: Re: [9front] -d option for fshalt
Date: Thu, 4 Jun 2020 23:27:43 +0930	[thread overview]
Message-ID: <976F3A6A48EC099DBF3B49F865DDDF9E@musolino.id.au> (raw)
In-Reply-To: <7AB11D189863A13031E8FD10D69FD355@a-b.xyz>

> 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

Yeah, that's fair comment.  Something like this:

#!/bin/rc
rfork E
if(~ $#* 0){
	c=`{ls /srv/cwfs*cmd >[2]/dev/null}
	h=`{ls /srv/hjfs*cmd >[2]/dev/null}
}
for (i in $* $c $h)
	echo dump >>$i

Perhaps we call it fsdump to go with fshalt?

> 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.

I did think about this but figured I'd do it separately (if at all) in
the interest of keeping the patch small and focused.  Anyway, might
be moot now.


  reply	other threads:[~2020-06-04 13:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02  4:37 Alex Musolino
2020-06-02  4:58 ` [9front] " Alex Musolino
2020-06-02  6:54 ` Alex Musolino
2020-06-02  6:59 ` rgl
2020-06-04  6:57   ` Alex Musolino
2020-06-04 12:27     ` kvik
2020-06-04 13:57       ` Alex Musolino [this message]
2020-06-04 15:50         ` kvik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=976F3A6A48EC099DBF3B49F865DDDF9E@musolino.id.au \
    --to=alex@musolino.id.au \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).