KW-ENV(1)

✨ kw-env — kw environment manager ✨

okay bestie, gather round 💖 this is the manual page for kw-env, aka the kw environment manager — the little corner of kw that lets you keep a million different kernel setups from crashing into each other. no cap, it's iconic.

---

🌸 SYNOPSIS 🌸

kw (env) [(-c | --create) <NAME>]
kw (env) [(-u | --use) <NAME>]
kw (env) [(-d | --destroy <NAME>)]
kw (env) [(-l | --list)]
kw (env) [(-e | --exit-env)]
kw (env) [--verbose]

---

🦋 DESCRIPTION 🦋

so here's the vibe. when you're doing Linux kernel stuff, sometimes you wanna run different tests to fix specific issues, right? classic example: you're out here working with a 64-bit architecture but you gotta double-check that the 32-bit compilation still works. that whole mission requires changing the config file and a bunch of other parts. 😭 another case: you're using the same kernel for a test machine with configuration X, but you ALSO need to check another device with configuration Y. it's giving chaos.

kw env makes your life easier by isolating multiple contexts in your environment. main character energy, honestly. 💅

when you create a new env, kw will isolate:

1. All kw configs per env. which means: you can have one dedicated configuration per env — yes queen, a whole config just for you 💖;
2. Associate the kernel config file with the new env. in other words, in the same kernel you can have different kernel config files per env;
3. Isolate compiled file per env. 🎀

Note: ⚠️ kw does not support the concept of a global env. you must have one env per kernel repository. periodt.

---

💅 OPTIONS 💅

• -c, --create <ENV_NAME> — the create parameter expects a string to be used as the env name. when kw creates a new env, it instantiates the current kw configurations into the new env. cute, right? ✨
• -u, --use <ENV_NAME> — switches you from one env to another one you already created. glow-up, but for contexts. 🦋
• -d, --destroy <ENV_NAME> — the destroy parameter expects a string with the name of the env you want to destroy. bye bestie 👋💀
• -l, --list — shows you all the envs created via the --create option. a little roster of your children, if you will. 📋
• -e, --exit-env — lets you "exit" the env feature. if you're using a specific env and you don't wanna use it anymore, --exit-env will remove all symbolic links and copy the current env's configuration files to the .kw. it's giving moving-out day 🧳
• --verbose — verbose mode is an option that makes the kw program display debug messages so you can track its progress. this one is highkey useful during the debugging process, because it lets you identify possible errors more easily. 🙈

---

🌈 EXAMPLES 🌈

if you wanna create a new env, you can use:

cd <kernel-path>
kw env --create MY_NEW_ENV
kw env --create 32-BIT-COMPILATION

if you wanna create a new env, you can use:

kw env --use 32-BIT-COMPILATION

if you wanna destroy an environment:

kw env --destroy MY_NEW_ENV
kw env --destroy 32-BIT-COMPILATION

if you wanna list the available envs:

kw env --list

if you wanna exit the env feature:

kw env --exit-env

---

and that's the whole page, bestie 🫶 kw-env — kw environment manager — go forth and isolate your contexts like the icon you are. 💜🌸⭐