From: Alex Musolino <alex@musolino.id.au>
To: 9front@9front.org
Subject: Re: [9front] Cannot
Date: Fri, 04 Dec 2020 11:09:02 +1030 [thread overview]
Message-ID: <FE2E188D1CC51E8DB73CE211CE88D0F3@musolino.id.au> (raw)
In-Reply-To: <CABB-WO_sTTgt2Q0e2AhwPATcD7vkQP55kw9pePqZMxvNxReF+w@mail.gmail.com>
Ah, you got me! I didn't actually try that part, figuring I'd
be well done before 5am rolled around again. I just jotted it
down when I came across it in my travels. So, you're right,
startdump is a subcommand of cwcmd. However, looking at it now,
fs(8) says:
startdump [01]
Suspend (0) or restart (1) the background dump process.
But it seems like it actually behaves the other way around:
cpu% con -C /srv/cwfs.cmd
cwcmd startdump 1
dump stopped
cwdcmd startdump 0
dump allowed
\x1c
>>> q
cpu%
Any objections to the following patch to bring cwfs64x inline with the
documentation?
diff -r 91126ac896fa sys/src/cmd/cwfs/cw.c
--- a/sys/src/cmd/cwfs/cw.c Sat Nov 28 23:03:44 2020 +1030
+++ b/sys/src/cmd/cwfs/cw.c Fri Dec 04 11:06:49 2020 +1030
@@ -2281,7 +2281,7 @@
blockcmp(dev, s1, s2);
} else if(strcmp(arg, "startdump") == 0) {
if(argc > 2)
- cw->nodump = number(argv[2], 0, 10);
+ cw->nodump = !number(argv[2], 0, 10);
else
cw->nodump = !cw->nodump;
if(cw->nodump)
next prev parent reply other threads:[~2020-12-04 0:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 8:19 [9front] Cannot install 9front-8013.d9e940a768d1.amd64.iso due to network issues Vladimir Nikishkin
2020-12-02 0:03 ` Josuah Demangeon
2020-12-02 4:03 ` Vladimir Nikishkin
2020-12-02 4:40 ` ori
2020-12-02 5:45 ` Vladimir Nikishkin
2020-12-02 16:46 ` ori
2020-12-02 17:12 ` Stanley Lieber
2020-12-02 18:07 ` ori
2020-12-02 19:03 ` Stanley Lieber
2020-12-03 0:35 ` kvik
2020-12-03 0:52 ` Stanley Lieber
2020-12-03 1:02 ` [9front] Cannot ori
2020-12-03 1:28 ` Stanley Lieber
2020-12-03 1:53 ` ori
2020-12-03 2:54 ` Xiao-Yong Jin
2020-12-03 3:11 ` Stanley Lieber
2020-12-03 3:22 ` Alex Musolino
2020-12-03 3:35 ` kvik
2020-12-03 16:07 ` kvik
2020-12-03 16:36 ` Stuart Morrow
2020-12-04 0:39 ` Alex Musolino [this message]
2020-12-02 7:15 ` [9front] Cannot install 9front-8013.d9e940a768d1.amd64.iso due to network issues Iruatã Souza
2020-12-02 16:44 ` ori
2020-12-03 18:02 ` Stuart Morrow
2020-12-03 18:18 ` hiro
2020-12-03 18:32 ` Stuart Morrow
2020-12-03 18:46 ` hiro
2020-12-03 18:53 ` Stuart Morrow
2020-12-03 19:37 ` hiro
2020-12-06 3:52 ` sl
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=FE2E188D1CC51E8DB73CE211CE88D0F3@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).