Bug 4061 - network interfaces, including lo, assumed to be modules
network interfaces, including lo, assumed to be modules
Status: CLOSED NEXTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-07-15 20:53 EDT by tompermutt
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-07-15 22:08:32 EDT
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 tompermutt 1999-07-15 20:53:07 EDT
The startup scripts insist on trying to load a module (50
times) for each atboot network interface.  This includes the
loopback interface, which doesn't even seem to be allowed to
be a module, as well as interfaces which may be compiled
statically into the kernel.  It fails slowly but gracefully.
Comment 1 Bill Nottingham 1999-07-15 22:08:59 EDT
You compiled your own kernel without IP aliasing, correct?
Comment out the section of /etc/sysconfig/network-scripts/ifup-aliases
that pertains to linuxconf; its IP-alias support is, interesting.
This is already done in the latest initscripts in Raw Hide.

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