Kernels
- Inicie sesión ou rexístrese para enviar comentarios
I am a member!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hey,
Just curious about something.
Ever since Debian Squeeze, the Debian Linux kernel has been deblobbed - i.e. it contains only free software.
Given this, what's the actual difference between the Debian kernel and Linux-Libre? And why does Trisquel prefer LL to Deb?
Thanks.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iF4EAREIAAYFAlHUUZIACgkQgijxUCZnvlul0gEAqLEMapNjzYwR1zSu8oJgYbQQ
7DO80uS4ga84Nqn/gaoBAItOvbdWIFpSwtxOe/asm9txUZo8rDGz1tHRjMHWhu7S
=bIB4
-----END PGP SIGNATURE-----
I asked this question some time ago in a debian forum. Nobody knew the answer.
Shoud be minor differences; the fsf and debian have different opinions what "exactly" to call free.
On 2013-07-03 12:30, name at domain wrote:
> Hey,
>
> Just curious about something.
>
> Ever since Debian Squeeze, the Debian Linux kernel has been deblobbed -
> i.e. it contains only free software.
>
> Given this, what's the actual difference between the Debian kernel and
> Linux-Libre? And why does Trisquel prefer LL to Deb?
The Linux kernel used in Debian will let you install non-free firmware
and drivers. Linux Libre won't. The hooks / facilities aren't there.
I asked this a while ago to the maintainer of the .deb packages of Linux
Libre and that was the answer.
F.
--
Fabián Rodríguez
http://fsf.magicfab.ca
I am a member!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Thanks for the clarification.
Is that the only reason they continue to develop Linux-Libre? To restrict what software the user can install? Seems like a bit of a waste of effort to me.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iF4EAREIAAYFAlHUYSIACgkQgijxUCZnvlsVUQD+NhhqUR8hZ0GkNSYd3De+RAsR
fIfA3R7xWY6mzj2Zyu8A/3iWFIPo2duKwJwP6wTNTqL1vw9bZxLTNAXd4uUyxHG2
=pAQL
-----END PGP SIGNATURE-----
The reason is to not recommend nonfree firmware, it would be possible to
implement it without disabling it (e.g. using machine-specific firmware
file names), but no one has implemented it.
I am a member!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Not sure I understand this comment.
I totally get the desire not to recomment nonfree firmware, but I don't understand how the potential use of the Debian Linux kernel (which is deblobbed) would lead to nonfree firmware being recommended.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iF4EAREIAAYFAlHUjdwACgkQgijxUCZnvlv8AQD/SXxRRS36YYGenRXhO4hNb6IA
5hv78SyiNs3y7qtRUNkA/iKDJQzDvZE3gubCVji1iwa+rZglB23TvGnNAKAdpnOP
=UJBO
-----END PGP SIGNATURE-----
I am a member!
I, too, don't understand how running a deblobbed Wheezy kernel equates
or leads to recommendation of non-free firmware or software. Is non
free firmware black-listed, in some way, in Linux Libre? There's
nothing, but my desire to keep it free, to prevent my installing
non-free user-land apps.
There are two separate issues:
1. Linux includes nonfree firmware
2. when a driver requests a firmware and it's missing, it logs an error
message containing the firmware file name
Both Debian and Linux-libre solve the first problem removing the
firmware from kernel (there are small, unimportant differences). The
Debian project hosts a separate repo with this firmware, it's not a part
of Debian.
The difference is in the second problem: Debian keeps the references to
nonfree firmware, Linux-libre replaces them with the /*(DEBLOBBED)*/
string. It solves the issue of the distro "steer[ing] users towards
obtaining any nonfree information for practical use, or encourag[ing]
them to do so" [0]. There are other possible solutions discussed on the
Linux-libre mailing list, they aren't implemented (you can change this).
A system where the user isn't allowed to install nonfree programs isn't
free (if there are nonfree programs), this is technically similar in
Linux-libre: you can load custom modules, e.g. undeblobbed modules that
use the nonfree firmware. Making it easier wouldn't help users of
completely free systems, so it has a very low priority for the
developers.
[0] http://www.gnu.org/distros/free-system-distribution-guidelines.html
I am a member!
I think the main reason to avoid using Debian is that the project points users to non-free software. It's not that the core of the distribution isn't free software friendly (even if you were to use the FSF definition).
I believe there was clarification on the binary blob blacklisting issue and everybody concerned (except for maybe the maintainer of the linux-libre code) has concluded its not necessary or even desirable. I think there was even talk of stopping the practice within linux-libre.
Ultimately I don't think there is a whole lot stopping the FSF from certifying Debian as a free distribution should the project want to go that route.
Some things that would have to be done: discontinue the non-free repository and wiki documentation links to non-free software. A few programs may need to be modified as well to prevent them from recommending or pointing to non-free software (Iceweasel).
lloydsmart asked: Is that the only reason they continue to develop Linux-Libre?
Continue? As if they should stop merely because some distro has a kernel without binary blobs?
Please remember that Linux-libre predates Debian this area (2008 versus 2011.) I understand that Gentoo also offers the option to deblob their kernels too using the deblob scripts from Linux-libre. Who knows what might have happened in various distros if the work to make a freedom-respecting kernel hadn't happened.
Debian and Gentoo, with their various package formats, aren't the only distros on the planet. It makes sense to consolidate development on the clean kernel instead of having each distro reimplement things from scratch. The work on Linux-libre should continue so as to provide a source that distros can easily use as a drop-in replacement for the kernel that comes from kernel.org.
- Inicie sesión ou rexístrese para enviar comentarios