If lilo is installed, the /etc/lilo.conf file points to /boot/vmlinuz-2.2.3-5. Shouldn't it point to the symbolic link /boot/vmlinuz?
the installer installs lilo.conf to point to whatever kernel was installed.
Commit pushed to master at https://github.com/openshift/openshift-docs https://github.com/openshift/openshift-docs/commit/38e569a0e76f117d7efafa253dd9e29555934194 Document iptables interaction with Openshift iptables, firewalls, Openshift, Docker all interact with the kernel iptables. None of the packages knows about what the other packages have done or need to do. It is very easy to misconfigure iptables and break Openshift and/or docker networking. These changes document the risks and some of the interactions between packages. https://trello.com/c/k6TgLcXS/307-3-document-un-allowed-iptables-mucking-with-behavior-sdn-supportability openshift/openshift-docs: Issue #1947 Signed-off-by: Phil Cameron <pcameron> Continuation of PR#30000