From: Taesoo Kim <taesoo-3s7WtUTddSA@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: searching checkpoints contaning an inode (or a filename)
Date: Fri, 5 Jul 2013 16:17:01 -0400 [thread overview]
Message-ID: <20130705201701.GE23851@taesoo.org> (raw)
Hi nilfs,
I am evaluating nilfs for using it in my machine. There are a few
questions regarding usages:
q1. how can I enumerate a list of cps, given a filename?
(I know I can mount each cp to check whether there is my file or
not, as time-machine (in mac) does)
q2. compute diff or cat against previous files in a specific cp?
(instead of mounting and copying them individually to my /tmp)
q3. using nilfs as rootfs?
(I couldn't find any people using nilfs for rootfs. Are there any
issue on that? or just matter of performance? on updates for
example)
Nilfs looks conceptually nice and clean, so I can trust the
implementation or jump directly into modifying code. Do you have any
design notes (other than one in /Documentation and overview-nilfs1.pdf).
Thank you in advance.
Taesoo
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2013-07-05 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 20:17 Taesoo Kim [this message]
[not found] ` <20130705201701.GE23851-Q1ymHw66ZoYdnm+yROfE0A@public.gmane.org>
2013-07-05 21:48 ` searching checkpoints contaning an inode (or a filename) Jérôme Poulin
[not found] ` <CALJXSJrLo_5=e-M41vXyuS9SbRyeZ=zjLYv2Hs3a8Dt+BwS6ig-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-06 8:03 ` Vyacheslav Dubeyko
2013-07-06 8:17 ` Vyacheslav Dubeyko
2013-07-06 7:34 ` Vyacheslav Dubeyko
[not found] ` <B16ADF79-9EF9-46E8-95F8-9D4815E86C64-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-07-06 9:50 ` Ryusuke Konishi
[not found] ` <20130706.185038.523614087.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2013-07-06 11:24 ` Taesoo Kim
2013-07-06 7:52 ` Vyacheslav Dubeyko
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=20130705201701.GE23851@taesoo.org \
--to=taesoo-3s7wtutddsa@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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