Bug 1947

Summary: lilo mispointer
Product: [Retired] Red Hat Linux Reporter: yngguru
Component: liloAssignee: David Lawrence <dkl>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-04-03 03:59:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description yngguru 1999-04-02 05:52:34 UTC
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?

Comment 1 Bill Nottingham 1999-04-03 03:59:59 UTC
the installer installs lilo.conf to point to whatever kernel was
installed.

Comment 2 openshift-github-bot 2016-11-11 21:03:37 UTC
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