Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 22 Jan 2003 07:01:40 +0100
From: Marcel Telka <marcel AT telka DOT sk>
To: cygwin AT cygwin DOT com
Subject: Re: Announce: ioperm-0.2.1 for cygwin released
Message-ID: <20030122060139.GD1136@tortuga.etc.sk>
References: <20030120150543 DOT GC27717 AT redhat DOT com> <20030120145735 DOT GC28535 AT tortuga DOT etc DOT sk> <20030120150543 DOT GC27717 AT redhat DOT com> <5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20030120103012 DOT 02ace590 AT pop3 DOT cris DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5.2.0.9.2.20030120103012.02ace590@pop3.cris.com>
User-Agent: Mutt/1.4i

On Mon, Jan 20, 2003 at 10:42:58AM -0800, Randall R Schulz wrote:
> Marcel et. al.,
> 
> At 09:52 2003-01-20, Marcel Telka wrote:
> >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? :-)
> 
> 
> Regarding (1): Are we ("We" Kemo Sabe?) not crossing a boundary here?

Yes. But this crossing is optional.

> 
> Up to now we've been able to say that Cygwin does not install drivers or 
> other kernel-mode software and, the recent "/etc" business notwithstanding, 
> have been able to claim that BSODs, hangs and other nastiness cannot be 
> blamed on Cygwin.

My idea for ioperm is:
After package installation user must by hand install ioperm.sys driver.
So, no automatic driver installation in postinstall script.

> 
> Will this added capability be optional so those who don't need it and who 
> would prefer to avoid the potential instability of added driver software 
> (and I emphasize _potential_, not wanting to impugn anyone's programming 
> abilities) can avoid it altogether?

Yes. ioperm package installation will be optional (like any other cygwin
package is).

> 
> Am I being overly cautious? Paranoid?

That is ok :-).


Thank you.

-- 
+-------------------------------------------+
| Marcel Telka   e-mail:   marcel AT telka DOT sk  |
|                homepage: http://telka.sk/ |
|                jabber:   marcel AT jabber DOT 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/