Ed, Although we have strict policy telling the field guys to remove shared storage connectivity, we have written procedures and I am using the --ignoredisk parameter in the kickstart config for disks, we had someone the other day forget to remove shared storage connectivity, and of course wipe out LUNs. I have been tempted to tweak the stage 2 setup, and remove the drivers completely, but I really hate to get that fare into the weeds.
Your solution using the pre% script to remove drivers from memory makes the most since to me, the question is, how do you determine which drivers to unload? You just shot-gun it, and unload all the applicable drivers? or is their a rmmod ql* trick possible? will remove module take a directed wildcard? Guess I could make a smaill script to parse the result of lsmod?
The only problem I see, is that if boot-from-SAN is being used? You never can avoid the potential problem.
