linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Cc: "Pali Rohár" <pali@kernel.org>
Subject: RE: [PATCH v2 08/10] fs/ntfs3: Add Kconfig, Makefile and doc
Date: Thu, 27 Aug 2020 16:01:39 +0000	[thread overview]
Message-ID: <8fc9d4a25f25472384d9de2b6d5e8111@paragon-software.com> (raw)
In-Reply-To: <63ae69b5-ee05-053d-feb6-6c9b5ed04499@infradead.org>

From: Randy Dunlap <rdunlap@infradead.org>
Sent: Friday, August 21, 2020 8:23 PM
> 
> On 8/21/20 9:25 AM, Konstantin Komarov wrote:
> > This adds fs/ntfs3 Kconfig, Makefile and Documentation file
[]
> > +
> > +- This driver implements NTFS read/write support for normal, sparsed and
> 
>                                                                 sparse
> 
> > +  compressed files.
> > +  NOTE: Operations with compressed files require increased memory consumption;
> > +- Supports native journal replaying;
> > +- Supports extended attributes;
> > +- Supports NFS export of mounted NTFS volumes.
> > +
> > +Mount Options
> > +=============
> > +
> > +The list below describes mount options supported by NTFS3 driver in addtion to
> 
>                                                                        addition
> 
> > +generic ones.

Thanks! Will be fixed in v3.

> > +===============================================================================
[]
> > +
> > +nohidden		Files with the Windows-specific HIDDEN (FILE_ATTRIBUTE_HIDDEN)
> > +			attribute will not be shown under Linux.
> 
> Without this mount option, will HIDDEN files be shown by default?

Yes, correct, without "nohidden" mount option files with FILE_ATTRIBUTE_HIDDEN set will be shown as regular files.

> > +
> > +sys_immutable		Files with the Windows-specific SYSTEM
[]
> > +
> > +- Full journaling support (currently journal replaying is supported) over JBD.
> 
>           journalling
> seems to be preferred.
> 

Have to disagree on this. According to "journaling" term usage in different sources, the single-L seems to be the standard.

> > +
> > +
> > +References
> > +==========
> > +https://www.paragon-software.com/home/ntfs-linux-professional/
> > +	- Commercial version of the NTFS driver for Linux.
> > +
> > +almaz.alexandrovich@paragon-software.com
> > +	- Direct e-mail address for feedback and requests on the NTFS3 implementation.
> > +
> > +
> 
> thanks.
> --
> ~Randy

  reply	other threads:[~2020-08-27 16:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21 16:25 [PATCH v2 08/10] fs/ntfs3: Add Kconfig, Makefile and doc Konstantin Komarov
2020-08-21 17:23 ` Randy Dunlap
2020-08-27 16:01   ` Konstantin Komarov [this message]
2020-08-27 16:15     ` Joe Perches
2020-08-23 10:16 ` Pali Rohár
2020-08-27 16:24   ` Konstantin Komarov

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=8fc9d4a25f25472384d9de2b6d5e8111@paragon-software.com \
    --to=almaz.alexandrovich@paragon-software.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).