From owner-freebsd-hackers@FreeBSD.ORG  Tue Jul  8 18:05:49 2003
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 869F137B401
	for <hackers@freebsd.org>; Tue,  8 Jul 2003 18:05:49 -0700 (PDT)
Received: from intarweb.us (pool-138-88-176-214.res.east.verizon.net
	[138.88.176.214])
	by mx1.FreeBSD.org (Postfix) with SMTP id 503F043F85
	for <hackers@freebsd.org>; Tue,  8 Jul 2003 18:05:48 -0700 (PDT)
	(envelope-from exarkun@intarweb.us)
Received: from meson ([127.0.0.1])
	by meson with smtp (Twisted 1.0.6)
	for hackers@freebsd.org; Tue, 08 Jul 2003 21:05:46 -0400
Date: Tue, 8 Jul 2003 21:05:43 -0400
From: Jp Calderone <exarkun@intarweb.us>
To: hackers@freebsd.org
Message-ID: <20030709010543.GA6014@intarweb.us>
References: <20030708192342.GA4899@intarweb.us>
	<20030708203026.GM87950@dan.emsphone.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030708203026.GM87950@dan.emsphone.com>
User-Agent: Mutt/1.3.25i
Subject: Re: telldir()/seekdir() confusion
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jul 2003 01:05:49 -0000

On Tue, Jul 08, 2003 at 03:30:26PM -0500, Dan Nelson wrote:
>
> [snip]
> 
> I don't think there's any pstandard that says that telldir has to
> return a seekable file offset, or that consecutive calls on the same
> position must return the same value.  Think about a filesystem that
> uses hashed or btree-based directories, for example; there may not be a
> way to store the correct position in a single "long" value without
> using a cookie like FreeBSD does.
> 

  Thanks, it all makes sense now.

  Jp