From owner-freebsd-hackers Tue Jul 31 8:46:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id B2E0137B43E; Tue, 31 Jul 2001 08:45:56 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.217]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id IAA27304; Tue, 31 Jul 2001 08:45:44 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010731163832.A91014@walton.maths.tcd.ie> Date: Tue, 31 Jul 2001 08:45:32 -0700 (PDT) From: John Baldwin To: David Malone Subject: Re: portmap_enable vs. rpcbind_enable Cc: alfred@FreeBSD.org, hackers@FreeBSD.org, Dan Nelson , Dima Dorfman 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 On 31-Jul-01 David Malone wrote: > On Tue, Jul 31, 2001 at 08:33:59AM -0700, Dima Dorfman wrote: >> Dan Nelson writes: >> > 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. >> >> Why not change the names now, but keep the old ones working until, >> say, 5.0 is branched? People moving from 4.x will have enough hurdles >> to jump through as it is, and those using -current will have half a >> year to change it. > > It still is an extra change for people updating from 4.X to 5.0. > Maybe we should just make a portmap_program variable which is set > to portmap in -stable and rpcbind in -current. At least things > would be orthogonal then. > grep portmap_program /etc/defaults/rc.conf portmap_program="/usr/sbin/rpcbind" # path to portmap, if you want a different one. > uname -r 5.0-CURRENT From cvs annotate: 1.71 (eivind 28-Jul-00): portmap_enable="NO" # Run the portmapper service (YES/NO). 1.96 (alfred 19-Mar-01): portmap_program="/usr/sbin/rpcbind" # path to portmap, if you want a different one. 1.1 (jkh 09-Feb-99): portmap_flags="" # Flags to portmap (if enabled). From cvs annotate of rev 1.95: 1.71 (eivind 28-Jul-00): portmap_enable="NO" # Run the portmapper service (YES/NO). 1.3 (jfitz 11-Mar-99): portmap_program="/usr/sbin/portmap" # path to portmap, if you want a different one. 1.1 (jkh 09-Feb-99): portmap_flags="" # Flags to portmap (if enabled). As you can see, we've had the portmap_program knob for 2.5 years now. :) Right now there is no change related to portmap for a 4.x -> 5.0 upgrade. (None that is visible to the user at least.) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message