<br><br><div class="gmail_quote">El 10 de agosto de 2010 09:19, Marcos Germán Guglielmetti <span dir="ltr"><<a href="mailto:marcos@ovejafm.com">marcos@ovejafm.com</a>></span> escribió:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<a href="http://www.fsfla.org/svnwiki/anuncio/2010-03-Linux-2.6.33-libre" target="_blank">http://www.fsfla.org/svnwiki/anuncio/2010-03-Linux-2.6.33-libre</a><br>
<br>
"Request for comments<br>
<br>
A number of our users have expressed legitimate dissatisfaction with a<br>
consequence of the method we've used to stop the kernel from inducing users<br>
to install non-Free firmware. It is not our goal to prevent users from<br>
loading or running non-Free firmware, but the only way we thought of to avoid<br>
inducing users to run non-Free firmware had the side effect of making it<br>
impossible to use the non-Free firmware just by installing it.<br>
<br>
In Linux, several drivers call request_firmware with a blob name. This request<br>
is logged, including the blob name, and passed on to a userland program,<br>
supposed to locate a firmware file with that name and upload it to the<br>
kernel. Given the logs, in addition to existing and potential behavior of the<br>
userland program, this amounted to Linux telling its user to install a<br>
specific non-Free program, which is unacceptable.<br>
<br>
Linux-libre releases since generation 2 replace the blob name with a name that<br>
the firmware loader is unlikely to match, and that could be recognized in<br>
userland to inform users about the lack of Free firmware for some hardware<br>
component of the system. We also reject whatever response the firmware loader<br>
produces for such requests, to minimize the risk of accidental matches and<br>
hardware damage.<br>
<br>
We reasoned that anyone determined to use the firmware could still build a<br>
module, or a complete kernel, that issues the request and uses the response.<br>
This possibility was considered too cumbersome by some.<br>
<br>
Recently we came up with another way to achieve the goal of stopping the<br>
kernel from inviting users into the trap of non-Free Software: where Linux<br>
requests a firmware file that we know is non-Free, we could anonymize the<br>
blob name with a unidirectional hash of its name and a kernel build and/or<br>
session identifier, and issue a request for a file named after the computed<br>
hash.<br>
<br>
Given a suitable implementation of the userland firmware loader, whatever<br>
pieces of firmware the user chose to install would still be readily located<br>
and made available to the kernel. However, because of the unidirectional<br>
nature of the hash, a request for firmware that's not installed won't steer<br>
users toward that firmware, because the hash code won't immediately identify<br>
it. Thus, if the user insists on installing this firmware, Linux-libre will<br>
work with it, but it is very unlikely anyone will install the firmware<br>
because of Linux-libre.<br>
<br>
Join us at <a href="mailto:linux-libre@fsfla.org">linux-libre@fsfla.org</a> and let us know your suggestions, other ways<br>
to address this issue, or your opinion about this plan and whether it might<br>
be accepted upstream. Feedback and help are welcome!<br>
<br>
In the mean time, Be Free! with Linux-2.6.33-libre, and help us reverse the<br>
growing dependency of Linux on non-Free firmware."<br>
<br>
<br>
Creo entender que funcionará cualquier firmware con los nuevos kernels 2.6.33,<br>
aún si fuera privativo. Esto es bueno porque el usuario ya no está prohibido<br>
de instalar lo que quiera en su sistema operativo y utilizar su hardware,<br>
además es bueno pq si se desarrollan firmwares libres ya esos kernels podrán<br>
cargarlos, y es bueno porque puede fomentar el desarrollo de esos reemplazos<br>
por software libre<br>
<br></blockquote><div><br><br>es interesante porque esa discusion sostuvimos desde ututo contra esa politica de prohibirle a los usuarios usar lo que quieran<br><br>parece que los muchachos entraron en razon<br><br> <br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
________________________________________________<br>
<br>
<br>
Solar-General es una lista abierta a toda la comunidad, sin ninguna moderación, por lo que se apela a la tolerancia y al respeto mutuo.<br>
Las opiniones expresadas son responsabilidad exclusiva de sus respectivos/as autores/as. La Asociación Solar no se hace responsable por los mensajes vertidos, ni representan necesariamente el punto de vista de la Asociación Solar.<br>
<br>
<a href="mailto:Solar-general@lists.ourproject.org">Solar-general@lists.ourproject.org</a><br>
<a href="https://lists.ourproject.org/cgi-bin/mailman/listinfo/solar-general" target="_blank">https://lists.ourproject.org/cgi-bin/mailman/listinfo/solar-general</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Diego Saravia<br><a href="mailto:Diego.Saravia@gmail.com">Diego.Saravia@gmail.com</a><br>NO FUNCIONA-><a href="mailto:dsa@unsa.edu.ar">dsa@unsa.edu.ar</a><br>