|> On Sun, Dec 30, 2001 at 05:10:41PM -0500, Brian Gerst wrote:
|> > > As user application are trying to use unistd.h and expect errno to get
|> > > set properly unistd.h or at least it's syscallX macros will have to be
|> > > made unusable from userspace or silent breakage of such apps rebuild
|> > > against new headers will occur.
|> > Userspace should be using glibc's unistd.h. If it's using the kernel's,
|> > it's broken.
|> A sufficient number take the unavailability of new syscall in everybody's
|> glibc as a sufficient excuse for broken code. util-linux as a major
|> offender comes to mind or also e2fsprogs.
Userspace should be using syscall(2/3) for new syscalls.
-- Andreas Schwab "And now for something Andreas.Schwab@suse.de completely different." SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/