9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jacob Moody <moody@mail.posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] Re: [PATCH] make exportfs give "standard" error for file does exist
Date: Sun, 23 Jul 2023 20:03:00 -0500	[thread overview]
Message-ID: <80e78967-bbc8-a053-75fe-3033b8f491c3@posixcafe.org> (raw)
In-Reply-To: <ZL3LDWtYUAr-OBzb@alice>

On 7/23/23 19:51, Anthony Martin wrote:
> The lady doth protest too much, methinks.
> 
> Here's a list of all file servers that do not use Enonexist,
> aka "file does not exist" for this purpose:
> 
> 	git/fs
> 	nusb/disk
> 	nusb/serial
> 	nusb/usbd
> 	skelfs
> 
> There's a commonality here. These are 9front snowflakes.
> Just make them use the common error.

Sure, those can be fixed but that is not the problem here.
The problem is that exportfs sends the errstr back from what
it gets from open(2). The kernel gives you back the path attempted
to be accessed in quotes prefixed to 'does not exist'.
Every fileserver using Enotexist would not fix exportfs causing
this issue with v9fs.



  reply	other threads:[~2023-07-24  1:04 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 [this message]
2023-07-24  4:13     ` Anthony Martin
2023-07-24  4:20       ` ori
2023-07-25  6:09         ` Anthony Martin
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=80e78967-bbc8-a053-75fe-3033b8f491c3@posixcafe.org \
    --to=moody@mail.posixcafe.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).