chris...@astron.com (Christos Zoulas) wrote:
>In article ,
>Robert Swindells wrote:
>>
>>What is wrong with your idea of updatesockopt(2) ? Or maybe call it
>>getsockopt2() and only use it for the "get with extra argument" case.
>
>I guess getsockopt2/updatesockopt is not that bad after all. Per
OK, I'll try to pick this up and run with it.
BTW, I think a better name for the COMPAT_LIB collection would be
COMPAT_UTILS
On Mon, 5 Mar 2018, Maxime Villard wrote:
Le 05/03/2018 à 11:43, Paul Goyette a écrit :
(Unicast, but feel free to share.)
I wonder if, for now, it would make sense
Le 05/03/2018 à 11:43, Paul Goyette a écrit :
(Unicast, but feel free to share.)
I wonder if, for now, it would make sense just to add compat_mod.c to the
libcompat.o object? That would "register" the included code, and other
modules which already depend on the compat module (such as the
compat
Le 05/03/2018 à 11:02, Paul Goyette a écrit :
I've notice an anomaly on which I hope someone can shed some light...
For some time now I've noticed that periodically something triggers the
"load all the exec modules on the off chance that it will let me exec
this image" - the code is function exe
I've notice an anomaly on which I hope someone can shed some light...
For some time now I've noticed that periodically something triggers the
"load all the exec modules on the off chance that it will let me exec
this image" - the code is function exec_autoload() in kern_exec.c (and
called from ex
