MODNEXT(2)

💖 MODNEXT(2) 💖

okay so this is the System Calls Manual entry for modnext, and we are about to make kernel module IDs make sense, bestie. No gatekeeping, just vibes and facts. 🦋

---

🌸 NAME 🌸

modnext — return the modid of the next kernel module. periodt. 💅

🧚 LIBRARY 🧚

Standard C Library (libc, -lc) — iconic, loaded, and ready. ✨

🎀 SYNOPSIS 🎀

#include <sys/param.h>
#include <sys/module.h>

int
modnext(int modid);

int
modfnext(int modid);

🦋 DESCRIPTION 🦋

The modnext() system call returns the modid of the next kernel module — literally the one after modid — or 0 if modid is the last module in the list. slay.

If the modid value is 0, then modnext() will return the modid of the first module. cute, right?

The modfnext() system call must always be given a valid modid.

🚨 no cap, bestie: modfnext() does not play around — it must always be given a valid modid. No fake IDs, no guessing. 💀

👑 RETURN VALUES 👑

The modnext() system call returns the modid of the next module (see “DESCRIPTION”) or 0. If an error occurs, errno is set to indicate the error. that's the whole return-value vibe. 💜

💀 ERRORS 💀

The only error set by modnext() is ENOENT, which is set when modid refers to a kernel module that does not exist (is not loaded). so if it's not loaded, it's not showing up — simple as that. 🫶

🌈 SEE ALSO 🌈

• kldfind(2)
• kldfirstmod(2)
• kldload(2)
• kldnext(2)
• kldstat(2)
• kldsym(2)
• kldunload(2)
• modfind(2)
• modstat(2)
• kld(4)
• kldstat(8)

🕰️ HISTORY 🕰️

The kld interface first appeared in FreeBSD 3.0. a classic. ⭐

---

made with 💖 from Debian, dated September 28, 2000 — that's MODNEXT(2) signing off, mwah 💅