Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 30 Jul 2004 11:41:11 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: how about providing Sniff+ support out of cygwin (thus elliminati ng need of MKS use) ? Message-ID: <20040730154111.GC27432@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <313680C9A886D511A06000204840E1CF08F430A5 AT whq-msgusr-02 DOT pit DOT comms DOT marconi DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <313680C9A886D511A06000204840E1CF08F430A5@whq-msgusr-02.pit.comms.marconi.com> User-Agent: Mutt/1.4.1i On Fri, Jul 30, 2004 at 11:35:05AM -0400, Povolotsky, Alexander wrote: >>We really don't want to go down the road of trying to figure out how to >>integrate a competing product's shell with cygwin. > >Then - how about providing Sniff+ support out of Cygwin (thus >eliminating the need for MKS) ? I am not familiar with Sniff+. I assume it's a free software application or you wouldn't be suggesting this. I think you should surely go for it if you need this functionality. You don't need anyone's permission to add a package to the distribution: http://cygwin.com/setup.html . cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/