On 10/11/2013 00:18, Steven Chamberlain wrote: >> - elflint doesn't know about the OS ABI "FreeBSD". >> - Is this correct in the ELF files?
Yes. >> I don't know whether >> kfreebsd is supposed to follow the user space ELF OS ABI >> or the kernel one. I'm not sure what you mean by this. ELFOSABI_FREEBSD indicates this binary has been built to run on kFreeBSD and uses its kernel ABI. If a binary is set to ELFOSABI_LINUX, then the kernel will enable Linux emulation mode, i.e. Linux syscall interface. Kernel modules are also built as ELF files, but AFAIK their e_ident is not checked for. >> - If it is the correct OS ABI then what would an elflint program >> need to know about it to make sure all its requirements are met? Nothing as far as ELF compliance is concerned. This tag is ment to be consumed by the kernel ELF loader only. >> - The other failures look like issues with the /proc interface >> on the install. Does the /proc interface follow the Linux kernel >> /proc interface that some of the tests rely on? Yes. But as there's no standard covering Linux-style /proc, it can't ever be 100% complete. FreeBSD developers provide an emulated "linprocfs" for compatibility purposes and try to keep up, but depending on what you do it might not work. Also, this is only provided on GNU/kFreeBSD. FreeBSD systems either use the native FreeBSD-style /proc or none at all. If you want to support FreeBSD as well, it's better if you use sysctls or whatever you need for what you're testing. -- Robert Millan -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/527ec90d.2010...@debian.org
