Messages in this thread |  | | Date | Mon, 13 Jan 1997 14:54:11 +0100 (MET) | From | Marcin Dalecki <> | Subject | Re: your mail |
| |
On Mon, 13 Jan 1997, Systemkennung Linux wrote:
> > > > PS. Is there any simple way to put some magic number in front of an > > > > object file containing a module ? > > > > > > Ein Module ist ganz einfach ein ELF object file und hat dementsprechend > > > in den ersten vier Bytes eine ELF Magic Nummer. > > > > > > Ralf > > > > > What I was asking for was: How to tag an objectfile AS A MODULE! How to > > find if a file is ELF is trivial... > > Ah... That's a small but significant difference. How about adding an > extra section .linux-module to modules? If more module specific information They are allready enought special secionts in the new implementation. Which You could check for, but the text strings are not comming in front of the file! Therefore they wouldn't help me. What I'm thinking about is the following:
1. Getting a way to recoginze object files used as modules in the first few bytes of them.
2. Write an binfmt loader for them similliar to binfmt_java.c or binfmt_shell.c using the modprobe programm as binfmt interpreter.
3. Change the kerneld messaging routines to call them as programms sing modprobe as the loader similiar to ld.so or the shell, in a similiar way like init or kswapd is called.
This way the autoloading of modules could be implemented cleanly and more importantly in an secure way! (Any hints ?)
4. FORGET about the kerneld and crude things like the backdoors between kernel and user space coming with it :-). Throw it away and never look back!
5. make the IPC code in the ipc/ dir do again what's supposed to do: IPC and any other ugly hacks :-).
> needs to be stored in a module that information could also be stored in that > section. > > Ralf >
Marcin
|  |