From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] inherit the auth_chid to exportfs
Date: Sun, 3 Oct 2021 09:36:57 +0000 (UTC) [thread overview]
Message-ID: <b73198bd-1dd4-4d6b-8799-7ca8485659ee@sirjofri.de> (raw)
In-Reply-To: <5B06A2E4FAE111F88C9C3DAF41EA98F4@felloff.net>
02.10.2021 21:55:26 cinap_lenrek@felloff.net:
> this is just wrong!
>
> t9fs service is supposed to dial the disk fileserver,
> you don't just run a exportfs there.
>
> re-exporting your local namespace's /root is different
> form dialing the fileserver directly. it is just needless
> overhead and would break stuff like 9fs dump.
>
> it also breaks multiuser because exportfs does not
> support Tauth over 9p.
It's possible that this is my error on eu.9p.zone. How would I reliably
export the fs to other cpus with tls and without standard 564?
sirjofri
prev parent reply other threads:[~2021-10-03 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 19:32 [9front] no more auth in exportfs(4)? me
2021-10-01 8:49 ` cinap_lenrek
2021-10-01 9:11 ` [9front] [PATCH] inherit the auth_chid to exportfs Josuah Demangeon
2021-10-02 19:55 ` cinap_lenrek
2021-10-03 9:36 ` sirjofri [this message]
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=b73198bd-1dd4-4d6b-8799-7ca8485659ee@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--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).