From: Alexander Aring <alex.aring@gmail.com>
To: Roland Hieber <rhi@pengutronix.de>
Cc: "Michael Olbrich" <m.olbrich@pengutronix.de>,
distrokit@pengutronix.de,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [DistroKit] [PATCH] unfs3: Fix generation of export list
Date: Sun, 25 Apr 2021 12:22:25 -0400 [thread overview]
Message-ID: <CAB_54W4BFucyhQqhRHBf6LOowhmejzf0HmRV_QXgp7zFdkcihw@mail.gmail.com> (raw)
In-Reply-To: <20210425153030.clzgu4b5hidhchej@pengutronix.de>
Hi,
On Sun, 25 Apr 2021 at 11:30, Roland Hieber <rhi@pengutronix.de> wrote:
>
> On Thu, Mar 11, 2021 at 06:38:49PM +0100, Uwe Kleine-König wrote:
> > Before this change the content of the export list is by default:
> >
> > / (rw,no_root_squash),insecure
> >
> > which is wrong. The closing parenthesis must be after the insecure
> > keyword.
> >
> > It seems I'm the first user of unfs3 in the v7a platform since 2016.
>
> Hmm, why do we need this file at all? Shouldn't this be included in
> upstream PTXdist too?
>
it adds the "insecure" option. Which is somehow needed because qemu
hostfwd rules and playing proxy with different port numbers. The
"insecure" option allows different port numbers.
"The insecure option in this entry also allows clients with NFS
implementations that don't use a reserved port for NFS."
- Alex
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
prev parent reply other threads:[~2021-04-25 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 17:38 Uwe Kleine-König
2021-03-11 17:52 ` Robert Schwebel
2021-04-25 15:30 ` Roland Hieber
2021-04-25 16:22 ` Alexander Aring [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=CAB_54W4BFucyhQqhRHBf6LOowhmejzf0HmRV_QXgp7zFdkcihw@mail.gmail.com \
--to=alex.aring@gmail.com \
--cc=distrokit@pengutronix.de \
--cc=m.olbrich@pengutronix.de \
--cc=rhi@pengutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
/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