From owner-freebsd-questions@FreeBSD.ORG Thu Jul 31 17:33:48 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E925D37B401 for ; Thu, 31 Jul 2003 17:33:48 -0700 (PDT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id D55E743F93 for ; Thu, 31 Jul 2003 17:33:46 -0700 (PDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: from be-well.ilk.org (be-well.no-ip.com[66.30.200.37]) by comcast.net (sccrmhc11) with ESMTP id <20030801003345011005rk66e>; Fri, 1 Aug 2003 00:33:46 +0000 Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37] (may be forged)) by be-well.ilk.org (8.12.9/8.12.9) with ESMTP id h710XjM1043370; Thu, 31 Jul 2003 20:33:45 -0400 (EDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: (from lowell@localhost) by be-well.ilk.org (8.12.9/8.12.6/Submit) id h710XiWV043367; Thu, 31 Jul 2003 20:33:44 -0400 (EDT) X-Authentication-Warning: be-well.ilk.org: lowell set sender to freebsd-questions-local@be-well.ilk.org using -f Sender: lowell@be-well.no-ip.com To: Hugo Saro References: <20030728132447.65348.qmail@web11807.mail.yahoo.com> From: Lowell Gilbert Date: 31 Jul 2003 20:33:44 -0400 In-Reply-To: <20030728132447.65348.qmail@web11807.mail.yahoo.com> Message-ID: <44vfti1ajb.fsf@be-well.ilk.org> Lines: 10 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: linux_llseek X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 00:33:49 -0000 Hmm. If I remember correctly, the linux_llseek() call is just a hack to add a wider-than-32-bit lseek(2) type call without touching anything already in the system. I may be confused, though. In any case, this doesn't really make sense, because it's really just a wrapper around a system call (at least, the normal lseek() is, and I can't imagine why any variant would be implemented much differently). The output may be some kind of artifact caused by the kernel dive, but I don't know why that would happen, either... maybe a -hacker would know.