Re: Bug#353277: ndiswrapper in main
On Sun, Feb 19, 2006 at 11:11:32AM +0100, Robert Millan wrote:
> On Sat, Feb 18, 2006 at 05:36:37PM +0100, Mike Hommey wrote:
> > On Sat, Feb 18, 2006 at 05:04:54PM +0100, Goswin von Brederlow
> > > The availability to do this is enough even if there are other
> > > (possibly better) ways to do the same. One free driver _in_ Debian and
> > > the package should stay in main.
> > >
> > > But does the cipe-source build or ship the windows driver for use with
> > > ndiswraper? I doubt that.
> > >
> > > Which means you need some software (even if it is free) from outside
> > > Debian for ndiswraper. That makes it contrib imho.
> >
> > Are there any free MSWord files in main ? No ? Then please move
> > antiword and similar tools to contrib.
>
> You're turning this into non-sense. An NDIS wrapper is OBVIOUSLY for the
> exclussive purpose of using non-free Windows drivers. It is so obvious
> because nobody has written [1] free GPLed NDIS drivers. EVER. It has nothing
> to do with Wine and MSWord [2].
>
> So, stop throwing unrelated points to this matter. Just fix the bug. Move this
> to contrib, with all the other warez wrappers.
>
> [1] Written, not ported. I know someone ported that CIPE thing from Linux to
> Windows, but the sole idea of porting something to Windows in order to emulate
> it from Linux makes me laugh.
The sole idea to run Internet Explorer under Wine on Linux makes _me_
laugh. But I've seen people do it. And they were not amused by my
laughing.
The fact that there is at least one GPL driver for ndiswrapper means
that it is possible to use ndiswrapper for useful purposes without
non-free software. And since cipe is not part of the kernel yet, that
might be a good idea anyway if the native driver doesn't work with the
kernel which you're using for some reason while ndiswrapper does.
Which is not _that_ strange, I've seen it often enough with
out-of-(vanilla)-kernel modules.
--
Fun will now commence
-- Seven Of Nine, "Ashes to Ashes", stardate 53679.4
Reply to: