From owner-freebsd-hackers Tue Jul 31 8:26:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 8FBEB37B405; Tue, 31 Jul 2001 08:26:10 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.11.4/8.11.4) id f6VFQ7l08813; Tue, 31 Jul 2001 10:26:07 -0500 (CDT) (envelope-from dan) Date: Tue, 31 Jul 2001 10:26:06 -0500 From: Dan Nelson To: Dima Dorfman Cc: hackers@FreeBSD.ORG, alfred@FreeBSD.ORG Subject: Re: portmap_enable vs. rpcbind_enable Message-ID: <20010731102606.A26323@dan.emsphone.com> References: <20010731114846.42FA73E2F@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010731114846.42FA73E2F@bazooka.unixfreak.org> User-Agent: Mutt/1.3.20i X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Jul 31), Dima Dorfman said: > 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). Probably to keep existing rc.conf's from breaking. Same reason we've still got xntpd_enable. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message