>-Linux includes some -GPL'd- modules that load firmware files into the >devices. Most of that files are non free,
or only some? ther are also free modules wich use non-free files not included in modulo distribution > -Older linux-libre versions -still in use in several distros- and Ututo >remove the > non-free blobs embedded in .c and .h files. External non free firmware > files are also deleted. > -Newest linux-libre versions remove not only the embedded blobs, but > also the ability of the modules to request non-free firmware files.[2] request? or only print info about what is missing? > -Should GPL modules that are useless without the non-free firmware files > be removed? why? > -Should they be kept, but disabling the file load call? what if someone develops a free file replacement? is there another way to detect that hardware? is not usefull to know what hardware do not have frre software to work with? > > -What is enough to comply with the Guidelines for Free System > Distributions? [3] is this free guideline fine? > > Note that this issue was already discussed in January by Richard > Stallman, Alexandre Oliva et. al. at the linux-libre lists[4], leading > Alexandre to implement one of the discussed solutions in the linux-libre > deblobber. Other solutions are possible, so this new thread should focus > on what is _enough_ to achieve a fully free kernel. is free-linux something usefull? or the removal can be done by a script running over a normal kernel? do free distros must have non-free-software-having-hardware detection procedures and user warnings? -- Diego Saravia diego.sara...@gmail.com NO FUNCIONA->d...@unsa.edu.ar
