Jesse Pollard wrote:
>
> Daniel Phillips <[EMAIL PROTECTED]>:
> > Jamie Lokier wrote:
> > >
> > > Daniel Phillips wrote:
> > > > DN_OPEN A file in the directory was opened
> > > >
> > > > You open the top level directory and register for events. When somebody
> > > > opens a subdir
Daniel Phillips <[EMAIL PROTECTED]>:
> Jamie Lokier wrote:
> >
> > Daniel Phillips wrote:
> > > DN_OPEN A file in the directory was opened
> > >
> > > You open the top level directory and register for events. When somebody
> > > opens a subdirectory of the top level directory, you
Jamie Lokier wrote:
>
> Daniel Phillips wrote:
> > DN_OPEN A file in the directory was opened
> >
> > You open the top level directory and register for events. When somebody
> > opens a subdirectory of the top level directory, you receive
> > notification and register for events on
Daniel Phillips wrote:
> DN_OPEN A file in the directory was opened
>
> You open the top level directory and register for events. When somebody
> opens a subdirectory of the top level directory, you receive
> notification and register for events on the subdirectory, and so on,
> do
Jamie Lokier wrote:
> Daniel Phillips wrote:
> > [things that can benefit from dnotify]
> > locate (reindex only those directories that have changed, keep index
> > database current).
>
> Not a chance. dnotify doesn't work recursively, so you can't monitor
> just a few top level directories like
Jamie Lokier wrote:
>
> Daniel Phillips wrote:
> > It was done last year, quietly and without fanfare, by Stephen Rothwell:
> >
> > http://www.linuxcare.com/about-us/os-dev/rothwell.epl
> >
> > This may be the most significant new feature in 2.4.0, as it allows us
> > to take a fundamentally di
- Received message begins Here -
>
> Jesse Pollard wrote:
> > Daniel Phillips <[EMAIL PROTECTED]>:
> > > This may be the most significant new feature in 2.4.0, as it allows us
> > > to take a fundamentally different approach to many different problems.
> > > Three that come to
Daniel Phillips wrote:
> It was done last year, quietly and without fanfare, by Stephen Rothwell:
>
> http://www.linuxcare.com/about-us/os-dev/rothwell.epl
>
> This may be the most significant new feature in 2.4.0, as it allows us
> to take a fundamentally different approach to many different
Daniel Phillips wrote:
> > It would also be very nice if the security of the feature could be
> > confirmed. The problem with SGI's implementation is that it becomes
> > possible to monitor files that you don't own, don't have access to,
> > or are not permitted to know even exist.
>
> To receive
Jesse Pollard wrote:
> Daniel Phillips <[EMAIL PROTECTED]>:
> > This may be the most significant new feature in 2.4.0, as it allows us
> > to take a fundamentally different approach to many different problems.
> > Three that come to mind: mail (get your mail instantly without polling);
> > make (d
Daniel Phillips <[EMAIL PROTECTED]>:
> "Michael D. Crawford" wrote:
> >
> > Regarding notification when there's a change to the filesystem:
> >
> > This is one of the most significant things about the BeOS BFS filesystem, and
> > something I'd dearly love to see Linux adopt. It makes an app ver
"Michael D. Crawford" wrote:
>
> Regarding notification when there's a change to the filesystem:
>
> This is one of the most significant things about the BeOS BFS filesystem, and
> something I'd dearly love to see Linux adopt. It makes an app very efficient,
> you just get notified when a direc
On Mon, 8 Jan 2001, Sean R. Bright wrote:
> I was writing a user space application to monitor a folder's contents. The
> folder itself contained 100 folders, and each of those contained 24 folders.
> While writing the code to traverse the directory structure I realized that
> instead of my softw
"Sean R. Bright" <[EMAIL PROTECTED]> writes:
> Ok, before I begin, don't shoot me down, but I had an idea for a kernel
> modification and was wondering how feasible the group thought it was.
>
> I was writing a user space application to monitor a folder's contents. The
> folder itse
On Mon, Jan 08, 2001 at 11:12:24PM +, Michael D. Crawford wrote:
[snipped a lot of sane opinions]
> While Be, Inc.'s implementation is closed-source, the design of the
> BFS (_not_ "befs" as it is sometimes called) is explained in Practical
> File System Design with the Be File System by Domi
age-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Michael D.
> Crawford
> Sent: Monday, January 08, 2001 6:12 PM
> To: [EMAIL PROTECTED]
> Subject: Re: FS callback routines
>
>
> Regarding notification when there's a change to the filesystem:
>
Regarding notification when there's a change to the filesystem:
This is one of the most significant things about the BeOS BFS filesystem, and
something I'd dearly love to see Linux adopt. It makes an app very efficient,
you just get notified when a directory changes and you never waste time poll
Ok, before I begin, don't shoot me down, but I had an idea for a kernel
modification and was wondering how feasible the group thought it was.
I was writing a user space application to monitor a folder's contents. The
folder itself contained 100 folders, and each of those contain
18 matches
Mail list logo
