From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <942b16624b4735bb1535f9aa1d352f8d@gmx.de> Date: Wed, 13 Apr 2011 13:54:34 +0400 Message-ID: From: Sergey Kornilovich To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001636e90f89c223ed04a0c9cb79 Subject: Re: [9fans] cifsd Topicbox-Message-UUID: d0052256-ead6-11e9-9d60-3106f5b1d025 --001636e90f89c223ed04a0c9cb79 Content-Type: text/plain; charset=ISO-8859-1 Trying to connect the vac file through cifsd. net use Y: \ \ 192.168.0.190 \ 1.vac (/ lib/vac/1.vac exist and "9fs 1.vac" command mount 1.vac in / n / 1) But on the windows client receives: C: \> net use Y: \ \ 192.168.0.190 \ 1.vac pause for 1 minute System error 64 has occurred. The specified network name is no longer available. Show you how to do it right? P.S. Local connection works fine. C: \> net use Y: \ \ 192.168.0.190 \ local The command completed successfully. 2010/9/22 David Leimbach > > > On Tue, Sep 21, 2010 at 5:35 PM, Akshat wrote: > >> Just for the official record: cifsd works perfectly fine with Windows 7. >> >> Cinap's approach to the problem of packet-based protocols is elegant, >> efficient, and through the invent of printf-alike functions, fits well with >> the Plan 9 programming suite/style. >> > > Looks like a LinkedIn recommendation! I would use this but I've been > happily windows free for years now. Windows 7 seems to be drawing people > back in, but I'm not sure I want to make the leap yet. Depends if Apple > turns Mac OS X into the iOS developer platform only or not I suppose. > > Dave > > >> >> Well done. >> ak >> >> On Sep 20, 2010, at 20:34, cinap_lenrek@gmx.de wrote: >> >> after doing some patching on aquarela, wrote a cifs/smb server >>> from scratch and got it down to 3350 lines of code. >>> >>> it uses binary regular expressions to unpack and pack the >>> various nested sub-structures in the packets. >>> >>> /n/sources/cinap_lenrek/cifsd.tgz >>> http://9hal.ath.cx/usr/cinap_lenrek/cifsd.tgz >>> >>> features include: >>> >>> run from listen(8) as none, so more secure. >>> >>> uses syslog() for informational logging (auth/share >>> accesses/errors/warnings). debug tracing can be done with a separate >>> debug trace file. >>> >>> open/read/write/close/rename/delete files and directories. >>> >>> fixed auth so it doesnt fail half the time. the trick was to delay the >>> auth failure to the TREE_CONNECT_ANDX, otherwise windows >>> will try over and over again with wrong password and username >>> combinations. >>> >>> moving files/directories works by returning a special error code to >>> instruct the client to do a recursive copy. >>> >>> impements/pretends enougth IPC$/rap to get the local share listed. >>> >>> not implemented: >>> >>> oplocks >>> wildcard matching (will do (again)) >>> netbios nameservice >>> named pipes/mailslots >>> setting file attributes >>> NT_TRANSACT / acls >>> anything i'v not seen while testing with w2k and wxp >>> >>> i'm interested in feedback. expecially tests with vista or w7. >>> >>> -- >>> cinap >>> >>> >>> >> > --001636e90f89c223ed04a0c9cb79 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Trying to connect the vac file through cifsd.
net use Y: \ \ 192.168= .0.190 \ 1.vac (/ lib/vac/1.vac exist and "9fs 1.vac" command mou= nt 1.vac in / n / 1)
But on the windows client receives:
C: \> net= use Y: \ \ 192.168.0.190 \ 1.vac
pause for 1 minute
System error 64 has occurred.

The specified ne= twork name is no longer available.

Show you how to do it right?
<= br>P.S. Local connection works fine.
C: \> net use Y: \ \ 192.168.0.1= 90 \ local
The command completed successfully.

2010/= 9/22 David Leimbach <leimy2k@gmail.com>


On Tue, Sep 21, 2010 a= t 5:35 PM, Akshat <akumar@mail.nanosouffle.net> wr= ote:
Just for the official record: cifsd works perfectly fine with Windows 7.
Cinap's approach to the problem of packet-based protocols is elegant, e= fficient, and through the invent of printf-alike functions, fits well with = the Plan 9 programming suite/style.

Looks like a LinkedIn recommendation! =A0I would use this but I've been= happily windows free for years now. =A0Windows 7 seems to be drawing peopl= e back in, but I'm not sure I want to make the leap yet. =A0Depends if = Apple turns Mac OS X into the iOS developer platform only or not I suppose.=

Dave
=A0

Well done.
ak

On Sep 20, 2010, at 20:34, cinap_lenrek@gmx.de wrote:

after doing some patching on aquarela, wrote a cifs/smb server
from scratch and got it down to 3350 lines of code.

it uses binary regular expressions to unpack and pack the
various nested sub-structures in the packets.

/n/sources/cinap_lenrek/cifsd.tgz
http://9hal.ath.cx/usr/cinap_lenrek/cifsd.tgz

features include:

run from listen(8) as none, so more secure.

uses syslog() for informational logging (auth/share
accesses/errors/warnings). =A0debug tracing can be done with a separate
debug trace file.

open/read/write/close/rename/delete files and directories.

fixed auth so it doesnt fail half the time. the trick was to delay the
auth failure to the TREE_CONNECT_ANDX, otherwise windows
will try over and over again with wrong password and username
combinations.

moving files/directories works by returning a special error code to
instruct the client to do a recursive copy.

impements/pretends enougth IPC$/rap to get the local share listed.

not implemented:

oplocks
wildcard matching (will do (again))
netbios nameservice
named pipes/mailslots
setting file attributes
NT_TRANSACT / acls
anything i'v not seen while testing with w2k and wxp

i'm interested in feedback. expecially tests with vista or w7.

--
cinap





--001636e90f89c223ed04a0c9cb79--