Messages in this thread | | | Date | Sun, 30 May 2004 23:06:10 +0200 | From | Andries Brouwer <> | Subject | Re: 2.6.x partition breakage and dual booting |
| |
On Sun, May 30, 2004 at 09:47:15PM +0100, viro@parcelfarce.linux.theplanet.co.uk wrote:
> > Clearly, BLKGETSIZE is obsolescent - it should be replaced by > > BLKGETSIZE64 everywhere. 2^41 B is 2 TB, and some RAIDs are larger. > > ITYM "it should be replaced to lseek(fd, SEEK_END, 0) everywhere".
Roughly speaking, I agree (if you change that to lseek(fd, 0, SEEK_END)).
But in practice, now that we have BLKGETSIZE64, that is much more convenient. How many bits does one get out of lseek? What is the size of off_t? Is perhaps llseek needed? Or lseek64? Complications.
Andries - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |