View Single Post
Old 08-27-2012, 09:37 AM   #5
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,828
Karma: 6314522
Join Date: Feb 2012
Device: Too many.
Just test, that is probably the quickest.
Try listing /proc/sys/fs before doing the insmod and after doing the insmod.

I don't think you have to create the directory (which is part of the module code) and I don't think you have to mount it (it did have to be mounted in the kernel 2.4.x days).

And I expect that a rmmod will make it all go away again.

You should find the "binfmt_misc" directory in the source code for the module as something like:
const char = "binfmt_misc"
Possible hidden inside a macro.

In the article linked to about luajit, I don't see any mkdir or mount commands.
But they are not clear about what parts of the system setup their distribution had automated for them. (The author might not even have known about distribution specific automation.)

Last edited by knc1; 08-27-2012 at 09:41 AM.
knc1 is offline   Reply With Quote