9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] cifsd
Date: Wed, 22 Sep 2010 08:05:11 -0700	[thread overview]
Message-ID: <AANLkTikD+6yaUdDeZGmEsM4CpE4LDyZM0n0Mo-5wL6fn@mail.gmail.com> (raw)
In-Reply-To: <B6A953BB-CEB3-474B-ADE7-F93E625BE04D@mail.nanosouffle.net>

[-- Attachment #1: Type: text/plain, Size: 2145 bytes --]

On Tue, Sep 21, 2010 at 5:35 PM, Akshat <akumar@mail.nanosouffle.net> 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
>>
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 2899 bytes --]

  reply	other threads:[~2010-09-22 15:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21  3:34 cinap_lenrek
2010-09-22  0:35 ` Akshat
2010-09-22 15:05   ` David Leimbach [this message]
2011-04-13  9:54     ` Sergey Kornilovich
2011-04-13 13:39       ` cinap_lenrek
     [not found]       ` <127c3a0c5e2e64da53701bf15949aa08@gmx.de>
2011-04-13 19:13         ` Sergey Kornilovich
     [not found]           ` <8a63b9e03865e2e31f270437530f46a8@gmx.de>
2011-04-13 19:54             ` Sergey Kornilovich
     [not found]               ` <44c6348b3cbf2ea7573e33e6013a21c0@gmx.de>
     [not found]                 ` <BANLkTikGY+Q6Xp94LcGEAq0o=NhjsKRFTg@mail.gmail.com>
2011-04-14 11:52                   ` [9fans] Fwd: cifsd Sergey Kornilovich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikD+6yaUdDeZGmEsM4CpE4LDyZM0n0Mo-5wL6fn@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).