From: Juergen Hasch <lkml@elbonia.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Michael Welles <mike@bangstate.com>, linux-kernel@vger.kernel.org
Subject: Re: Using get_cwd inside a module.
Date: Sun, 23 Nov 2003 20:40:28 +0100 [thread overview]
Message-ID: <200311232040.29132.lkml@elbonia.de> (raw)
In-Reply-To: <20031122110459.A31359@infradead.org>
Am Samstag, 22. November 2003 12:04 schrieb Christoph Hellwig:
> On Sat, Nov 22, 2003 at 11:45:39AM +0100, Juergen Hasch wrote:
> > > What are the exact requirements of changedfiles or samba?
> >
> > Samba needs to be able to notify a client machine, when a file in a
> > directory changes (i.e. is added/removed/modified/renamed). The directory
> > to be watched is given by the client and can include subdirectories.
>
> Well, reporting a single path component relative to the parent directory
> is doable, there's just no way to have a canonical absolute or
> multi-component pathname.
If dnotify is able to return name and event type for each dnotify event,
it is quite simple to make use of it in Samba. I tested this some time
ago, but it was too much of a hack to consider sending this to the list.
What are the chances of such an extension being accepted in the
kernel at all ?
>From the LKML archives I haven't seen much love for dnotify and I
think only few Samba users would consider using a custom kernel.
...Juergen
next prev parent reply other threads:[~2003-11-23 19:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-22 0:05 Michael Welles
2003-11-22 0:32 ` Maciej Zenczykowski
2003-11-22 12:30 ` Szymon Acedański
2003-11-22 8:30 ` Christoph Hellwig
2003-11-22 9:33 ` Juergen Hasch
2003-11-22 10:15 ` Christoph Hellwig
2003-11-22 10:45 ` Juergen Hasch
2003-11-22 11:04 ` Christoph Hellwig
2003-11-22 17:22 ` Michael Welles
2003-11-23 19:40 ` Juergen Hasch [this message]
2003-11-22 11:48 ` Andreas Dilger
2003-11-23 19:41 ` Juergen Hasch
2003-11-22 17:15 ` Michael Welles
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=200311232040.29132.lkml@elbonia.de \
--to=lkml@elbonia.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@bangstate.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®