Messages in this thread |  | | | Date | Thu, 11 Dec 1997 10:01:52 -0800 | | From | Richard Henderson <> | | Subject | Re: kerneld & binfmt_aout |
| |
On Thu, Dec 11, 1997 at 02:56:19AM -0500, Ion Badulescu wrote: > On 10 Dec 1997, Vladimir Volovich wrote: > > > I have the following problem: I compiled binfmt_aout as a module (and > > did "depmod -a"). But when I try to run an aout binary, kerneld does > > not load the binfmt_aout.o module automagically. The other modules, > > such as cdrom.o, isofs.o, ide-cd.o are loaded by kerneld very well. > > That's because somebody decided (a while ago, mind you) to request the > binary loader as binfmt-%04x instead of binfmt-%03d, which is what > modprobe expects and has as defaults. It's in 2.0.x too.
There was that gratuitous change, and also the fact that they changed what offset it gets the data from as well. Even more annoying is that it prints out data that, at least on the Alpha, is not a magic number, but varies with the executable.
The only appropriate solution I can think of relies on the kernel giving the first 32 bytes or so and modutils doing some sort of globbing.
But the issue is non-pressing and I havn't gotten around to it.
r~
|  |