Hi all,
I am wanting to add to my working kickstart post section grabbing the NVIDIA binary and installing it.
I can grab the file thats not the problem. I can use the --x-module-path to pass to the binary installer...
however, How do I get the correct module path, kernels are added the the yum update, and a new one comes along and wish to account for that. What is the correct way to know which path to provide to the installer.
Process is in kickstart post: yum -u update copy NVIDIA binary init 3 install the NVIDIA binary with either the current kernel module path or if yum update grabbed a new kernel then use that module path..
Also is there anyway in the post section to do do a "CTRL+ALT+F3"
Thanks,
Jerry
Jerry Geis wrote:
however, How do I get the correct module path, kernels are added the the yum update, and a new one comes along and wish to account for that. What is the correct way to know which path to provide to the installer.
I'd suggest installing a copy of the driver on a test system, build a list of files that the installer creates, then copying those files in kickstart, or package it as a custom RPM(or find an existing RPM). When a new kernel comes out, compile the driver on a test system, and push the driver out with the new kernel when you install the new kernel on your system(s). I do this for a few things such as drivers for VMWare when a new kernel comes out and updated qlogic drivers as well for my HBAs.
nate
On Fri, Feb 08, 2008 at 11:12:16AM -0500, Jerry Geis alleged:
Hi all,
I am wanting to add to my working kickstart post section grabbing the NVIDIA binary and installing it.
I can grab the file thats not the problem. I can use the --x-module-path to pass to the binary installer...
however, How do I get the correct module path, kernels are added the the yum update, and a new one comes along and wish to account for that. What is the correct way to know which path to provide to the installer.
Process is in kickstart post: yum -u update copy NVIDIA binary init 3 install the NVIDIA binary with either the current kernel module path or if yum update grabbed a new kernel then use that module path..
I wouldn't do this in %post, I'd write a script that did this at boot. That way, you don't have to worry about future kernel updates.
Also is there anyway in the post section to do do a "CTRL+ALT+F3"
chvt 3
-
Garrick Staples -
Jerry Geis -
nate