Re: non-free firmware in kernel modules, aggregation and unclear copyright notice.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Apr 05, 2005 at 04:05:07PM +0200, Josselin Mouette wrote:
> Le lundi 04 avril 2005 à 21:32 +0200, Adrian Bunk a écrit :
> > On Mon, Apr 04, 2005 at 09:05:18PM +0200, Marco d'Itri wrote:
> > > On Apr 04, Greg KH <[email protected]> wrote:
> > > 
> > > > What if we don't want to do so?  I know I personally posted a solution
> > > Then probably the extremists in Debian will manage to kill your driver,
> > > like they did with tg3 and others.
> > 
> > And as they are doing with e.g. the complete gcc documentation.
> > 
> > No documentation for the C compiler (not even a documentation of the 
> > options) will be neither fun for the users of Debian nor for the Debian 
> > maintainers - but it's the future of Debian...
> 
> You are mixing apples and oranges. The fact that the GFDL sucks has
> nothing to do with the firmware issue. With the current situation of
> firmwares in the kernel, it is illegal to redistribute binary images of
> the kernel. Full stop. End of story. Bye bye. Redhat and SuSE may still
> be willing to distribute such binary images, but it isn't our problem.
>...


It's a grey area.

debian-legal did pick one of the possible opinions on this matter.


The similarities between the GFDL and the firmware discussion can be 
described with the following two questions:


Is it true, that the removal of much of the documentation in Debian is 
scheduled soon because it's covered by the GFDL, that this is called an 
"editorial change", and that Debian doesn't actually care that this will 
e.g. remove all documentation about available options of the standard C 
compiler used by and shipped with Debian?

Is it true, that Debian will leave users with hardware affected by the 
firmware problem without a working installer in Debian 3.1?


The point is simply, that Debian does more and more look dogmatic at 
it's definition of "free software" without caring about the effects to 
it's users.


As a contrast, read the discussion between Christoph and Arjan in a part 
of this thread how to move firmware out of kernel drivers without 
problems for the users. This might not happen today, but it's better for 
the users.


cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux