Date: Sat, 17 Sep 2005 00:36:57 +0930 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: Peter Pentchev <roam@ringlet.net> Cc: Daniel Eischen <deischen@freebsd.org>, freebsd-hackers@freebsd.org, Wouter van Rooij <aentgood@gmail.com> Subject: Re: ELF binary type "0" not known. Message-ID: <200509170036.58660.doconnor@gsoft.com.au> In-Reply-To: <20050916144653.GG2813@straylight.m.ringlet.net> References: <Pine.GSO.4.43.0509161008460.17155-100000@sea.ntplx.net> <200509162357.22204.doconnor@gsoft.com.au> <20050916144653.GG2813@straylight.m.ringlet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart2861364.t62uzUTcex Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 17 September 2005 00:16, Peter Pentchev wrote: > > Wow that's weird.. > > I wonder why that happens? > > What is weird? The fact that if linux.ko is not loaded, the kernel > does not know what to do with an unknown ELF binary type? :) I misread that as having linprocfs loaded :) > What I find weird is the fact that as soon as linux.ko is loaded, > the kernel "learns" to treat type 0 binaries as type 3; but this is > probably because Daniel Eischen has at some earlier time set > the kern.fallback_elf_brand sysctl to 3. Yes that is pretty odd.. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart2861364.t62uzUTcex Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBDKt+S5ZPcIHs/zowRAnrDAJ43GxzTaSOHoOw4AOU7IM7TH1T8wQCeJqid OT9t8U8EgIG/xtb2PfCG4dg= =ejF/ -----END PGP SIGNATURE----- --nextPart2861364.t62uzUTcex--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200509170036.58660.doconnor>