SEMODULE_LINK(8)

🎀 SEMODULE_LINK — the manual page, but make it make sense 🎀

okay bestie, pull up a chair, we're doing semodule_link from the System Manager's Manual and it's actually kind of a niche little icon 💅

✨ NAME ✨

semodule_link — link SELinux policy module packages together 🦋

✨ SYNOPSIS ✨

semodule_link [-hVv] [-o outfile] basemodpkg modpkg1 [modpkg2]...

✨ DESCRIPTION ✨

so like, semodule_link is a developer tool, okay? not a casual everyday thing. it manually links a whole set of SELinux policy module packages into one single policy module package. that's the whole job. that's the vibe. 🫶

and no, you do not need this for normal SELinux operation, fr fr. in normal operation, that linking happens internally — by libsemanage, in response to semodule commands. so the machinery is doing it behind the scenes while you're living your life 😌

also, for the record: module packages themselves are created by semodule_package. so that's where they come from. iykyk 🌸

✨ OPTIONS ✨

• -h — show help. bestie behavior, always available 💖
• -V — show version. who am i, what am i, etc ⭐
• -v — verbose mode. it will tell you things. lots of things. 📣
• -o <output file> — the linked policy module package that this tool generates. this is where your hard work lands, and yes it's the output file, iconic 🎀

✨ SEE ALSO ✨

go read your sisters, they're all slaying in their own lanes 👑

• checkmodule(8)
• semodule_package(8)
• semodule(8)
• semodule_expand(8) — and the original page also trails a lil stray (8), after this one, so here it is, preserved with love: (8), 💀

✨ AUTHORS ✨

• this manual page was written by Dan Walsh <dwalsh@redhat.com> ✍️
• the program was written by Karl MacMillan <kmacmillan@tresys.com> 💻

and that's the whole page, bestie!! this one's from Security Enhanced Linux, dated Nov 2005 — yeah, vintage, but the drip is timeless 💜✨ no cap, go link some packages responsibly 🧚‍♀️🌈