Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Date:	3 Sep 1999 11:07:59 -0700
Message-ID:	<19990903180759.15206.cpmta@c005.sfo.cp.net>
X-Sent:	3 Sep 1999 18:07:59 GMT
Mime-Version:	1.0
To:	Cygwin Mailing List <cygwin AT sourceware DOT cygnus DOT com>
From:	Terry Lincoln <wterrylincoln AT icqmail DOT com>
X-Mailer:	Web Mail 3.1
Subject:	RE: Samba 2 running in NT box almost there !!
X-Icq:	39362285

------------=_936382079-14635-0
Content-Type: text/plain
Content-Disposition: inline

Please refresh my memory...

Why is it useful to port an incomplete Linux interface to a M$ Windows file/printer sharing protocol to an OS that has that built on top of that protocol to begin with?

Are we wanting to "dumb-down" NT file and printer sharing?!?! :)

I really would like to know if this is a exersize or simply not well thought out.

Regards,

W. Terry Lincoln




-------------------------------------------------------------
Sign up for ICQmail at http://www.icq.com/icqmail/signup.html
------------=_936382079-14635-0
Content-Type: text/plain; name="Samba 2 running in NT box almost there !!.txt"
Content-Disposition: attachment; filename="Samba 2 running in NT box
    almost there !!.txt"
Content-Transfer-Encoding: 7bit

From: MoMa [siae0071 AT gc DOT ehu DOT es]
Sent: Friday, September 03, 1999 1:55 PM
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Samba 2 running in NT box: almost there !!

Hi,

I have been able to port Samba 2 to an NT box with this setup:
NT 4.0, cygwin Beta 20.1, gcc of this version of cygwin

Well, almost.There is a probleml with the select (cygwin) call in the
samba function sys_select. This select returns inmediately, with
errno=EBADF. This seems akward to me at this point of the server
process, it must be an indicator of a prior error. But the socket opens
correctly some source lines before, and is ready to listen (errno=0).

This prevents the smbd in NT from serving (does not detect the
connection from the client) and the smbclient in NT from receiving the
results of the commands it sends (it connects to a Linux box Samba,
sends commands but does not receive the returning packages).

If we overcome this, Samba will work on NT. I have done a research on
the legal/license implications of this, and look very interesting:
 * The legal limit of 10 connections to an NT workstation dissapear =>
NT server value for NT workstation price, legal.
 * No need for CAL (client access license) to connect to an NT box =>
legal non Win clients, and the NT Terminal server client implications
seem interesting too.

Can someone help withthe select problem?

TIA

Ivan & Ray


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com


------------=_936382079-14635-0
Content-Type: text/plain; charset=us-ascii

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
------------=_936382079-14635-0--

- Raw text -