From: Christoph Hellwig <hch@infradead.org>
To: John Ogness <jogness@antivir.de>
Cc: Dave Jones <davej@redhat.com>,
Michael Clark <michael@metaparadigm.com>,
linux-kernel@vger.kernel.org
Subject: Re: File change notification
Date: Sat, 7 Feb 2004 14:01:24 +0000 [thread overview]
Message-ID: <20040207140124.A29298@infradead.org> (raw)
In-Reply-To: <4024A1D8.9060700@antivir.de>; from jogness@antivir.de on Sat, Feb 07, 2004 at 09:29:12AM +0100
On Sat, Feb 07, 2004 at 09:29:12AM +0100, John Ogness wrote:
> I am the current maintainer of Dazuko. Could you please explain your
> "wackiest 2004" comment? Do you know of a better way to intercept system
> calls for 2.2/2.4 kernels *without* patching the kernel source?
better implies it's good - it isn't. In fact it's plain wrong for any
kernel. Do a stackable filesystem if you want to intercept filesystem
calls.
next prev parent reply other threads:[~2004-02-07 14:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 8:29 John Ogness
2004-02-07 14:01 ` Christoph Hellwig [this message]
[not found] <18PG9-4og-27@gated-at.bofh.it>
[not found] ` <18TgF-QJ-7@gated-at.bofh.it>
[not found] ` <18TJE-1qL-3@gated-at.bofh.it>
2003-12-31 19:30 ` René Scharfe
-- strict thread matches above, loose matches on Subject: below --
2003-12-31 16:42 Rüdiger Klaehn
2003-12-31 18:20 ` Javier Fernandez-Ivern
2003-12-31 18:48 ` Rüdiger Klaehn
2004-01-01 1:28 ` Michael Clark
2004-01-01 1:58 ` Dave Jones
2004-01-01 2:18 ` Michael Clark
2004-01-01 2:30 ` Javier Fernandez-Ivern
2004-01-01 13:11 ` Rüdiger Klaehn
2003-12-31 20:49 ` Javier Fernandez-Ivern
2004-01-01 9:02 ` Juergen Hasch
2004-01-01 10:47 ` jw schultz
2004-01-01 12:44 ` Rüdiger Klaehn
2004-01-03 6:32 ` Jan Harkes
2002-11-01 21:31 file " Colin Burnett
2002-11-01 22:19 ` Chris Wright
2002-11-02 15:43 ` 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=20040207140124.A29298@infradead.org \
--to=hch@infradead.org \
--cc=davej@redhat.com \
--cc=jogness@antivir.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@metaparadigm.com \
/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®