From owner-freebsd-isp Sun Mar 9 09:19:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA01199 for isp-outgoing; Sun, 9 Mar 1997 09:19:34 -0800 (PST) Received: from jennifer.pernet.net (jennifer.pernet.net [205.229.0.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA01192 for ; Sun, 9 Mar 1997 09:19:32 -0800 (PST) Received: (from neal@localhost) by jennifer.pernet.net (8.8.4/8.8.4) id LAA22028; Sun, 9 Mar 1997 11:20:07 -0600 (CST) Date: Sun, 9 Mar 1997 11:20:07 -0600 (CST) From: Neal Rigney To: Dror Matalon cc: isp@freebsd.org Subject: Re: ISP Billing Software In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Not the right solution for FreeBSD shops. The solution I'd like to see > would include the following components. > > 1. Server runs of Freebsd and other flavors of Unix. > 2. Use Postgres95 as the database. It works well and it's free. The FreeBSD > or databases. > 3. Use CGI and PERL for the development language. > 4. Use web browsers for front end. > > We've done parts of this in house, but we'd rather focus on being an > ISP than developing billing packages. > Would it be too much of a stretch to suggest maybe a group of us(isp'ers) get together and write this software? It seems that everyone has the same problem: they can't find software that fits their needs exactly. I know what we're using works, but not *exactly* the way we want it to work. Look what the "sommunity" effort has done for FreeBSD, etc. Maybe we can do the same for billing software? > Dror Matalon Voice: 510 649-6110 > Direct Network Access Fax: 510 649-7130 > 2039 Shattuck Avenue Modem: 510 649-6116 > Berkeley, CA 94704 Email: dror@dnai.com > > -- Neal Rigney, PERnet Communications, (409)729-4638 neal@mail.pernet.net