Hirayama, Pat wrote:
Greetings,
I had a couple of questions I'm wrestling with right now.
1. create_package_descr -- So, if I have an installation repository setup, and then I add/update some packages, if I run create_package_descr, that should allow the new/updated packages to appear in YaST Software Installation?
Thats right, create_package_descr creates a new database to be used when installing a system. Only then customized packages can be installed.
2. When I use AutoYaST with a control file, as the system gets to the point that it will read the control file, it goes through and looks at hardware, and loads what modules it needs to. So, I was wondering if it was possible to PREVENT a specific module from loading? I have found that when I have a Dell with a PERC3/DC RAID controller, SuSE installer wants to load both a QLogic driver, and a Megaraid driver, which is a problem, since they are the same card. My workaround at the moment is to run a manual setup, answering yes/no to whichever modules to load. This defeats the purpose of having a hands-off autoinstallation routine. Any thoughts?
What about loading the right module before yast2 even starts with insmod=<module name> as a kernel parameter, would this help? Anas
Thank you!
-p
Pat Hirayama IT / Server Operations Fred Hutchinson Cancer Research Center phirayam@fhcrc.org