Bug 58501 - "BOOT" configuration cuts of a network.
"BOOT" configuration cuts of a network.
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
alpha Linux
medium Severity medium
: ---
: ---
Assigned To: Beth Uptagrafft
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2002-01-18 00:30 EST by Michal Jaegermann
Modified: 2007-04-18 12:39 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-06-07 20:27:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2002-01-18 00:30:31 EST
Description of Problem:

Even with such configuration for a boot kernel:


and after inserting a required network device support "manually"
an attempt to bring a network up with 'service network start'
fails with

Cannot send dump request: Connection refused

and not even a loopback device is configured. Configuring everything
"by hand", using 'ifconfig' and 'route' which luckily are still
available, works just fine (or you are not reading this :-).
Do current Red Hat network startup scripts require a presence
of RTNETLINK?  If yes then it should be available in "BOOT" kernel
as this is the only kernel which can be possible to boot after
something else in an installation was botched (like a bad partition
table, see    ).

BTW - an attempt to bring up networking with a kernel compiled with
supplied "BOOT" configuration resulted in the following messages:

Cannot open netlink socket.
Address family not supported by protocol.
Comment 1 Michal Jaegermann 2002-01-18 00:39:50 EST
Oops. "Bad partition table" was supposed to be a reference to #58499
but I forgot to fill that in before hitting "Commit".
Comment 2 Alan Cox 2003-06-07 20:27:46 EDT
Our ip tools require netlink sockets, our boot kernel install stuff does not

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