Date: Thu, 21 Aug 1997 09:12:46 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: grog@lemis.com (Greg Lehey) Cc: terry@lambert.org, hackers@FreeBSD.ORG Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] Message-ID: <199708211612.JAA23531@phaeton.artisoft.com> In-Reply-To: <19970821084227.64768@lemis.com> from "Greg Lehey" at Aug 21, 97 08:42:27 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > > What do you mean by "convert to ELF"? I hope you don't mean a > > > wholesale change. > > > > Why not? > > Because I don't have the time at the moment. I'm too busy finding > out why libc.so.3.0 doesn't build in -current, and thus blows my > world out of the water. But it does it by making it build. 8-) 8-). > I might change my mind. What I really don't understand is why a > wholesale changeover should be necessary: I certainly hope that the > new system will still be able to run a.out executables. Yes, of course. The main sticking point is that the boot blocks booting an ELF kernel can only boot an ELF kernel, so dancing back and forth, back and forth is a bit out of the question. Yes, the current boot hacks fit (barely; < 80 bytes remaining), but don't cover all the cases the a,out-only boot blocks do. The LKM situation is equally grim; the LKM's must be switched at the same time. This is because the LKM relocation is done by linking against the kernel symbol table. Try linking an a.out image against the kernel symbol table. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708211612.JAA23531>