Red Hat Bugzilla – Bug 8148
Various issues with initscripts (incl updated version)
Last modified: 2014-03-16 22:11:55 EDT
intscripts turns off named as a default.
(verified with chkconfig on all machines)
initscripts adds usepeerdns to ifup-ppp. These two things generally
contrive to mess up internal DNS (non-Internet IP DNS).
I also have a question. I have 4 Linux boxs,aside from the the above
3 work just fine. On my firewall server I am forced to manually
insmod 8309,3c503,and the PPP modules or stuff wont work.
This is an upgrade from 6.0 -> 6.1
Not starting bind was a change in policy (increased default security, among
Use 'chkconfig --level 35 named on' to turn it on, or use ntsysv.
To turn off peer dns on PPP, add 'PEERDNS=no' to
Not sure about the rest of it, but to sort out the 8309 and 3c503 modules, you
need to put some entries in /etc/conf.modules to map them as required.
On my system, I have three network cards, and NE2000-ISA, and NE2000-PCI and a
DEC Tulip card, and I have the following entries to deal with them:
Q> alias eth0 ne
Q> options eth0 io=0x340 irq=9
Q> alias eth1 ne2k-pci
Q> alias eth2 tulip
The first two lines deal with the NE2000-ISA card, assigning it to eth0, the
third line assigns the NE2000-PCI card as eth1 and the last line assigns the DEC
Tulip card as eth2.
You will need to do something similar on your system.
I know that you are sincere in your comments but all these things are already
set up in conf.modules after all this is my firewall server that connects to
the outside world and since I want to shorten the modeprobe for base addresses
I have had the following in conf.modules for years.
alias eth0 3c503
options 3c503 0x280
The 8390 device is taken care of under module-info under /boot.
You outlined the fixes I already worked out. Dont you think this is a
problem for people with real DNS servers to find them suddenly turned off?
I run 8.2.2-P5 with good security scripts.
Or to add a feature under PPP that not everyone wants that again affects
Also this ticket was closed, but what about the second half of my questions?
I have never gotten a adequate answer that explains to me why this one
machine locks up on the modprobe and I have to manually ismod the modules.
I would presume the `options` line actually reads...
options 3c503 io=0x280
...but I will add that I have had problems in the past caused by the use of the
card type in the options line rather than the ethX port name. In theory it
should make no difference, but you may wish to check whether changing that to...
options eth0 io=0x280
...makes any difference.
Annoyingly that option change worked. But I remember that the original
setting I had came from the earlier documentation on the 3c503. I guess my
only question then remains why did it work with insmod and not in the
networking script? Ah well the mysteries of life and Linux.
Thanks a bunch, guess I aint too old to learn something new. Back to my