Bug 1947 - lilo mispointer
lilo mispointer
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: lilo (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-04-02 00:52 EST by yngguru
Modified: 2016-11-11 16:03 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-04-02 22:59:16 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description yngguru 1999-04-02 00:52:34 EST
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-02 22:59:59 EST
the installer installs lilo.conf to point to whatever kernel was
installed.
Comment 2 openshift-github-bot 2016-11-11 16:03:37 EST
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@redhat.com>

Continuation of PR#30000

Note You need to log in before you can comment on or make changes to this bug.