Bug 2810 - rpcbind: Could we replace portmap with rpcbind
Summary: rpcbind: Could we replace portmap with rpcbind
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: connectivity (show other bugs)
Version: 1.3
Hardware: x86 Multiple
: Low normal
Target Milestone: 1.4
Assignee: Cristian Iorga
QA Contact:
URL:
Whiteboard: 9a1c99916bfc8b599e1fd567b0a61b979576b254
Depends on:
Blocks:
 
Reported: 2012-07-22 02:11 UTC by LiRongQing
Modified: 2013-01-07 13:00 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description LiRongQing 2012-07-22 02:11:08 UTC 
Rpcbind supports more feature than portmap, Like ipv6, nfs4.
So could we replace portmap with rpcbind in image and in init scripts by default.
Comment 1 Saul Wold 2012-07-23 22:31:09 UTC 
What's the size difference in the binary?  Can you summarize the feature differences, specifically are there any features that will be lost do to such a switch?

Are there other conisderations?
Comment 2 LiRongQing 2012-07-24 01:00:09 UTC 
the size of rpcbind+rpcinfo is 240k
the size of portmap+pmap_dump+pmap_set is 100k.

I search on the network, only find that rpcbind has more
feature than portmap, does not find that rpcbind lost
feature than portmap
Comment 3 Alexandru Georgescu 2012-08-27 09:59:25 UTC 
Hello,
Do you have any updates regarding rpcbind vs portmap?

Thanks,
Alex.
Comment 4 LiRongQing 2012-08-27 10:07:03 UTC 
NO
Comment 5 LiRongQing 2012-12-20 02:30:33 UTC 
Redhat, Fedora, debian, Ubuntu are using rpcbind by default, 
If do not using rpcbind, nfs can not work under ipv6 address,
and nfs4 does not work.