From owner-freebsd-ports@FreeBSD.ORG Thu Jun 23 14:25:58 2005 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E2DF16A41C for ; Thu, 23 Jun 2005 14:25:58 +0000 (GMT) (envelope-from fbsd_user@a1poweruser.com) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 489A843D55 for ; Thu, 23 Jun 2005 14:25:58 +0000 (GMT) (envelope-from fbsd_user@a1poweruser.com) Received: from barbish ([69.172.31.81]) by mta9.adelphia.net (InterMail vM.6.01.04.01 201-2131-118-101-20041129) with SMTP id <20050623142557.GFVB29002.mta9.adelphia.net@barbish>; Thu, 23 Jun 2005 10:25:57 -0400 From: "fbsd_user" To: "Lupe Christoph" Date: Thu, 23 Jun 2005 10:25:52 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <1119534995.42babf9358774@buexe.b-5.de> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal Cc: ports@freebsd.org Subject: RE: FreeBSD Port: doorman-0.8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd_user@a1poweruser.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jun 2005 14:25:58 -0000 -----Original Message----- From: Lupe Christoph [mailto:lupe@lupe-christoph.de] Sent: Thursday, June 23, 2005 9:57 AM To: fbsd_user@a1poweruser.com Cc: ports@freebsd.org Subject: RE: FreeBSD Port: doorman-0.8 Quoting fbsd_user : > Doing it your way will work also and is more in line with the 5.x > way of doing things. > But there is still need for a way to stop and/or restart it to get > the updated guestlist file reread. Much like the (stop, start, and > restart) functions for apache. What's wrong with "/usr/local/etc/rc.d/doormand.sh (start|stop|restart)" ? REPLY: THATS FINE WITH ME > And while you are at it the port description is so very poor at > describing the port. > How about something like this: I did not change the description when I took over the port. The description at http://doorman.sourceforge.net/ isn't too descriptive either ;-) I think your's is a little long. I'll see if I can come up with a shorter one for the next release. REPLY: I AGREE WITH YOU THAT THE SOURCEFORGE DESCRIPTION SUCK ALSO. THE CURRENT PORT DESCRIPTION MAY BE SHORT BUT IT REALLY DOES NOT TELL THE READER WHAT THE PORT AS ALL ABOUT. ANY THING YOU CAN DO WOULD BE GREATLY APPECIATED. > One last thing. Doorman has a ms/windows knock program available as > a .zip file. Sure would be nice to have that zip file included with > the port alone with a example Windows's script combining the knock > exec with say FTP or telnet. This is a FreeBSD port. It does not even include the doorman code. Why should it include something that is not even needed to run doorman on FreeBSD? REPLY: BACAUSE MANY FREEBSD USERS HAVE LARGE USER COMMUNITIES THAT USE WINDOWS BOXS TO ACCESS THEIR FREEBSD SERVER THATS WHY. I wrote the current handbooks firewall section and I think this doorman port is so important that I am going to add reference to it in the update I am writing to the firewall section. That is why I have been testing it and corresponding with you about enhancements to the install process. Thanks for your fast replies in this matter. You are doing a good job. Thanks for your support, Luep Christoph -- | lupe@lupe-christoph.de | http://www.lupe-christoph.de/ | | "... putting a mail server on the Internet without filtering is like | | covering yourself with barbecue sauce and breaking into the Charity | | Home for Badgers with Rabies. Michael Lucas |