public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Paulo Neves <ptsneves@gmail.com>
To: Adrian Freihofer <adrian.freihofer@gmail.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v3 2/2] nfs-ganesha: Replace unfs3 with nfs-ganesha
Date: Thu, 15 Sep 2022 09:28:17 +0200	[thread overview]
Message-ID: <41567c10-d4b1-9d9a-6a7a-bfb282da06fa@gmail.com> (raw)
In-Reply-To: <04dc909a54c792368fa9285f32160c4c3e39ae8d.camel@gmail.com>

Hello Adrian,

Sorry for my late replies but i can only work on this effort 
sporadically. I was not aware of the issue of runqemu and given that i 
am progressing slowly i definitely will follow the breakdown you suggest.

It is taking me quite longer due to the fact that ntirpc is not 
compatible with tirpc. I spent sometime trying to make it so but it is 
huge increase in scope for the current delivery.

ntirpc is also requiring some adaptations with musl that i did not 
anticipate. Some upstream discussions are also taking a bit longer than 
expected.

Paulo Neves

On 9/14/22 23:19, Adrian Freihofer wrote:
> Hi Paulo
>
> Is it possible to do the transition from unfsd to nfs-ganesha step by
> step?
>
>     1. Add nfs-ganesha
>     2. Refactor runqemu-export-rootfs to work with ganesha.nfsd instead
>        of unfsd.
>     3. Remove unfs3
>
> My conclusion so far is that just removing the unfs3 recipe would break
> runqemu-export-rootfs and some features of runqemu. Therefore I would
> suggest that you send a V4 which only adds nfs-ganesha as a first step.
> Note: There is also a typo: The "-D" from USE_ACL_MAPPING=OFF is
> missing.
>
> Regards,
> Adrian
>
>
>



  reply	other threads:[~2022-09-15  7:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-28 17:43 [PATCH v3 1/2] ntirpc: Add ntirpc recipe Paulo Neves
2022-08-28 17:43 ` [PATCH v3 2/2] nfs-ganesha: Replace unfs3 with nfs-ganesha Paulo Neves
2022-08-28 19:13   ` [OE-core] " Alexander Kanavin
     [not found]   ` <170F981B9326E578.11791@lists.openembedded.org>
2022-08-28 19:15     ` Alexander Kanavin
2022-08-29  9:20   ` Alexandre Belloni
2022-09-12 22:19   ` Adrian Freihofer
     [not found]   ` <17143CF1C30D4B98.24896@lists.openembedded.org>
2022-09-14 21:19     ` Adrian Freihofer
2022-09-15  7:28       ` Paulo Neves [this message]
2022-08-28 19:07 ` [OE-core] [PATCH v3 1/2] ntirpc: Add ntirpc recipe Alexander Kanavin
2022-09-15 10:50 ` Ross Burton
2022-09-15 11:18   ` Paulo Neves

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=41567c10-d4b1-9d9a-6a7a-bfb282da06fa@gmail.com \
    --to=ptsneves@gmail.com \
    --cc=adrian.freihofer@gmail.com \
    --cc=openembedded-core@lists.openembedded.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