Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 20 Jan 2003 18:52:47 +0100 From: Marcel Telka To: cygwin@cygwin.com Cc: cygwin-apps@cygwin.com Subject: Re: Announce: ioperm-0.2.1 for cygwin released Message-ID: <20030120175247.GD28535@tortuga.etc.sk> References: <20030120145735.GC28535@tortuga.etc.sk> <20030120150543.GC27717@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030120150543.GC27717@redhat.com> User-Agent: Mutt/1.4i On Mon, Jan 20, 2003 at 10:05:43AM -0500, Christopher Faylor wrote: > On Mon, Jan 20, 2003 at 03:57:35PM +0100, Marcel Telka wrote: > >This software adds support for ioperm() function to Cygwin. This support > >includes sys/io.h and sys/perm.h header files (not included in Cygwin by > >default) together with development and runtime libraries. > > > >News in this release: > > * Windows DDK is optional for compilation now > > * --prefix=/usr parameter for ./configure script is not mandatory now > > > >Homepage: http://openwince.sourceforge.net/ioperm/ > > Is there some reason you're not proposing this as a standard cygwin package? There are at least two reasons: 1. A device driver (ioperm.sys) is required for running ioperm with NT/2000/XP 2. Windows DDK is required for the driver compilation. If these drawbacks are acceptable for a standard cygwin package I could start ioperm integration with mainstream cygwin net distribution. Any votes? :-) CC'ed to cygwin-apps@cygwin.com Have a nice day -- +-------------------------------------------+ | Marcel Telka e-mail: marcel@telka.sk | | homepage: http://telka.sk/ | | jabber: marcel@jabber.sk | +-------------------------------------------+ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/