From: Dave Lukes <davel@anvil.com>
To: 9fans <9fans@cse.psu.edu>
Subject: Re: [9fans] Re TO_DO
Date: Wed, 25 Feb 2004 16:47:30 +0000 [thread overview]
Message-ID: <1077727650.19238.211.camel@zevon> (raw)
In-Reply-To: <adb43ba861dd71160d647339dc7b3001@snellwilcox.com>
> I am crawling up the (grubby) learning curve of CIFS
> with a view to re-writing/fixing/updating a CIFS client
> I have from the labs.
Good luck:-(.
> As supplied it nearly works, supporting Unicode and long
> filenames but no user/group names or meaningfull file modes.
Wow! I'm impressed!
> The major problem is still the sketchy docco - though this
> has improved, there is still no single "protocol spec".
Pragmatically, you don't care about CIFS or some random document:
what you care about "can it connect to Win95/98/NT/ME/2K/XP/..."?
samba's smbd has a bucketload (i.e. ~~10) options to control
exactly which permutation of SMB/CIFS it supports,
which is very little help.
IM_H_O, we need a "which particular set of braindamage?" enumeration
somewhere in all SMB clients and servers.
Cheers,
Dave.
prev parent reply other threads:[~2004-02-25 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 15:45 plan9fans
2004-02-25 16:47 ` Dave Lukes [this message]
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=1077727650.19238.211.camel@zevon \
--to=davel@anvil.com \
--cc=9fans@cse.psu.edu \
/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).