Does anybody know (remember?) why portmap_enable (the rc.conf knob) wasn't renamed to rpcbind_enable when portmap became rpcbind? It seems odd to have a knob called portmap_enable that actually starts something called rpcbind (not to mention violating POLA). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- RE: portmap_enable vs. rpcbind_enable Dima Dorfman
- RE: portmap_enable vs. rpcbind_enable John Baldwin
- Re: portmap_enable vs. rpcbind_enable David O'Brien
- Re: portmap_enable vs. rpcbind_enable Dima Dorfman
- Re: portmap_enable vs. rpcbind_enable David Malone
- Re: portmap_enable vs. rpcbind_enable John Baldwin
- Re: portmap_enable vs. rpcbind_enable Dima Dorfman
- Re: portmap_enable vs. rpcbind_enable Alfred Perlstein
- Re: portmap_enable vs. rpcbind_enable Warner Losh
- Re: portmap_enable vs. rpcbind_enable Brian Somers
- Re: portmap_enable vs. rpcbind_enable Warner Losh