>> or only print info about what is missing? > > The vanilla kernel prints an error about the missing files if the > request fails. For the case of non-free blobs, linux-libre now prints > a /*DEBLOBBED*/ message, and the files are not actually requested.
Ututo now also prints a special message. > If a driver needs a non-free firmware file to work, removing it renders > the driver useless, so you can remove it. Having non working drivers > looks pointless to me, and can -maybe in a subtle way- cause harm. could you tell us about this subtle harm? > Then the maintainer of the freed version of the kernel can stop removing > that module. and the people will need to upgrade, a lot of additional work >> is there another way to detect that hardware? > > All hardware can be detected. That part doesn't matter. can is different than doing it. Why do you think that do not matter >> is not usefull to know what hardware do not have frre software to work with? > > Yes, but how is that related to the load call thing? is related to the module modules are a way to know if the hardware exists and is working. >> > -What is enough to comply with the Guidelines for Free System >> > Distributions? [3] >> >> is this free guideline fine? > > Is ok for me, but maybe it needs some clarifications (like this issue). its not weel organized, have a lot of confusing parts, etc but the principal issue is its central argument we have free software definition, a huge agreement about that, why try to impose additional conditions? why to speak about trademarks and non functional non-free works we are talking about a free distribution with non free material, why? For example debian is more restrictive on that >> is free-linux something usefull? or the removal can be done by a >> script running over a normal kernel? > > I'm not sure if I'm getting your question. :| do the world need free-linux? we have free gnu/linux system without blobs a long time before that project exists. > >> do free distros must have non-free-software-having-hardware detection >> procedures and user warnings? > > Please, explain "non-free-software-having-hardware detection procedures" capability to detect and warn user about hardware without free software -- Diego Saravia diego.sara...@gmail.com NO FUNCIONA->d...@unsa.edu.ar