> So one has to create binfmt_felf ?
I dont think so, one has to modify binfmt_elf and the loader.
> Do existing implementation of "FAT binaries" share data between
> binary types?
Another question is, if there is a standard way to make FAT binaries.
I.e. do we have more than one elf-header (as the arch is coded into
the header)? The current binfmt_elf implementation simply checks the
arch-code in the (first) header and rejects it, if it is not the
current one. One has to change this to look further for other headers
with current arch supports?? This way we could throw out binfmt_em86
and handle FAT binaries/emulated binaries in the user-land loader?
Many questions...
> Would there be any use for data and code sharing?
Of course! Endian information is provided in the elf-headers, too (and
will be auto swapped by the loader/binfmt_elf??)
Richard.
-- Richard Guenther <richard.guenther@student.uni-tuebingen.de> PGP: 2E829319 - 2F 83 FC 93 E9 E4 19 E2 93 7A 32 42 45 37 23 57 WWW: http://www.anatom.uni-tuebingen.de/~richi/