[meta-xilinx] How to develop?

[Nathan Rossi]

> -----Original Message-----
> From: Rich Wilson [mailto:richaw at gmail.com]
> Sent: Tuesday, April 29, 2014 3:21 PM
> To: Nathan Rossi
> Cc: aland at softorchestra.com; meta-xilinx at yoctoproject.org
> Subject: Re: [meta-xilinx] How to develop?
> 
> 	>       > How about nfs?
> 	>
> 	>       > # mount 192.168.1.40:/ /mnt
> 	>       > mount: wrong fs type, ... you might need a
> /sbin/mount.<type>
> 	> helper
> 	>       > program)
> 	>
> 	>
> 
> 
> 
> 
> 	You are going to want to add nfs-utils to your image. Core-image-
> minimal leaves it out by default, just add something similar to below to
> your local.conf to get it in your rootfs:
> 
> 	CORE_IMAGE_EXTRA_INSTALL += "nfs-utils"
> 
> 	You will then have mount.nfs and the associated userspace daemon
> stuff for NFS. And nfs should then just work.
> 
> 	Regards,
> 	Nathan
> 
> 
> 
> 
> 
> That didn't work. There was no mount.nfs in the target filesystem.

Hmm, not sure what is going wrong, when I build an image with nfs-utils I get the mount.nfs/etc.

$ tar -tf core-image-minimal-qemuzynq.tar.gz | grep nfs
...
./sbin/mount.nfs4
./sbin/umount.nfs
./sbin/mount.nfs
./sbin/umount.nfs4
...

> 
> I finally gave up trying to do it the "Yocto way": I found a copy of
> mount.nfs
> in the work directory, and copied it to my SD card. The nfs mount now
> works.
> 
> I have no idea how to fix/configure the nfs-utils package so that it
> includes mount.nfs
> in the target filesystem during bitbake.
> I suppose I should report this on the yocto mailing list.

Definitely worth taking this issue to the yocto/oe-core mailing lists, might be a known bug?

Regards,
Nathan