On Wed, Feb 22, 2006 at 03:52:29AM -0800, Steve Langasek wrote:
> On Wed, Feb 22, 2006 at 12:43:39PM +0100, Wouter Verhelst wrote:
> > What makes 'running free windows drivers for stuff' so much more
> > unrealistic than 'running free windows software for stuff'? Especially
> > seen as how no Windo
On Sat, Feb 18, 2006 at 01:42:38PM +0100, Robert Millan wrote:
> On Sat, Feb 18, 2006 at 12:49:48PM +0100, Wouter Verhelst wrote:
> > On Sat, Feb 18, 2006 at 09:40:26AM +0100, Robert Millan wrote:
> > > I'll ask again: Is the purpose of ndiswrapper running non-free
> > > drivers? If it isn't, sho
Anthony Towns writes:
> On Sat, Feb 18, 2006 at 09:59:07AM -0500, Michael Poole wrote:
> > Anthony Towns writes:
> > > But even if that weren't the case, nasm is an assembler -- it doesn't
> > > rely on assembler code to do anything useful, its purpose is to translate
> > > assembler code. ndiswra
On Sat, Feb 18, 2006 at 09:59:07AM -0500, Michael Poole wrote:
> Anthony Towns writes:
> > But even if that weren't the case, nasm is an assembler -- it doesn't
> > rely on assembler code to do anything useful, its purpose is to translate
> > assembler code. ndiswrapper isn't a driver compiler, it'
Le samedi 18 février 2006 à 09:59 -0500, Michael Poole a écrit :
> Anthony Towns writes:
>
> > But even if that weren't the case, nasm is an assembler -- it doesn't
> > rely on assembler code to do anything useful, its purpose is to translate
> > assembler code. ndiswrapper isn't a driver compiler
Anthony Towns writes:
> But even if that weren't the case, nasm is an assembler -- it doesn't
> rely on assembler code to do anything useful, its purpose is to translate
> assembler code. ndiswrapper isn't a driver compiler, it's a wrapper to
> allow existing drivers to run on Linux.
This apparen
On Sat, Feb 18, 2006 at 08:46:53AM -0500, Michael Poole wrote:
> But nasm requires such assembly for useful execution!
Dude, you're on crack. First, there's apparently free software in
main that you can compile with nasm to your heart's content, namely
crystalspace, drip, e3, effectv, extipl, fl
Robert Millan writes:
> Policy:
>
> "2.2.2 The contrib section
>
> [...]
> Examples of packages which would be included in contrib are:
>
Here's the part that you left out:
* free packages which require contrib, non-free packages or packages
which are not in our archive at all for compila
On Sat, Feb 18, 2006 at 12:49:48PM +0100, Wouter Verhelst wrote:
> On Sat, Feb 18, 2006 at 09:40:26AM +0100, Robert Millan wrote:
> > I'll ask again: Is the purpose of ndiswrapper running non-free drivers?
> > If it
> > isn't, show me a free, non-toy, non-POC driver that would prove otherwise.
>
On Sat, Feb 18, 2006 at 09:40:26AM +0100, Robert Millan wrote:
> I'll ask again: Is the purpose of ndiswrapper running non-free drivers? If
> it
> isn't, show me a free, non-toy, non-POC driver that would prove otherwise.
Does the lack of a free driver which can be used with ndiswrapper mean
th
On Fri, Feb 17, 2006 at 08:14:38PM -0500, Michael Poole wrote:
>
> Then please work to revise [Removed false premise fallacy]
Last time your argument was that free NDIS drivers exist, so the situation is
analogous to wine. Nobody bothered to check, but it turns out that only one
free driver exis
Robert Millan writes:
> I see. From http://cipe-win32.sourceforge.net/ :
>
> "CIPE-Win32 is a port of Olaf Titz's CIPE package from Linux to Windows NT."
>
> I think this is the cipe-source package in debian. If this driver is already
> available, there's no much point in using it via ndiswr
On Feb 17, Robert Millan <[EMAIL PROTECTED]> wrote:
> I see. From http://cipe-win32.sourceforge.net/ :
>
> "CIPE-Win32 is a port of Olaf Titz's CIPE package from Linux to Windows NT."
>
> I think this is the cipe-source package in debian. If this driver is already
> available, there's no muc
On Fri, 2006-02-17 at 23:48 +0100, Robert Millan wrote:
> On Fri, Feb 17, 2006 at 12:40:10PM -0500, Andres Salomon wrote:
> > On Fri, 2006-02-17 at 18:00 +0100, Robert Millan wrote:
> > [...]
> > >
> > > First, I couldn't find any reference to a "GPLed NDIS driver" in
> > > ndiswrapper's
> > > we
On Fri, Feb 17, 2006 at 12:40:10PM -0500, Andres Salomon wrote:
> On Fri, 2006-02-17 at 18:00 +0100, Robert Millan wrote:
> [...]
> >
> > First, I couldn't find any reference to a "GPLed NDIS driver" in
> > ndiswrapper's
> > website, like Michael Poole asserts:
> >
> > http://lists.debian.org/
On Fri, 2006-02-17 at 18:00 +0100, Robert Millan wrote:
[...]
>
> First, I couldn't find any reference to a "GPLed NDIS driver" in ndiswrapper's
> website, like Michael Poole asserts:
>
> http://lists.debian.org/debian-devel/2005/01/msg00381.html
>
I assume he was talking about the CIPE drive
On Fri, Feb 17, 2006 at 07:49:10AM -0800, Debian Bug Tracking System wrote:
> On Fri, 2006-02-17 at 11:22 +0100, Robert Millan wrote:
> > Package: ndiswrapper
> > Severity: serious
> >
> > This package should be in contrib, not main.
>
>
> We've had this discussion. We're not having it again.
On Fri, 2006-02-17 at 11:22 +0100, Robert Millan wrote:
> Package: ndiswrapper
> Severity: serious
>
> This package should be in contrib, not main.
We've had this discussion. We're not having it again. Check the lists
(google for 'ndiswrapper', 'debian', and 'contrib').
signature.asc
Descrip
Package: ndiswrapper
Severity: serious
This package should be in contrib, not main.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-k7
19 matches
Mail list logo
