linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: sedat.dilek@gmail.com
Cc: dhowells@redhat.com, Al Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: Status of union-mount?
Date: Fri, 22 Mar 2013 01:38:55 +0000	[thread overview]
Message-ID: <3190.1363916335@warthog.procyon.org.uk> (raw)
In-Reply-To: <CA+icZUVj4jChaGSdC5Lu4R9h-NzVx8HqT+tnve9GOMh84C5sVw@mail.gmail.com>

Sedat Dilek <sedat.dilek@gmail.com> wrote:

> Hmmm, sorry for asking, but when do you plan to offer a "working"
> union-mount (u-m)?

It's a maze of twisty locking problems - some of which also apply to things
like overlayfs:-(

> What's the status of the user-space tools or are they no more needed?

You need to be able to tell mount(2) that you want a union.  This is currently
done with a mount flag, but it might be portable to something in the mount
option string.

> AFAICS the original authors patched e2fsprogs etc. (see Valerie's old
> homepage [1]).

Yeah... I guess fsck programs need to be able to handle whiteout and fallthru
directory entries.

> >> Where does the development happen - in [1]?
> >
> > On a git tree on my PC - which is occasionally mirrored in [1] when I've got
> > it working.
> >
> 
> Development on your local workstation does not look like you do an
> open development.

Excuse me.  But it's quite hard to develop this on a remote git tree.
Further, I prefer not to push partially working stuff to my git tree, lest
someone pull it, try playing with it and have their fs eaten.

If someone wants it, I can mail the partially working stuff to them, but not
many people ask.

> So, it's currently only you doing the work on u-m?

Almost entirely, yes.

David

      parent reply	other threads:[~2013-03-22  1:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 16:55 Status of union-mount? Sedat Dilek
2013-03-12 17:18 ` Mark Knecht
2013-03-13  9:53   ` Sedat Dilek
2013-03-12 17:19 ` David Howells
2013-03-13  9:57   ` Sedat Dilek
2013-03-22  1:38   ` David Howells [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=3190.1363916335@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --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).