It appears this rpm does not check for the presense of kernel 2.4, thus allowing me to install with kernel 2.2. Yet it gets rather grumpy due to the use of -u in the init script.
There is no problem with using -u with current 2.2 kernels. The only problem I saw was that BIND disables IPv6 because it detects kernel<->libc structure discrepancies.
My config... $ rpm -q kernel bind bind-utils kernel-2.2.16-22 bind-9.1.0-10 bind-utils-9.1.0-10 and from the syslog: named: named startup succeeded named[2203]: starting BIND 9.1.0 named: named: named: -u not supported on Linux kernels older than 2.3.99-pre3 when using threads named: named startup failed Workaround was hack -u out of the init script, change some permissions, and run as root. Ugh!
I said "with current 2.2 kernels" which 2.2.16 doesn't qualify as. IIRC the change is in 2.2.18 or at least 2.2.19.
I'm stuck with 2.2.16 due to the !%$! closed source module for a Promise FastTrak controller. However, I would have avoided this had the specfile included a Requires: kernel >= 2.2.18
We don't want the dependency in precisely because you can run without "-u named". You should really really update to kernel 2.2.18 or higher though, 2.2.18 fixes a local root exploit. Since there are not that many changes between 2.2.16 and 2.2.19, are you sure you can't just insmod -f their module?