From owner-freebsd-stable Wed May 12 13:36: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from troi.csw.net (troi.csw.net [209.136.192.23]) by hub.freebsd.org (Postfix) with ESMTP id 6D9B115D9A for ; Wed, 12 May 1999 13:35:58 -0700 (PDT) (envelope-from lambert@cswnet.com) Received: from gronk (gronk.csw.net [209.136.201.13]) by troi.csw.net (8.9.2/8.9.3) with SMTP id PAA51781 for ; Wed, 12 May 1999 15:35:57 -0500 (CDT) (envelope-from lambert@cswnet.com) Message-Id: <199905122035.PAA51781@troi.csw.net> From: lambert@cswnet.com Date: Wed, 12 May 1999 15:26:05 -0500 To: freebsd-stable@freebsd.org Subject: What happenned to the INN-1.7.2 port?? X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v1.60 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey guys, I just almost had my new news system ready to roll with INN 1.7.2 on 3.1-19990218-STABLE. I needed to change a config option and recompile but the INN port is now CVSupped to INN-2.2 and there is now an INN-STABLE but it's 2.2-stable. Enough stuff has changed in INN 2.2 that my Managing USENET book doesn't help much. Can I readd the old INN-1.7.2 port as maybe INN-1.7.2 in my ports tree somehow? Or do I get to go back to the 19990218-SNAP of -STABLE? Do I need to not follow -STABLE for production machines? I was hoping following -STABLE would improve the stability/security of my production machines. It's bit me in the *** twice this week. I started trying to keep -STABLE last week after thinking about it for several months before. Maybe tracking -STABLE requires that you have several years of *nix admin experience? I have about six months experience. Thanks in advance, Scott Lambert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message