From owner-freebsd-isp Fri Sep 18 08:20:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07931 for freebsd-isp-outgoing; Fri, 18 Sep 1998 08:20:04 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from artorius.sunflower.com (artorius.sunflower.com [24.124.0.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07854 for ; Fri, 18 Sep 1998 08:20:00 -0700 (PDT) (envelope-from bsd-isp@artorius.sunflower.com) Received: from artorius.sunflower.com (artorius.sunflower.com [24.124.0.6]) by artorius.sunflower.com (8.8.8/8.8.7) with SMTP id KAA17037; Fri, 18 Sep 1998 10:19:38 -0500 (CDT) (envelope-from bsd-isp@artorius.sunflower.com) Date: Fri, 18 Sep 1998 10:19:38 -0500 (CDT) From: "Stephen D. Spencer" To: frank segner cc: freebsd-isp@FreeBSD.ORG Subject: Re: INN 1.7.2 & Device Not Configured error In-Reply-To: <199809181428.QAA15115@blabla.ip.lu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 18 Sep 1998, frank segner wrote: > I know this might not be a very 'constructive' comment (with respect to the > problem) but have a look at inn-2.1; it runs circles around 1.7.2 (performance > wise) and you don't need any ccd stuff since it's using its > own "CNFS" (Cyclic News File System) > Frank, Heh. I laugh because I was for about 4 weeks. I agree that it is a beautiful piece of work; however, due to the problems with the unified overview lag I was forced to return to 1.7 :( I am awaiting the day when 2.x is happy enough to be used in our production machine with great anticipation. Regards, Stephen --------------------------------------------------------------------- - Stephen Spencer finger gladiatr@artorius.sunflower.com for - - administrator PGP key. - - Sunflower Datavision http://www.sunflower.com - --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message