public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Bart Trojanowski <bart@jukie.net>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] document additional vfat mount options
Date: Sat, 23 Aug 2008 12:10:59 +0900	[thread overview]
Message-ID: <87k5e8ify4.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <1219452859-24960-1-git-send-email-bart@jukie.net> (Bart Trojanowski's message of "Fri, 22 Aug 2008 20:54:19 -0400")

Bart Trojanowski <bart@jukie.net> writes:

Thanks. However, some parts seem not true. I'll change those to the following.

> +nocase        -- If set, files and directories read from device will have
> +                 their names converted to lowercase.  Not set by
> +                 default.

nocase           -- This was deprecated for vfat. Use shortname=win95 instead.

> +showexec      -- If set, files that end if .EXE, .COM, or .BAT will have
> +                 the execute permission bits set.  Not set by default,
> +                 in which case all files show up with the execute bits set.

showexec         -- If set, the execute permission bits of the file will be
		    allowed only if the extension part of the name is .EXE,
                    .COM, or .BAT. Not set by default.

> +sys_immutable -- If set, all files on this filesystem which have the SYS
> +                 attribute (DOS bit) set will become IMMUTABLE (inode flag)
> +                 preventing write operations on these files.  Not set by
> +                 default.

sys_immutable    -- If set, ATTR_SYS attribute on FAT is handled as
		    IMMUTABLE flag on Linux. Not set by default.

> +flush         -- If set, modified inodes will be flushed to disk on file
> +                 close system call.  This is ideal for USB connected
> +                 devices.  Not set by default.

flush            -- If set, the filesystem will try to flush to disk more
		    early than normal. Not set by default.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

      parent reply	other threads:[~2008-08-23  3:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 22:03 vfat BKL/lock_super regression in v2.6.26-rc3-g8f59342 Bart Trojanowski
2008-08-19 22:06 ` [PATCH] make lock_super recursive to simulate BKL Bart Trojanowski
2008-08-19 22:21   ` Linus Torvalds
2008-08-20  1:14     ` Bart Trojanowski
2008-08-19 22:17 ` vfat BKL/lock_super regression in v2.6.26-rc3-g8f59342 Linus Torvalds
2008-08-20  0:03   ` Bart Trojanowski
2008-08-20  0:11     ` Linus Torvalds
2008-08-20  0:24       ` Bart Trojanowski
2008-08-20  0:18   ` Bart Trojanowski
2008-08-20  0:43     ` Linus Torvalds
2008-08-20  0:56       ` Linus Torvalds
2008-08-20  2:27         ` Bart Trojanowski
2008-08-20 21:23           ` Diego Calleja
2008-08-23  0:54           ` [PATCH] document additional vfat mount options Bart Trojanowski
2008-08-23  2:33             ` Grant Coady
2008-08-23  3:12               ` Bart Trojanowski
2008-08-23  3:14                 ` Bart Trojanowski
2008-08-23  3:27                   ` OGAWA Hirofumi
2008-08-23 13:11                     ` Bart Trojanowski
2008-08-23 14:47                       ` OGAWA Hirofumi
2008-08-23  3:10             ` OGAWA Hirofumi [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=87k5e8ify4.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=bart@jukie.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@kernel.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