Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Mon, 20 Aug 2001 16:25:21 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Samba for Cygwin Message-ID: <20010820162521.A4064@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20010820154601.B1186@redhat.com> <3B816B6E.9070107@ece.gatech.edu> <033501c129b4$ef718190$0d76aec7@D4LHBR01> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <033501c129b4$ef718190$0d76aec7@D4LHBR01>; from march@indirect.com on Mon, Aug 20, 2001 at 01:15:50PM -0700 On Mon, Aug 20, 2001 at 01:15:50PM -0700, Michael F. March wrote: >I happen to prefer the administration of Samba to traditional NT/2k >shares. That is also why I use Apache under Win2K instead of >IIS. In this case, I'd just have to say "Get over it". It sounds like an a lot of work to port a file service layer on top of an *existing* completely operational layer. Administration of shares on Windows is hardly complicated. The Windows OS doesn't implicitly support the http protocol. So, you can choose whatever web server you want. Windows does implicitly support the SMB protocol. It invented the SMB protocol. In this case porting a UNIX application to Windows to support something that existed on Windows first doesn't make much sense to me. I can just see the "Why is Samba so slow on Cygwin?" posts now. >> That's like asking to port WINE to Cygwin (or port cygwin to WINE). >> It's a gee-whiz proof-of-concept, but has no practical value. > >I believe there is a WINE port to Cygwin. Many of the Wine developers >wanted to be able to develope Wine under Windows. It's hard to understand how this could work, unless they're also using the Cygwin XFree86 server. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/