All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <landley@webofficenow.com>
To: Horst von Brand <vonbrand@sleipnir.valparaiso.cl>,
	landley@webofficenow.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS Client patch
Date: Mon, 23 Jul 2001 05:57:34 -0400	[thread overview]
Message-ID: <01072305573400.00996@localhost.localdomain> (raw)
In-Reply-To: <200107230202.f6N228NG016619@sleipnir.valparaiso.cl>
In-Reply-To: <200107230202.f6N228NG016619@sleipnir.valparaiso.cl>

On Sunday 22 July 2001 22:02, Horst von Brand wrote:
> Rob Landley <landley@webofficenow.com> said:
> > On Thursday 19 July 2001 14:24, Pavel Machek wrote:
>
> [...]
>
> > > > No, if the file was removed, it still tells you where to start your
> > > > search.  A missing filename is just as good a marker as a present
> > > > one.
> > >
> > > And if new file is created with same name?
> >
> > The same thing that happens as if a new file was inserted BEFORE your
> > cursor, in the part of the directory you've already looked at.  You
> > ignore it.
>
> Who says that if I've got files A, B, C, D, and delete B, and create a new
> B, whatever underlying directory structure there is will place it where the
> old B was? It might reuse holes before A...

I suppose the assumption was that the directory entries are returned in 
alphabetically sorted order, even if the underlying filesystem doesn't do 
that.  Maybe this is a waste of effort on the server's part (and 
generating/maintaining other sorts of cookies aren't?), but it also seems 
fairly easy to make it work.  (I could easily be missing something obvious...)

Rob

  reply	other threads:[~2001-07-23 18:59 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.3.96L.1010709131315.16113O-200000@happyplace.pdl.cmu.edu.suse.lists.linux.kernel>
2001-07-09 18:33 ` NFS Client patch Andi Kleen
2001-07-10 13:33   ` Chris Wedgwood
2001-07-10 13:41     ` Andi Kleen
2001-07-10 16:48       ` Craig Soules
2001-07-10 17:06         ` Andi Kleen
2001-07-10 18:04           ` Chris Wedgwood
2001-07-12 20:57             ` Alan Cox
2001-07-13 11:26               ` Chris Wedgwood
2001-07-17 22:02   ` Hans Reiser
2001-07-17 22:14     ` Craig Soules
2001-07-17 22:21       ` Hans Reiser
2001-07-18 13:30         ` Daniel Phillips
2001-07-18 14:46           ` Hans Reiser
2001-07-18 14:00         ` Jan Harkes
2001-07-18 14:46           ` Hans Reiser
2001-07-19 18:24             ` Pavel Machek
2001-07-22 15:15               ` Rob Landley
2001-07-23  2:02                 ` Horst von Brand
2001-07-23  9:57                   ` Rob Landley [this message]
2001-07-18 13:57     ` Chris Mason
2001-07-19 11:35       ` Trond Myklebust
2001-07-19 18:02         ` Hans Reiser
2001-07-20  8:50           ` Trond Myklebust
2001-07-20 11:30             ` Hans Reiser
2001-07-20 14:07             ` Chris Mason
2001-07-09 17:28 Craig Soules
2001-07-09 18:59 ` Trond Myklebust
2001-07-09 19:45   ` Craig Soules
2001-07-09 19:53     ` Charles Cazabon
2001-07-09 20:05     ` Trond Myklebust
2001-07-09 22:09       ` Craig Soules
2001-07-10  8:22         ` Trond Myklebust
2001-07-10 13:38           ` Chris Wedgwood
2001-07-11  8:14             ` Trond Myklebust
2001-07-09 21:46     ` J. Richard Sladkey
2001-07-10 15:06       ` Craig Soules

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=01072305573400.00996@localhost.localdomain \
    --to=landley@webofficenow.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vonbrand@sleipnir.valparaiso.cl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.