Date: Tue, 19 Jun 2007 08:48:46 +0400 From: Andrey Chernov <ache@nagual.pp.ru> To: Tim Kientzle <kientzle@FreeBSD.org> Cc: cvs-all@FreeBSD.org, cvs-src@FreeBSD.org, src-committers@FreeBSD.org, Colin Percival <cperciva@FreeBSD.org>, Bruce Evans <brde@optusnet.com.au> Subject: Re: cvs commit: src/lib/libarchive archive_read_open_fd.c archive_read_open_filename.c Message-ID: <20070619044845.GA46485@nagual.pp.ru> In-Reply-To: <467759A9.9040602@freebsd.org> References: <200706180036.l5I0asac023540@repoman.freebsd.org> <4675DFC8.8060108@freebsd.org> <46760F7A.8020209@freebsd.org> <20070618195605.J43008@delplex.bde.org> <467759A9.9040602@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 18, 2007 at 09:20:57PM -0700, Tim Kientzle wrote: > into whether a particular lseek() request is acceptable. > Many devices can do relative but not absolute seeks. Ah, I understand the problem and it is not related to drivers but misunderstanding what lseek does. lseek changes _virtual_ pointer, not physical. That's driver task to change physical pointer accordingly on the next I/O operation. That's driver task to do it relative or absolute, per what device can. -- http://ache.pp.ru/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070619044845.GA46485>