Re: why sys_socketcall() is not implemented as an ioctl?

From: Jes Sorensen (jes@linuxcare.com)
Date: Fri Jun 23 2000 - 11:27:46 EST

Next message: Tigran Aivazian: "Re: closefd: closes a file of any process"
Previous message: Tim Waugh: "Re: closefd: closes a file of any process"
Next in thread: uaca@alumni.uv.es: "Re: why sys_socketcall() is not implemented as an ioctl?"
Reply: uaca@alumni.uv.es: "Re: why sys_socketcall() is not implemented as an ioctl?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>>>>> "Ulisses" == <uaca@alumni.uv.es> writes:

Ulisses> Is there any special reason because sys_socketcall() is not
Ulisses> implemented as an ioctl()?

Historical reasons, on modern architectures like the Alpha and ia64 we
don't implement sys_socketcall() anyway.

Jes

-
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: Tigran Aivazian: "Re: closefd: closes a file of any process"
Previous message: Tim Waugh: "Re: closefd: closes a file of any process"
Next in thread: uaca@alumni.uv.es: "Re: why sys_socketcall() is not implemented as an ioctl?"
Reply: uaca@alumni.uv.es: "Re: why sys_socketcall() is not implemented as an ioctl?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:26 EST