Re: DCACHE Pinning Problems with rm -r on 2.2.15/2.3.99Pre3 withNWFS2.2.2

• Next message: Jamie Lokier: "Re: DCACHE Pinning Problems with rm -r on 2.2.15/2.3.99Pre3 withNWFS2.2.2"
• Previous message: Marco Colombo: "Re: Avoiding *mandatory* overcommit..."
• In reply to: Jamie Lokier: "Re: DCACHE Pinning Problems with rm -r on 2.2.15/2.3.99Pre3 withNWFS2.2.2"
• Next in thread: Trond Myklebust: "Re: DCACHE Pinning Problems with rm -r on 2.2.15/2.3.99Pre3 withNWFS2.2.2"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, 4 Apr 2000, Jamie Lokier wrote:

> Stephen C. Tweedie wrote:
> > > In fact, I already do have a scheme for doing this with persistent
> > > offsets, problem is that they are not always ascending.
> >
> > That's OK, as long as there is some magic value that can seek to
> > a sequence point in the directory even if files are being added
> > and removed, things will work fine.
>
> Beware that Glibc assumes it can do LSEEK_CUR using the difference
> between two offsets...

glibc is b0rken, film at 11.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Jamie Lokier: "Re: DCACHE Pinning Problems with rm -r on 2.2.15/2.3.99Pre3 withNWFS2.2.2"
• Previous message: Marco Colombo: "Re: Avoiding *mandatory* overcommit..."
• In reply to: Jamie Lokier: "Re: DCACHE Pinning Problems with rm -r on 2.2.15/2.3.99Pre3 withNWFS2.2.2"
• Next in thread: Trond Myklebust: "Re: DCACHE Pinning Problems with rm -r on 2.2.15/2.3.99Pre3 withNWFS2.2.2"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Apr 07 2000 - 21:00:11 EST