Greg Freemyer wrote:
I normally use in-kernel drivers, but I am pretty sure you are correct, out-of-kernel drivers have to be compiled for the specific kernel they need to work with.
I think even a suse security kernel update will trigger the same thing. I know with VMware I have to recompile every time I get a new suse kernel.
Yes, this is the case with self-compoled raid drivers as well. One of the reasons why I will not buy an raid controller that isn't supported natively by the kernel. It was a major pain to update the kernel while the areca module was not supported. If I problems all the various problems the only conclusion has to be to use a natively supported raid controller. Just the thought that a productive system will be down if some unsuspecting sysadmin installs a kernel update is already enough. Also booting from the raid is a bit tricky to configure with software raid compared to hardware raid. It all comes down to the question in what currency you want to pay: - hard currency at once for a hardware controller - over a long time with more maintenance and more care for a software raid. -- Sandy List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org