Re: Dealing with drivers that need firmware on the filesystem

2005-01-12 Thread Manoj Srivastava
On Sun, 9 Jan 2005 14:00:51 +, Matthew Garrett <[EMAIL PROTECTED]> said: > As you say, there's a couple of practical issues. There's also the > fact that putting something in contrib is something of a judgement - > we're saying that this driver needs non-free code to work, and as a > result i

Re: Dealing with drivers that need firmware on the filesystem

2005-01-12 Thread Michael K. Edwards
On Wed, 12 Jan 2005 01:57:08 -0600, Manoj Srivastava <[EMAIL PROTECTED]> wrote: [snip] > Software that resides on disk, however, lives on our side of > the divide; the kernel, and the filesystem drivers are required to > mediate delivery of this non-free payload to the system, and it can'

Re: documentation x executable code

2005-01-12 Thread Michael K. Edwards
On Wed, 05 Jan 2005 14:49:36 +0100, Florian Weimer <[EMAIL PROTECTED]> wrote: > * Craig Sanders: > > > and, as you pointed out yourself, this freedom (to patch) exists > > even when it is not explicitly granted by the license. > > Without permission from the author, you may not redistribute patch

Re: documentation x executable code

2005-01-12 Thread Sam Couter
Craig Sanders <[EMAIL PROTECTED]> wrote: > right. even after 6 days you can't come up with any answer to over 70 lines > of argument in that message, so you retreat to the position of a coward and a > cretin - delete all but one flippant throw-away line and make a stupid > ad-hominem attack based

Re: Dealing with drivers that need firmware on the filesystem

2005-01-12 Thread Matthew Garrett
Manoj Srivastava <[EMAIL PROTECTED]> wrote: > I must confess I do not see it that way. I think of Debian as > distriuting softwware that runs on a platform, this platform consists > of hardware, and, perhaps, associated software burned into > ROM/flash. We do not distribute the hardware

Re: Dealing with drivers that need firmware on the filesystem

2005-01-12 Thread Glenn Maynard
On Wed, Jan 12, 2005 at 12:17:05AM -0800, Michael K. Edwards wrote: > Do you think it would be tolerable to exclude non-free firmware images > from the kernel binary and modules themselves but to permit loading > them from the initrd or the root filesystem? I. e., treat the > firmware download fun

subscribe

2005-01-12 Thread Jonas Goes
-- []'s Jonas Goes http://goes.eti.br -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Dealing with drivers that need firmware on the filesystem

2005-01-12 Thread Michael K. Edwards
> Once the hardware's out there, it's out there--I don't think the case of > "all devices with firmware in flash have been tracked down and destroyed, > so we have to move this driver back to contrib" is a serious worry. I was thinking more of the cases, "skipping the firmware download used to res

Re: Dealing with drivers that need firmware on the filesystem

2005-01-12 Thread Peter Vandenabeele
On Wed, Jan 12, 2005 at 10:33:40AM +, Matthew Garrett wrote: > Manoj Srivastava <[EMAIL PROTECTED]> wrote: > > > I must confess I do not see it that way. I think of Debian as > > distriuting softwware that runs on a platform, this platform consists > > of hardware, and, perhaps, asso

Re: Dealing with drivers that need firmware on the filesystem

2005-01-12 Thread Steve Langasek
On Wed, Jan 12, 2005 at 09:27:43PM +0100, Peter Vandenabeele wrote: > On Wed, Jan 12, 2005 at 10:33:40AM +, Matthew Garrett wrote: > > Manoj Srivastava <[EMAIL PROTECTED]> wrote: > > > I must confess I do not see it that way. I think of Debian as > > > distriuting softwware that runs

Re: documentation x executable code

2005-01-12 Thread Craig Sanders
On Wed, Jan 12, 2005 at 09:15:47PM +1100, Sam Couter wrote: > Craig Sanders <[EMAIL PROTECTED]> wrote: > > right. even after 6 days you can't come up with any answer to over 70 lines > > of argument in that message, so you retreat to the position of a coward and > > a > > cretin - delete all but