I'm certain if we made a Venn diagram, there would be an overlap. But
FatELF solves different problems than package managers, and in the case of
ia32 compatibility packages, it helps the package manager solve its
Not really - as I said it drives disk usage up, it drives network
bandwidth up (which is a big issue for a distro vendor) and the package
manager and file system exist to avoid this kind of mess being needed.
You can ask the same question as FatELF the other way around and it--
becomes even more obvious that it's a bad idea.
Imagine you did it by name not by architecture. So you had a single
"FatDirectory" file for /bin, /sbin and /usr/bin. It means you don't have
to worry about people having different sets of binaries, it means they
are always compatible. And like FatELF it's not a very good idea.
Welcome to the invention of the directory.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/