Subject: Re: type inconsistencies
To: None <>
From: None <>
List: tech-kern
Date: 03/09/1995 10:45:18
   Yes.  Check the POSIX 1003.1 spec. for the official prototypes for
   mmap, munmap, mprotect, etc.

POSIX 1003.1 doesn't define any of these, and if it did, I *strongly*
suspect it would have used size_t in the first place.  Right now,
we're not even consistent; mmap(2) uses size_t, but the rest of them
use int.