CDE-EXEC(1)

✨ NAME ✨

cde-exec — bestie, this runs a binary inside a package that was generated by cde. That's the whole job. She's a little launcher goblin and she's so good at it. 💅

This is section 1 of the manual (user commands, aka the "stuff you type at a shell" zone), so welcome to the CDE-EXEC(1) era. 🎀

🌈 DESCRIPTION 🌈

CDE: Code, Data, and Environment packaging for Linux — say it with me, that's the whole acronym, no notes. 👑

Copyright 2010-2011 Philip Guo (pg@cs.stanford.edu)

http://www.stanford.edu/~pgbovine/cde.html

Here's how you actually call her:

usage: cde-exec [command within cde-root/ to run]

So you hand her a command that lives inside cde-root/, and she runs it with all the packaged environment goodness around it. Iconic behavior, honestly. 🦋

🎀 Options 🎀

• -l — use the native dynamic linker on the machine you're on. Lowkey less portable, but highkey more robust. It's giving "trade a little portability for a lot of sturdiness." 💪
• -n — block network access by blanking out the bind/connect syscalls. No cap, no network, no problem. 🚫🌐
• -f — do NOT follow forks, so child processes just run natively. She's letting the babies go free. 🙈
• -s — streaming mode. (ooh, mysterious!) 🫧✨ genuinely, that's all the lore we get.
• -i '<file path>' — ignore the given exact file path. Like, this one specific path, not a family of them. 🎯
• -p '<file path>' — ignore the given file path prefix. So anything starting with that path gets the silent treatment. 🌸
• -v — verbose mode, for debugging. She will not stop talking and honestly? We love that for her. 🗣️💖

💜 SEE ALSO 💜

• cde(1) — go read the main character's page, this one's her little sister. 👑

okay bestie that's the whole page, you ate that 💅 This was cde-exec version 0.1, dated February 2012, from the CDE-EXEC(1) manual — periodt. 🎀🦋✨