From: Anthony Martin <ality@pbrane.org>
To: 9front@9front.org
Subject: Re: [9front] Re: [PATCH] make exportfs give "standard" error for file does exist
Date: Mon, 24 Jul 2023 23:09:37 -0700 [thread overview]
Message-ID: <ZL9nIWzMtS9cWNeC@alice> (raw)
In-Reply-To: <D1E53774598794A99B1C7464953523B8@eigenstate.org>
ori@eigenstate.org once said:
> note, the problem with strstr is that walking to a file named
> 'file does not exist' may confuse the caller; this is why I
> would like to move to a convention where the "well known" error
> is at a well known location.
1. Spaces in file names are suspect to begin with.
2. If you name a file "file does not exist", you deserve
the consequences.
3. Almost two decades ago, ericvh wanted to standardize
error strings to appease Linux v9fs. Nothing happened.
4. Over a decade ago, rminnich proposed using "%d:%s"
with a prefixed errno for all errors, mostly to appease
Linux v9fs. Nothing happened.
5. All of this only matters because the POSIX tolerators
are trying to parse error strings to make up an "error
code" and do something special for each one so v9fs will
work with vfs_create. How can that ever not be brittle?
6. 9p2000.L, .u, etc. Enough said.
7. This is a lost cause. Outside of Plan 9, friends only
let friends use emu(1).
8. Your idea isn't bad but is it worth it?
Thanks for coming to my TED talk.
Cheers,
Anthony
next prev parent reply other threads:[~2023-07-25 6:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 21:07 [9front] " Jacob Moody
2023-07-23 22:03 ` Stuart Morrow
2023-07-23 22:11 ` Jacob Moody
2023-07-23 22:24 ` Stuart Morrow
2023-07-24 0:19 ` Jacob Moody
2023-07-24 21:20 ` Stuart Morrow
2023-07-24 22:33 ` Jacob Moody
2023-07-24 0:07 ` Michael Forney
2023-07-24 0:56 ` Jacob Moody
2023-07-24 2:12 ` ori
2023-07-24 8:13 ` hiro
2023-07-24 23:37 ` Jacob Moody
2023-07-24 23:54 ` ori
2023-07-24 0:51 ` [9front] " Anthony Martin
2023-07-24 1:03 ` Jacob Moody
2023-07-24 4:13 ` Anthony Martin
2023-07-24 4:20 ` ori
2023-07-25 6:09 ` Anthony Martin [this message]
2023-07-25 8:26 ` hiro
2023-07-25 13:14 ` ori
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=ZL9nIWzMtS9cWNeC@alice \
--to=ality@pbrane.org \
--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).