11.23 kernel changes and process

[Tim Nelson]

Here is an 11.23 difference that I would like to make sure I understand completely. I have read the docs and here is what I have concluded, in a simplified form. Please correct me if my explaination are wrong or incomplete. I will leave out SAM or kcweb as I like command line.


kctune is used modify the parameters
By default kctune will immediatly implement the change for any dynamic parameter unless explicitly told to hold.

kconfig lists all configurated kernels sets, the current kernel set and any changes held for next reboot.

Here is where I am unclear. If an actual rebuild of the kernel is required, kconfig does this as part of the reboot ? No futher commands or actions are required ?

Any comments ? Corrections ? Further explanations ?

Thanks All !!

[Steven E. Protter]

yes on kctune.

Yes, but you have the option of saving the change for later.

My understanding is that the process of putting a kernel into production which has changes to static parameters is similar to 11.11.

I've just finished a punch of changes on an 11.23 system. Almost all of them were dynamic.

I cheated and used sam to put the kernel into production though for the static parameters.

SEP

[Tim Nelson]

Thanks Steven,

I did make some changes to some static settings with kctune, then simply rebooted.

The changes are now in effect ( like magic ).

Another 2 notes worth mentioning.
-Auto kernel backup. Answer yes to backup when making changes, then old kernel can be booted from /stand/backup/vmunix ( no copying of /stand/vmunix required.
-kernel naming. put a name on the kernel, i.e. batch, online, etc.. Then load any of them at will, if reboot is required the new "named" kernel will take effect next reboot.

[Reshma Malusare]

Hi Tim,
Kconfig is for complete kernel configurations.
1.The set of data that controls the behavior and content of the HP-UX kernel is called a kernel configuration.
2. A kernel configuration consists of module usage choices made using kcmodule(1M) and tunable values chosen using kctune(1M).
3. By default, these commands affect the state of the currently running system. When these commands are given a -c config option, they instead affect the saved kernel configuration named config.
4. The currently running kernel configuration can be saved using kconfig -s.
5. A saved configuration can be loaded using kconfig -l.
6.A saved configuration can be marked for use when the system is next booted, by using kconfig -n

[Tim Nelson]

Thanks Reshma,
I did leave out the DLKM info ( only because I have yet to have a need for them ).