Date: Thu, 24 Oct 2002 17:09:47 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.org> To: Craig Rodrigues <rodrigc@attbi.com> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/sys aio_cancel.2 aio_error.2 aio_read.2 aio_return.2 aio_suspend.2 aio_waitcomplete.2 aio_write.2 Message-ID: <Pine.NEB.3.96L.1021024170857.33116I-100000@fledge.watson.org> In-Reply-To: <20021024170737.A34595@attbi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It used to be the case that we discouraged the use of the aio code because the kernel side of things was notoriously flakey (and in fact, had security holes). I know there has been quite a bit of cleanup since I last noticed that was the case -- do we know if those concerns still apply, and if so, whether we should stop a scary BUGS message into the aio man pages, rather than just recommending people load the module? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories On Thu, 24 Oct 2002, Craig Rodrigues wrote: > On Thu, Oct 24, 2002 at 10:55:55PM +0200, Philippe Charnier wrote: > > Salut, > > > > Please add the following patch > > OK, I incorporated some minor fixes to aio.4 from Philippe. > Here's what I've got. > -- > Craig Rodrigues > http://www.gis.net/~craigr > rodrigc@attbi.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1021024170857.33116I-100000>