From: kvik@a-b.xyz
To: 9front@9front.org
Subject: Re: [9front] exportfs: fix debug logging
Date: Mon, 16 Aug 2021 15:55:10 +0200 [thread overview]
Message-ID: <1FB5D1B9C97EB96BD9B642CB8AD1362D@qak> (raw)
In-Reply-To: <03FE47CDA929D330902D308081FB34EC@smtp.pobox.com>
Quoth unobe@cpan.org:
> File servers being anything categorized under section 4? For example,
> I just looked at a few ( cfs(4), cifs(4), sshfs(4) ) which all use -d.
Yea, consistency is WIP. Here's what 9p(2) has to say about it:
By convention, servers written using this library accept the -D
option to increment chatty9p.
Note that some file servers that support -D don't care to document it
in the manual -- specifically because it's a "well known" convention.
cifs(4) from your list is one example.
I do realize now that exportfs mixes the 9p trace and general debug
output, so maybe -d is more appropriate after all. Not sure, and I
certainly don't want to bog down this patch submission with my
bikeshed. We can deal with many consistency issues at some other
time.
next prev parent reply other threads:[~2021-08-16 14:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 1:11 Amavect
2021-08-13 5:16 ` [9front] " Amavect
2021-08-13 19:11 ` [9front] " ori
2021-08-14 22:04 ` Amavect
2021-08-15 16:29 ` kvik
2021-08-16 4:40 ` unobe
2021-08-16 5:20 ` ori
2021-08-16 16:49 ` unobe
2021-08-16 13:55 ` kvik [this message]
2021-08-16 16:50 ` unobe
2021-08-16 17:56 ` Amavect
2021-08-16 19:32 ` ori
2021-08-16 22:48 ` ori
2021-08-18 14:24 ` cinap_lenrek
2021-08-18 14:49 ` k m
2021-08-16 20:19 ` Steve Simon
2021-08-16 23:26 ` ori
2021-08-13 6:46 unobe
2021-08-13 11:15 ` Amavect
2021-08-14 20:14 ` Stuart Morrow
2021-08-15 16:40 ` kvik
2021-08-15 20:44 ` Stuart Morrow
2021-08-16 20:17 ` Humm
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=1FB5D1B9C97EB96BD9B642CB8AD1362D@qak \
--to=kvik@a-b.xyz \
--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).