Re: <fcntl.h> vs <asm/fcntl.h> - total mess.

Alan Cox (alan@lxorguk.ukuu.org.uk)
Wed, 23 Dec 1998 21:28:25 +0000 (GMT)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Guest section DW: "Re: <fcntl.h> vs <asm/fcntl.h> - total mess."
Previous message: Alan Cox: "Re: <fcntl.h> vs <asm/fcntl.h> - total mess."

> situation is a complete mess. The O_xxx flags for open(2) are duplicated in
> the glibc2's <fcntl.h> and the kernel's <linux/fcntl.h> (or <asm/fcntl.h>
> the same). So, if I now implement O_NOFOLLOW or O_NONAME as an enhancement to

Thats intended

> open(2) it is not immediately visible to user space. And if I force user

Equally if you change something incompatibly its not visible in a way where
the library cannot preserve compatibility. Glibc for example doesn't have
32bit inode numbers of 32bit file offset limits.

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Guest section DW: "Re: <fcntl.h> vs <asm/fcntl.h> - total mess."
Previous message: Alan Cox: "Re: <fcntl.h> vs <asm/fcntl.h> - total mess."