Date: Thu, 26 Dec 2002 09:45:02 +0100 (CET) From: Peter Much <pmc@citylink.dinoex.sub.org> To: freebsd-questions@freebsd.org, freebsd-emulation@freebsd.org Cc: david@skytrackercanada.com, andrey@hm.perm.ru, leth@primus.ca, unicorn@blackhats.org, dwcjr@inethouston.net Subject: linux_base port install -> sig 12 (brandelf/SVR4) Message-ID: <200212260845.gBQ8j2H40859@disp.oper.dinoex.org>
next in thread | raw e-mail | index | archive | help
Over last months, quite a couple of people complained that they couldn't install linux_base from ports. There is currently no clue given in replies about any reason for that failure. I am sure now that these people had activated the svr4.ko kernel module (rsp. svr4_enable="YES" in rc.conf). Some people also complained that various linux binaries did not work anymore since upgrading to 4.7. The point here is that nearly all of the linux binaries have an brandelf of "0", that is SYSV, and not "3" aka Linux. The behaviour of this looks a little fuzzy alltogether, but as long as svr4.ko is not loaded and sysctl kern.fallback_elf_brand is set to "3" (the port takes care of the latter), most things seem to work. If fallback_elf_brand is not set, then dynamic linked binaries will still work, but static ones will not work except after they get a "brandelf -t Linux". After svr4.ko is loaded, this looks a bit different: The kern.fallback_elf_brand variable has then no influence anymore. Static binaries with brandelf="0" will then run into sig-12, and those with brandelf="3" will complain about a missing ELF-Interpreter in /compat/svr4 (should this happen?). Dynamic binaries with brandelf="0" will also complain about the missing interpreter in /compat/svr4, only dynamic ones with brandelf="3" will still work. PMc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200212260845.gBQ8j2H40859>