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
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
Hi Paulo
This looks very interesting. Is the goal here to just replace unfs3 on
a device running a Yocto-based firmware, or is the goal also to enable
the User Space NFS server for development without root privileges as
documented here:
Hello,
On 28/08/2022 19:43:56+0200, Paulo Neves wrote:
> nfs-ganesha is actively maintained in contrast with unfs3. glibc tests
> pass with nfs-ganesha.
>
This fails with:
ERROR: Nothing PROVIDES 'unfs3-native' (but
On Sun, 28 Aug 2022 at 21:13, Alexander Kanavin via
lists.openembedded.org
wrote:
> All newly added or removed patches need an adjustment to
> maintainers.inc in conf/distro/include.
*recipes* :)
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online
On Sun, 28 Aug 2022 at 19:44, Paulo Neves wrote:
> +gcc incorrectly decides that pos_len and pos_end are used
> +unninitialized. It is incorrect because the condition of their
> +use is the same as their early initialization. Apparently
> +gcc does not pick this fact and with Werror, emits an
nfs-ganesha is actively maintained in contrast with unfs3. glibc tests
pass with nfs-ganesha.
Signed-off-by: Paulo Neves
---
meta/lib/oeqa/utils/nfs.py| 2 +-
...ix-possible-null-pointer-dereference.patch | 38 +
...-Workaround-for-erroneous-gcc-Werror.patch | 33
