From owner-freebsd-stable Wed Mar 27 7: 9:57 2002 Delivered-To: freebsd-stable@freebsd.org Received: from bobo.thehutt.org (pcp709198pcs.alxndr01.va.comcast.net [68.49.240.9]) by hub.freebsd.org (Postfix) with ESMTP id BA04D37B416 for ; Wed, 27 Mar 2002 07:09:37 -0800 (PST) Received: from [10.0.3.13] (helo=nomad.thehutt.org ident=mailnull) by bobo.thehutt.org with esmtp (Exim 4.01) id 16qF3R-000FBh-00; Wed, 27 Mar 2002 10:09:37 -0500 Received: from jerry by nomad.thehutt.org with local (Exim 4.01) id 16qF3Q-0001l9-00; Wed, 27 Mar 2002 10:09:36 -0500 Date: Wed, 27 Mar 2002 10:09:36 -0500 From: Jerry A! To: John Cc: stable@freebsd.org Subject: Re: HEADS UP: sendmail 8.12.2 MFC'ed Message-ID: <20020327150936.GA6621@nomad.thehutt.org> Reply-To: jerry@thehutt.org References: <200203262226.XAA27664@galaxy.de.cp.philips.com> <026501c1d561$90d61de0$0200a8c0@gauss> <002201c1d59c$0b1a6c20$6501a8c0@techgodz.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002201c1d59c$0b1a6c20$6501a8c0@techgodz.com> User-Agent: Mutt/1.3.28i Organization: Broken Toys Unlimited Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Mar 27, 2002 at 08:31:11AM -0600, John wrote: : : I'm a *nix newbie. I ran into this the other day. Had my system completely : up and running. (Internet gateway, NAT box, several other packages config'd : successfully). Decided I wanted to install Bind9. : I cvsup'd, and went in and installed Bind9 from ports. : Config'd it according to the bind9 doc, and when I started named, naturally : it started 8.2.4 (Free 4.4 Rel), rather than the 9.2.1.rc1 that I had : installed. Now I've got Bind installed twice, and have no idea what's the : best way to get it working properly. : I'll have to bait friends over with beer and pizza to get them to help me : fix :( You should have named installed twice. All ports by default install under the /usr/local hierarchy. See hier(7) for how the filesystems are laid out. You should also get used to reading through /etc/defaults/rc.conf and seeing what the default values are for various apps. Then you'll know what to set in /etc/rc.conf to override the defaults. See rc.conf(5) for more details. I shouldn't do this, but the quick answer to your question is to insert the following in your /etc/rc.conf. named_enable="YES" named_program="/usr/local/sbin/named" : Is there doc for the ports tree apps ANYWHERE that describes locations that : things are installed to, or what config files are necessary, possibly even : how to admin different apps when installed from the ports tree?? : (Especially since it seems that when installed from ports, it doesn't : install them in their default locations.. thus I have named in : /usr/local/sbin, and /usr/sbin...) Check out the ports(7) man page. It's chock full o' goodness. There you'll find a pointer to pkg_info(1) which is the program you'll use to see the contents of an installed package/port. Also, check out chapter 4 of the FreeBSD Handbook, "Installing Applications: Packages and Ports". : I'm a beginner, and my biggest help with my FreeBSD boxes is a linux guy, : who keeps telling me "FreeBSD is F'Kd up. They do things screwey". I can say the same thing about Linux. I can point out examples of inconsistencies ad infinitum. Having an attitude like that doesn't help. Point out that no two UNIX-like OS's have the exact same setups or behave exactly the same. When I was starting out on this stuff a long time ago, someone described this as "character" and "flavor". : My experiences with cvsup and installing from ports were excellent, until I : ran into the Bind prob. Well, I hope I helped somewhat and that you've got the groundwork for enjoying this stuff and making it work for you. --Jerry Open-Source software isn't a matter of life or death... ...It's much more important than that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message