All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaya Potter <spotter@cs.columbia.edu>
To: Ashish Khurange <ashishk@it.iitb.ac.in>
Cc: Al Viro <viro@ftp.linux.org.uk>, linux-fsdevel@vger.kernel.org
Subject: Re: get vfsmount from dentry
Date: Sun, 12 Mar 2006 15:45:39 -0500	[thread overview]
Message-ID: <1142196339.4954.58.camel@localhost.localdomain> (raw)
In-Reply-To: <441485C5.4090900@it.iitb.ac.in>

On Mon, 2006-03-13 at 02:04 +0530, Ashish Khurange wrote:
> Al Viro wrote:
> 
> >mkdir /tmp/1
> >mkdir /tmp/2
> >mkdir /tmp/3
> >mount --bind /tmp/2 /tmp/1
> >mkdir /tmp/1/a
> >umount /tmp/1
> >mount --bind /tmp/3 /tmp/1
> >mkdir /tmp/1/a
> >umount /tmp/1
> >
> >What output do you want to get from the last two mkdir() calls, assuming
> >you do have vfsmounts?  What is this output useful for?
> >  
> >
> Well, forget about this particualr case.
> My final aim is to build online file system mirroring tool for home 
> directories. And lets assuming that no other user have superuser 
> privilage to use mount or make symbolic links to directories.
> I want entire pathname of changed file to replicate that change on the 
> corresponding file in the mirror site.

look at inotify.  beagle monitors entire home directory via inotify.


  reply	other threads:[~2006-03-12 20:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-12 13:44 get vfsmount from dentry Ashish Khurange
2006-03-12 13:55 ` Al Viro
2006-03-12 17:20   ` Ashish Khurange
2006-03-12 17:41     ` Al Viro
2006-03-12 18:00       ` Ashish Khurange
2006-03-12 18:23         ` Shaya Potter
2006-03-12 18:54           ` Ashish Khurange
2006-03-12 19:13             ` Al Viro
2006-03-12 20:34               ` Ashish Khurange
2006-03-12 20:45                 ` Shaya Potter [this message]
2006-03-13  7:24                 ` Jan Hudec
2006-03-12 18:24         ` Al Viro
2006-03-12 19:10 ` Jamie Lokier

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=1142196339.4954.58.camel@localhost.localdomain \
    --to=spotter@cs.columbia.edu \
    --cc=ashishk@it.iitb.ac.in \
    --cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.