From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH-2.6.6-rc2-bk] NTFS 2.1.7 release: Implement NFS exporting
Date: Mon, 26 Apr 2004 17:01:33 +0100 [thread overview]
Message-ID: <1082995293.5754.8.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <408D31DC.6040708@tmr.com>
On Mon, 2004-04-26 at 16:59, Bill Davidsen wrote:
> Anton Altaparmakov wrote:
> > Linus, please do a
> >
> > bk pull http://linux-ntfs.bkbits.net/ntfs-2.6
> >
> > Thanks! This update implements NFS exporting of mounted NTFS volumes
> > which people have been requesting for a while. Also, there are some minor
> > updates and white space cleanups. This has been tested including forcing
> > a server reboot while clients have open files on an NTFS volume NFS
> > exported by the server.
>
> Sounds like tha answer to the maiden's prayer. And if it will allow both
> NFS and SMB access to the same data, I know some people who will find
> it most useful.
It certainly should allow both NFS and SMB access to the same data. At
least I don't see any reason why it shouldn't work...
But keep in mind that whilst the ntfs driver can read everything (except
encrypted files) at present it can only overwrite existing files without
changes in file size...
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ &
http://www-stu.christs.cam.ac.uk/~aia21/
prev parent reply other threads:[~2004-04-26 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 20:03 Anton Altaparmakov
2004-04-26 15:59 ` Bill Davidsen
2004-04-26 16:01 ` Anton Altaparmakov [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=1082995293.5754.8.camel@imp.csi.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=akpm@osdl.org \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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
all inboxes | Powered by JetHome®