On Thu, Jun 1, 2017 at 1:02 PM, Mark Hatle <mark.ha...@windriver.com> wrote:
> > The rpcbind runs on a privileged port (usually). So either you have to > 're-use' > the system wide on or run your own. On many environments, with a system wide > one, you will clash if someone else is offering the same services. So you are > forced to run your own and/or register then with a different set of port > numbers. > > This is absolutely needed in a multi-user or 'locked system' configuration > where > the user does not have permission to run these types of things. unfsd does not include rpcbind, it optionally uses the system's rpcbind. In the runqemu-export-rootfs case, unfsd does not use any rpcbind at all. Still not seeing anything that would require runqemu-export-rootfs to use custom rpc program numbers. -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
