2.6.29-libre, and 2.6.28-libre2

Alexandre Oliva lxoliva at fsfla.org
Wed Apr 1 16:51:07 UTC 2009

On Apr  1, 2009, Rubén Rodríguez Pérez <ruben at es.gnu.org> wrote:

> ./deblob-check linux-2.6.28.tar.bz2

Hmm...  You say this didn't work.  How so?  Did it complete successfully
without spitting out anything whatsoever?  (that would be *very* bad,
for this file is known to contain lots of blobs)  Or did it just print
the tarball name and quit?  (that would be the expected behavior,
without any additional flags)

> ./deblob-check -i linux-2.6.28 linux-2.6.28.tar.bz2

The -i is redundant in this case.  The thing is, to figure out which
patterns/false positives to use, it matches patterns on the input
filename.  Both *linux*.tar* and *linux-*.*.* are recognized as Linux
tarballs, and bring in all the patterns for false positives and known
blobs in Linux.

What -i does is to arrange for its argument to be considered part of the
input filename, for purposes of matching patterns.  In this case, it is
just redundant.  But it helps if you are, say, within an exploded linux
tarball, and you want to process say include/firwmare.h using all the
patterns used for Linux: adding '-i linux-x.y.z' to the command line
does that.

> ¿El script necesita de tener instalado algún comando especial?

No, no special commands are needed.  If deblob-check can find and remove
blobs for you (and it does, otherwise deblob-<kver> would have failed),
it ought to be able to report the blobs as well.

Alexandre Oliva, freedom fighter    http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/   FSF Latin America board member
Free Software Evangelist      Red Hat Brazil Compiler Engineer

More information about the linux-libre mailing list