public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jra@dp.samba.org
To: Steven French <sfrench@us.ibm.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org, jra@samba.org
Subject: Re: [BK PATCH] CIFS filesystem for Linux 2.5
Date: Thu, 10 Oct 2002 20:14:22 +0000	[thread overview]
Message-ID: <20021010201422.C3579@dp.samba.org> (raw)
In-Reply-To: <OFFB04937F.1EAC8996-ON87256C4E.006DA4CF@boulder.ibm.com>; from sfrench@us.ibm.com on Thu, Oct 10, 2002 at 03:08:53PM -0500

On Thu, Oct 10, 2002 at 03:08:53PM -0500, Steven French wrote:
> The CIFS filesystem has been updated to handle yesterday's changes to the
> superblock structure and has been added to a new bitkeeper repository as a
> single bitkeeper changset in order to be easier to apply.  It is changeset
> number 1.747 at bk://cifs.bkbits.net/linux-2.5-with-cifs  and is low risk,
> not changing core kernel files.
>
> ...... stuff cut......
> 
> The CIFS file system is ready to be included in the 2.5 Linux kernel and
> only affects the usual small set of files outside its own directory
> (fs/cifs) that a filesystem must change (e.g. fs/Config.in, fs/Makefile,
> fs/Config.help) but does not require changes to any core kernel code.
> 
> The filesystem is designed for remote access to Samba, newer Windows
> servers and also the many common CIFS based NAS appliances, but unlike
> smbfs is optimized for the current version of the SMB/CIFS protocol.   The
> CIFS file system can coexist with smbfs.   The CIFS file system is
> reasonably stable, passing most but not all of the standard filesystem test
> suites going to either Windows servers or Samba (NB a few Samba bug which I
> am working is blocking fsx at the moment and memory mapping support is not
> finished) running with the current 2.5 kernel.  It has been tested at both
> Connectathon and the CIFS Plugfest this year and has been under development
> for over a year with the assistance from some others on the Samba team as
> well as feedback from the standards group (SNIA CIFS Technical Workgroup)
> and others at IBM.    The project web site has more information on the
> project http://us1.samba.org/samba/Linux_CIFS_client.html

I don't know if it will help, but here's my 2 cents (US :-). I'd love
this to be included into 2.5.x Linux, as it is a very nicely written,
modern CIFS client that we can use to start adding UNIX specific extensions
into Samba, and hopefully end up with a filesystem that uses UNIX semantics
when talking to a Samba server, and will fall back to Windows semantics
when talking to lagacy Windows server (I really love saying that :-) :-).

Should be a big help in making Linux the "universal client glue" we know
and love .... :-).

Cheers,

	Jeremy Allison,
	Samba Team.

  reply	other threads:[~2002-10-10 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 20:08 [BK PATCH] CIFS filesystem for Linux 2.5 Steven French
2002-10-10 20:14 ` jra [this message]
2002-10-10 21:10 ` David Woodhouse
     [not found] <OFFB04937F.1EAC8996-ON87256C4E.006DA4CF@boulder.ibm.com.suse.lists.linux.kernel>
     [not found] ` <17092.1034284232@passion.cambridge.redhat.com.suse.lists.linux.kernel>
2002-10-10 22:00   ` Andi Kleen

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=20021010201422.C3579@dp.samba.org \
    --to=jra@dp.samba.org \
    --cc=jra@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfrench@us.ibm.com \
    --cc=torvalds@transmeta.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