mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Erez Zadok <ezk@cs.sunysb.edu>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, viro@ftp.linux.org.uk,
	hch@infradead.org, Jim Kissel <jlk@osml.eu>
Subject: Re: [PATCH 2/2] Unionfs: clarify usage.txt mount options
Date: Fri, 14 Dec 2007 19:32:46 +0300	[thread overview]
Message-ID: <4762B02E.7030102@msgid.tls.msk.ru> (raw)
In-Reply-To: <11976472822359-git-send-email-ezk@cs.sunysb.edu>

Erez Zadok wrote:

> --- a/Documentation/filesystems/unionfs/usage.txt
> +++ b/Documentation/filesystems/unionfs/usage.txt
[]
> +OPTIONS can be any legal combination one of:
                                       ^^^^^
A small typo.

> +
> +- ro		# mount file system read-only
> +- rw		# mount file system read-write
> +- remount	# remount the file system (see Branch Management below)
> +- incgen	# increment generation no. (see Cache Consistency below)
> +
> +BRANCH-OPTIONS can be either (1) a list of branches given to the "dirs="
> +option, or (2) a list of individual branch manipulation commands, described
> +in the "Branch Management" section below.

Should this (2) choice mention remount operation somehow?
It seems the (2) case is about remount only.

> +The "dirs=" option takes a colon-delimited list of directories to compose
> +the union, with an optional branch mode for each of those directories.
> +Directories that come earlier (specified first, on the left) in the list
> +have a higher precedence than those which come later.  Additionally,

By the way, what is "precedence" here?  I mean, will unionfs always
write to the first rw branch, or is it possible to write to some
deeper branch too?

And finally, can a first (and all of them as well) branch be ro?

Thanks.

/mjt

  reply	other threads:[~2007-12-14 16:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-14 15:47 [GIT PULL -mm] 0/2 Unionfs updates/fixes/cleanups Erez Zadok
2007-12-14 15:48 ` [PATCH 1/2] Unionfs: avoid using drop_pagecache_sb in remount Erez Zadok
2007-12-14 15:48 ` [PATCH 2/2] Unionfs: clarify usage.txt mount options Erez Zadok
2007-12-14 16:32   ` Michael Tokarev [this message]
2007-12-14 16:36     ` Michael Tokarev
2007-12-14 16:58     ` Erez Zadok

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=4762B02E.7030102@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=akpm@linux-foundation.org \
    --cc=ezk@cs.sunysb.edu \
    --cc=hch@infradead.org \
    --cc=jlk@osml.eu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ftp.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

all inboxes | Powered by JetHome®