Le 12/07/2014 00:42, Paul Goyette a écrit :
I run without _any_ EXEC_* or COMPAT_* module compiled into my kernel. ALL of
my EXEC_* and COMPAT_* modules are auto-loaded as needed from the file system.
Please don't break this! :)
Well, netbsd32 already breaks the module loader, because of a
Le 05/07/2014 16:58, Maxime Villard a écrit :
[...]
My approach was wrong. #if(ARCH_ELFSIZE != 64) doesn't remove the exec_elf32
module, since it is still listed in distrib/sets/lists/modules/md.amd64. It
just removes exec_elf32_modcmd() from the module.
If the module is built in (GENERIC
I run without _any_ EXEC_* or COMPAT_* module compiled into my kernel.
ALL of my EXEC_* and COMPAT_* modules are auto-loaded as needed from the
file system.
Please don't break this! :)
My currently auto-loaded modules as reported by modstat(8) include
exec_script
exec_elf32
Le 03/07/2014 21:40, David Holland a écrit :
On Thu, Jul 03, 2014 at 03:26:09PM +0200, Maxime Villard wrote:
Being able to automatically invoke a suitable emulator for user
binaries of the wrong OS and/or architecture would be very helpful for
crossbuilding difficult packages.
Hi,
I would like to improve the priorities of the binary loader. When the kernel
loads a binary, it basically loops and calls different loaders (for aout, ELF,
...). There are several ELF loaders, for native and emulated binaries. This
loop has a particular order: the 32bit compat loaders are
On Tue, Jul 1, 2014 at 9:03 AM, Maxime Villard m...@m00nbsd.net wrote:
Hi,
I would like to improve the priorities of the binary loader. When the kernel
loads a binary, it basically loops and calls different loaders (for aout, ELF,
...). There are several ELF loaders, for native and emulated
On Tue, Jul 01, 2014 at 07:38:33PM +0100, Justin Cormack wrote:
FreeBSD recently (
http://svnweb.freebsd.org/base?view=revisionrevision=264269 ) added
elf header signature parsing to decide how to execute binaries (based
on the Linux binfmt_misc). The main use case is for qemu emulation,
