Somewhere early in the 2.1.x game the network aliasing game
changed.  Net-tools (ifconfig) kept up.  Linuxconf did not.
RedHat 5.1 would hang/stall on boot because of network
aliases.  5.2 just ignores them saying the kernel doesn't
support aliases (2.1.127), which is incorrect.

This was brought to RedHat's attention in the 5.1 period by
myself.  I sought for two months for a remedy before giving
up.  A few people on the newsgroups suggested using 5.0
initscripts.  It worked for them, for some reason it
wouldn't even enable networking for me.

As an angry message I posted to the newsgroups states, I do
not believe RedHat controls the kernel, but when an issue
like this exists and it _IS_ known, it is advertising fraud
to say the distribution is kernel 2.2 ready (or late 2.1.x
ready).

I have two boxes that development kernels would better suit
but cannot put it on because they require 3 and 4 aliases
each.  Again, recap, aliasing interface changed in 2.1.x.
Linuxconf (or any other tool in RedHat) needs to be updated
to detect and deal with it.  Also, kerneld should _NOT_ be
run in anyway 2.1.1xx series or 2.2 kernel.  It is a simple
change to check for.  Below is the fix for the initscript
for kerneld.  Based on 5.1 initscripts.

case "$1" in
  start)
    if [ -f /proc/sys/kernel/modprobe ]; then
        echo "Kerneld unneeded"
        exit 0
    fi
    [ -f /var/lock/subsys/kerneld ] && exit 0

        echo -n "Starting kerneld services: "
        daemon kerneld

        echo
        touch /var/lock/subsys/kerneld
        ;;
  stop)

Trever Adams
highlander