From owner-freebsd-advocacy Fri Apr 9 20:50:31 1999 Delivered-To: freebsd-advocacy@freebsd.org Received: from mta1-rme.xtra.co.nz (mta.xtra.co.nz [203.96.92.1]) by hub.freebsd.org (Postfix) with ESMTP id 2AB04151CF for ; Fri, 9 Apr 1999 20:50:28 -0700 (PDT) (envelope-from junkmale@pop3.xtra.co.nz) Received: from wocker ([210.55.164.76]) by mta1-rme.xtra.co.nz (InterMail v04.00.02.07 201-227-108) with SMTP id <19990410034943.WYVO5596385.mta1-rme@wocker>; Sat, 10 Apr 1999 15:49:43 +1200 From: "Dan Langille" Organization: The FreeBSD Diary To: Alan Weber Date: Sat, 10 Apr 1999 15:48:15 +1200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: FreeBSD Solutions Cookbook (proposal) Reply-To: junkmale@xtra.co.nz Cc: advocacy@freeBSD.org In-reply-to: <19990409222832.A12535@austin.rr.com> X-mailer: Pegasus Mail for Win32 (v3.01d) Message-Id: <19990410034943.WYVO5596385.mta1-rme@wocker> Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 Apr 99, at 22:28, Alan Weber wrote: > I have a suggestion for a new kind of document that would parallel the > Handbook and FAQ. I am suggesting that a "COOKBOOK" be created with > "RECIPES" for common FreeBSD applications. I am listing below some of the > types of recipes that I am thinking of: I think it's a great idea. This would definitely serve a purpose and meet a need. Some of these setups seem to be FAQ. [samples snipped] IMHO, the two most common configurations I've seen asked for are a Dialup Gateway and a CableModem Gateway. We've all seen lots of messages about those. I can't comment on the complexities of implementing such a solution. But it sounds like you are proposing a "select and go" solution. To me, it looks like that shouldn't be too difficult. It's merely automating the steps listed in various documents. Sounds like a plan. -- Dan Langille The FreeBSD Diary http://www.FreeBSDDiary.com/freebsd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message