KW-KERNEL-CONFIG-MANAGER(1)

πŸ“¦ version 0.10, in ubuntu stonking

✨ 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 .config file 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 -d flag 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 .config file 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 .config file, 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 .config file 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 .config file 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 πŸ”₯. --output lets you name the config file yourself, and --optimize runs make localmodconfig so 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