From: Christoph Hellwig <hch@infradead.org>
To: Steven French <sfrench@us.ibm.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: CIFS VFS
Date: Tue, 1 Oct 2002 11:33:56 +0100 [thread overview]
Message-ID: <20021001113356.A14845@infradead.org> (raw)
In-Reply-To: <OF546A54F5.1325EB3F-ON87256C45.001839EC@boulder.ibm.com>; from sfrench@us.ibm.com on Mon, Sep 30, 2002 at 11:25:40PM -0500
On Mon, Sep 30, 2002 at 11:25:40PM -0500, Steven French wrote:
> Although we are still working through a few bugs found during recent runs
> of the fsx file system test suite against 2.5.38 and 2.5.39 (and working
> on a few new features at the same time), suggestions for improving the
> 2.5 version of the CIFS VFS would be welcome. So far most of the feedback
> (e.g. on the recent addition of NTLMSSP security provider compatability and
> some of the MS DFS work in progress) has been from the Samba community
> (rather than Linux kernel side) since I have been doing much of my testing
> against Samba servers and the project info is hosted there. The current
> 2.5 source for the CIFS VFS is at
Would you mind giving an short outline what the idea behind this filesystem is?
It looks like it's an replacement for smbfs, but what are the advantages and
why didn't you start with smbfs?
next prev parent reply other threads:[~2002-10-01 10:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 4:25 CIFS VFS Steven French
2002-10-01 10:33 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-01 17:30 Steven French
2002-10-01 18:42 ` Matthew Wilcox
2002-10-02 22:13 ` Urban Widmark
2002-10-01 20:00 Petr Vandrovec
2002-10-02 2:17 ` Matthew Wilcox
2002-10-02 2:45 ` Petr Vandrovec
2002-10-01 23:38 Steven French
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=20021001113356.A14845@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sfrench@us.ibm.com \
/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).