|
Home > Archive > Unix Programming > January 2005 > Where's the modctl(2) system call in Solaris 8?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Where's the modctl(2) system call in Solaris 8?
|
|
| Sunny Suen 2005-01-23, 7:47 am |
| Greetings,
A truss of the modload(1M) command in S8 reveals the following line:
modctl(MODLOAD, 0x00000000, 0x080470A4, 0x080470A0, 0x08047594) = 0
Looks like modctl() is a valid but undocumented system call as
/usr/include/sys/syscall.h contains this macro:
#define SYS_modctl 152
Couldn't locate its definition from /usr/include/sys/modctl.h.
Anbody knows about its prototype/signature details or the relevant
header file?
Many thanks
| |
| Gavin Maltby 2005-01-24, 7:47 am |
| Sunny Suen wrote:
> Greetings,
> A truss of the modload(1M) command in S8 reveals the following line:
> modctl(MODLOAD, 0x00000000, 0x080470A4, 0x080470A0, 0x08047594) = 0
>
> Looks like modctl() is a valid but undocumented system call as
> /usr/include/sys/syscall.h contains this macro:
> #define SYS_modctl 152
Yes, it is a private system call. Don't be tempted to equate "undocumented"
with "secret" - it's only undocumented and private because it does not form
part of any public API and as such it is subject to change without notice.
> Couldn't locate its definition from /usr/include/sys/modctl.h.
> Anbody knows about its prototype/signature details or the relevant
> header file?
Don't use it, even if you do discover how to call it - you'll just break
in future release or make your customers dependent on current release
implementation details.
Cheers
Gavin
|
|
|
|
|