nix - Rust friendly bindings to *nix APIs

Age	Commit message (Collapse)	Author
2018-10-18	Document ioctl_param_type	Rukai

2018-04-10	Correct the third argument to ioctl on appropriate platforms.	Bryant Mairs
	While usually `ioctl()` passes a pointer, the function call has been overloaded to allow integers to be passed. For some platforms this is an `int` and on others it's a `ulong`. Fixes #824.
2018-04-10	Implement equivalent for _IOWINT for FreeBSD-like targets	Bryant Mairs
	ioctls on FreeBSD and DragonflyBSD have a separate request code generation macro `_IOWINT` which is now exposed as `request_code_write_int`. `ioctl_write_int` is also fixed on these platforms to use this new request
2018-04-10	Refactor the ioctl API and documentation	Bryant Mairs
	* Split `ioctl!` into separate macros. This makes documentation easier to read. * For every `ioctl_!` macro include a description of the macro arguments as, the function prototype for the generated wrapper function, and an example if we have one. Expose `request_code_!` in the documentation to make the `ioctl__bad` macros easier to use. * Reorganize the file hierarchy to be simpler
2017-12-20	Use backticks around types/functions in docs	Bryant Mairs

2017-12-04	Stop reexporting `Errno` and its variants	Jonas Schievink
	cc #664 (unsure if this is everything needed)
2017-07-21	Allow doc attributes in ioctl macro	roblabla

2017-07-19	Refactor ioctl! for buffers	Bryant Mairs
	Instead of relying on the macro user to calculate the length in bytes do that within the macro itself
2017-07-19	Add 'bad' prefixes for read, write_*, and readwrite ioctls	Bryant Mairs

2017-07-19	Split ioctl!(write ...) into write_ptr and write_int	Bryant Mairs
	There two different write semantics used with ioctls: one involves passing a pointer the other involves passing an int. Previously the ioctl! macro did not distinguish between these cases and left it up to the user to set the proper datatype. This previous version was not type safe and prone to errors. The solution here is to split the "write" variant into a "write_ptr" and "write_int" variant that makes the semantics more explicit and improves type safety by specifying arguments better.
2017-07-19	Unify argument names to generated ioctl functions	Bryant Mairs

2017-07-19	Use the proper ioctl number type depending on target	Bryant Mairs
	This also means that we need to properly mask off bits to the valid range of ioctl numbers.
2017-07-19	Revise ioctl module documentation	Bryant Mairs
	This refactors the examples to more directly address the exact use cases for the `ioctl!` macro that `nix` provides. Additionally other macros that should not be used by end users are no longer discussed.
2017-07-19	Remove unnecessary path aliasing	Bryant Mairs

2017-07-19	Hide internal macros/types within ioctl	Bryant Mairs

2017-07-19	Add a "bad none" variant to the ioctl macro	Bryant Mairs

2017-07-19	Re-add bad variant of ioctl!	Bryant Mairs

2017-07-19	Remove old workaround	Bryant Mairs

2017-07-05	We need to pass by value and not by pointer for writing ioctls	Bastian Köcher

2017-04-21	remove test warnings	king6cong

2016-12-10	Add ioctl support for BSD	Conrad Kramer

2016-12-10	Fix typo in documentation	Conrad Kramer

2015-11-20	netbsd support	Jeremy Fitzhardinge

2015-09-15	ioctl: only run ioctl doctest under linux	Paul Osborne

2015-09-15	ioctl: correct documentation and add example ioctl! code	Paul Osborne

2015-08-12	ioctl: reintroduce libc ioctl workaround until we can use updated liblibc	Paul Osborne
	This PR fixes the issue upstream https://github.com/rust-lang/rust/pull/26809 but no version 0.2.0 of the crate has been published as of yet. Signed-off-by: Paul Osborne <osbpau@gmail.com>
2015-08-12	ioctl: remove all but command encoding	Corey Richardson

2015-08-12	Update docs	Corey Richardson

2015-08-12	Completely revamp sys::ioctl to use cmr/ioctl's approach	Corey Richardson
	This is more type-safe. Also, the old code wasn't cross-platform at all even though it claimed to be. It wasn't even portable across architectures on Linux.