mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Wilson" <defiler@null.net>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Network device problems
Date: Thu, 25 Oct 2001 14:39:22 -0400	[thread overview]
Message-ID: <00ee01c15d84$5e878310$839183a0@W20303512> (raw)
In-Reply-To: <1004013479.2597.50.camel@athlon1.hemma.se> <3BD80A32.16D618FD@mandrakesoft.com> <1004033467.1726.3.camel@athlon1.hemma.se>

----- Original Message ----- 
From: "Thomas Svedberg" <thsv@bigfoot.com>
To: "Jeff Garzik" <jgarzik@mandrakesoft.com>
Cc: <linux-kernel@vger.kernel.org>; <rgooch@atnf.csiro.au>
Sent: Thursday, October 25, 2001 2:11 PM
Subject: Re: Network device problems

> > > 
> > > Just updated to RedHat 7.2 and after compiling and starting my new
> > > kernel my network interfaces won't go up (not even lo), I get the
> > > following message:
> > > "ifup: Cannot send dump request: Connection refused".
> > 
> > Yep.  Newer initscripts from RedHat and Mandrake (and others?) require
> > CONFIG_NETLINK_DEV.  initscripts runs, IIRC, iproute, which in turn
> > requires the netlink device.
> > 

Here's the relevant portion of the RELEASE-NOTES document from RedHat 7.2:

"The initscripts now use /sbin/ip (from the iproute packages) for most
operations. /sbin/ip requires the netlink and netlink routing features
of the kernel to function properly; it is impossible to make use of
the kernel's full routing functionality without these features. If you
are building your own kernel, make sure that CONFIG_NETLINK and
CONFIG_RTNETLINK are enabled."

They accused us of suppressing freedom of expression.
This was a lie and we could not let them publish it.
-- Nelba Blandon, Nicaraguan Interior Ministry Director of Censorship




      reply	other threads:[~2001-10-25 18:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25 12:37 Thomas Svedberg
2001-10-25 12:48 ` Jeff Garzik
2001-10-25 13:31   ` Ookhoi
2001-10-25 18:11 ` Thomas Svedberg
2001-10-25 18:39   ` Wilson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='00ee01c15d84$5e878310$839183a0@W20303512' \
    --to=defiler@null.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®