KW-KERNEL-CONFIG-MANAGER(1)
β¨ NAME β¨
kw-kernel-config-manager β your kernel config file manager, bestie π
(the page header says it's from the kw-kernel-config...nfig file manager manual, in case you were wondering π)
β¨ SYNOPSIS β¨
kw (k | kernel-config-manager) [(-s | --save) <name> [(-d | --description) <description>] [-f | --force]]
kw (k | kernel-config-manager) [-l | --list]
kw (k | kernel-config-manager) [--fetch [(-o | --output) <filename>] [-f | --force] [--optimize] [--remote [<remote>:<port>]]]:
kw (k | kernel-config-manager) [--get <name> [-f | --force]]
kw (k | kernel-config-manager) [(-r | --remove) <name> [-f | --force]]
kw (k | kernel-config-manager) [--verbose]]
πΈ DESCRIPTION πΈ
okay so kernel-config-manager is the command that keeps track of all the different versions of your project's .config file π. It gives you the save, load, remove, and list operations for those files β that's the whole kit and caboodle π«Ά.
and the lil plot twist? if you don't pass any parameter at all, kernel-config-manager will just list all the configs under kw's management for you. no arguments, no problem, it's giving helpful fr fr β¨
Note (pay attention bestie π«Ά): this feature has interoperability with the kw env feature. slay.
π OPTIONS π
--save <name> [-d <description>] [-f | --force]β this one takes a snapshot of the.configfile sitting in your current folder and tucks it into kw's management system under whatever<name>you gave it πΈ. wanna add a lil note about what this config even is? hit the-dflag with your description π¬. and here's the tea: if you try to add another config using a name that's already being managed, kw will throw a warning at you β<pink>-f</pink>shuts that warning up π .-l,--listβ lists every.configfile version you've got available π. this is also the default behavior when you specify no option at all, so honestly it's the main character of this whole page π.--get <name> [-f | --force]β grabs a copy of the config file with the<name>you provided and drops it right in your current directory π. heads up though: this operation overwrites your current.configfile, so kw shows you a warning first π.<pink>-f</pink>suppresses that warning and carries on with any destructive operations β so use it with intention, bestie, no cap π.-r <name> [-f | --force],--remove <name> [-f | --force]β removes the config labeled<name>from kw's management system ποΈ. since this operation removes a.configfile from kw management, a warning gets shown first.<pink>-f</pink>suppresses the warning and carries on any destructive operations β periodt.--fetch [(-o | --output) <filename>] [-f | --force] [--optimize] [--remote [<remote>:<port>]]β fetches a.configfile from a target machine straight into your current directory π°οΈ. if there's already another config hanging out in that directory, kw asks you whether you wanna replace it or not.<pink>-f</pink>suppresses that warning and carries on with any destructive operations π₯.--outputlets you name the config file yourself, and--optimizerunsmake localmodconfigso you get a config that's optimized for the target machine β¨. (--remote [<remote>:<port>]is right there in the synopsis for pointing at your target π.)--verboseβ verbose mode makes the kw program spill out debug messages so you can track its progress π. this is highkey iconic during debugging, since it makes spotting possible errors way easier π.
π¦ EXAMPLES π¦
for all of these, we're assuming the relevant fields in your configuration files (which live in .kw/ by default πΈ) have already been set up. and we highly recommend using kw config for managing your local and global configurations π«Ά.
so, say you want kw to save your current .config file β run this:
cd <kernel-path>
kw k --save my_current_config
you can peep the config files kw is maintaining with:
kw k --list
and if you wanna fetch a config from a remote machine (in this case one available at localhost:2222) as root, go ahead and run:
kw kernel-config-manager --fetch --remote root@localhost:2222
okay that's literally the whole page, bestie π go forth and manage those kernels. π β¨
<span>that's a wrap on the kw-kernel-config...nfig file manager manual β the footer is just that same title again, no version, no date, which is giving mystery π but we move. π</span>
π¦ where this page comes from
- ubuntu stonking: kworkflow 1:0.10-3 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms