Kernel Parameter nfile change & Kernel Patch Simultaneously

[Gerard Drobnicki]

I would like to up the nfile parameter through sam and not reboot yet; but instead apply a kernel patch that requires a reboot so I only reboot once. What action do I first take in sam before I swinstall the patch? Does anyone see a problem with this?

Thanks.....

[harry d brown jr]

That's tough, because without knowing what the patch does it's a little unpredictable. After the patch is installed, it only takes about 15 minutes to rebuild the kernel and reboot. You can try to do both, but no bets from me on what the outcome will be. Safer bet is do them seperately, unless you know how to modify the patch.

live free or die
harry

[Sanjay_6]

Hi Gerard,

Suggest you first up the nfile parameter, do not generate the new kernel, then do a swinstall to install the new patch, Let it generate the new kernel and reboot. Hope this will fix the two reboots in one itself.

Hope this helps.

Regds

[Roger Baptiste]

Gerard,

If you are a "brave" man, you can change the nfile first, select the build kernel later option.
Then, install patch and allow the system to reboot.

If you want to play it safe, do two reboots, like
i always do ;-) Yeah, even in the days of so-called dynamic kernel.

-raj

[Gerard Drobnicki]

OK thanks.

I will try changing nfile & not processing the new kernel. Then I'll apply the kernel patch & reboot. Hopefully both changes will go in with only one reboot.

[harry d brown jr]

Rajman,

Can we call it a "Pseudo Dynamic Kernel"?

live free or die
harry

[Krishna Prasad · Accepted solution]

You can do what you want...but you need to do it in steps.

1. first make your changes in sam
2. Go ahead and regen the kernel but select the option that does NOT reboot the machine.
It will create and move a kernel into /stand/build/vmunix_test it will also create a system.SAM file.
3. Next mv the system.SAM file to /stand/system
This will keep your nfile parm. in the system file. You can at this time move the kernel to /stand/vmunix if you wish, however this could actually cause problems for apps. that actually access the kernel i.e. glance so I would recommend not to move the kernel in at this time.
4. When you schedule the patch install install the patch. When the patch generates the kernel it will access the system file you copied from before that has your nfile change. When the system comes backup it should have the changes made by the patch and by your nfile change.

This is a method that I have used in the past to make a kernel change and a patch install and only have one rebot.

[Gerard Drobnicki]

Thanks for all the expertise. I'll use "The Single Boot Theory" next time. I went the safe coward way with 2 re-boots this time.