From: "Jon Masters" <jonmasters@gmail.com>
To: "Steven Rostedt" <rostedt@goodmis.org>
Cc: "Lee Revell" <rlrevell@joe-job.com>,
"Helge Hafting" <helge.hafting@aitel.hist.no>,
"Chris Ball" <cjb@mrao.cam.ac.uk>,
"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [OT] inotify hack for locate
Date: Thu, 9 Mar 2006 02:44:34 +0000 [thread overview]
Message-ID: <35fb2e590603081844t4c5f062bo7f53088e3085a2a4@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0603070524020.9699@gandalf.stny.rr.com>
On 3/7/06, Steven Rostedt <rostedt@goodmis.org> wrote:
> Hmm, this could also be very useful for change management systems and
> especially backup utilities. Imagine having a daemon that records all the
> changes on a filesystem, and then backs them up periodically. Could very
> well be useful.
Some people have already done similar things with FUSE based
filesystems but my point is that there's nothing cool and useful in
mainline to do what I personally want :-) Anyway, I was catching up
with an old friend as part of this thread and we'll spend some time
over at LinuxWorld Boston hacking on some ideas. Then I'll see what's
worth doing.
Jon.
next prev parent reply other threads:[~2006-03-09 2:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 21:36 Jon Masters
2006-03-05 21:42 ` Jesper Juhl
2006-03-05 21:50 ` Jon Masters
2006-03-06 9:23 ` Helge Hafting
2006-03-06 21:59 ` Pavel Machek
2006-03-05 21:53 ` Robin Holt
2006-03-05 22:02 ` Jon Masters
2006-03-05 21:43 ` Lee Revell
2006-03-05 23:08 ` Benjamin LaHaise
2006-03-05 23:30 ` Måns Rullgård
2006-03-06 21:53 ` Pavel Machek
2006-03-06 22:08 ` Måns Rullgård
2006-03-06 22:22 ` Pavel Machek
2006-03-08 13:56 ` Jan Engelhardt
2006-03-05 23:41 ` Chris Ball
2006-03-06 1:04 ` Jon Masters
2006-03-06 9:31 ` Helge Hafting
2006-03-06 13:10 ` Jon Masters
2006-03-07 0:11 ` Lee Revell
2006-03-07 0:33 ` Jon Masters
2006-03-07 10:26 ` Steven Rostedt
2006-03-09 2:44 ` Jon Masters [this message]
2006-03-06 7:49 ` Arjan van de Ven
2006-03-06 13:12 ` Jon Masters
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=35fb2e590603081844t4c5f062bo7f53088e3085a2a4@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=cjb@mrao.cam.ac.uk \
--cc=helge.hafting@aitel.hist.no \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®