public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ookhoi <ookhoi@ookhoi.xs4all.nl>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Thomas Svedberg <thsv@bigfoot.com>,
	linux-kernel@vger.kernel.org, rgooch@atnf.csiro.au
Subject: Re: Network device problems
Date: Thu, 25 Oct 2001 15:31:03 +0200	[thread overview]
Message-ID: <20011025153103.T24475@humilis> (raw)
In-Reply-To: <1004013479.2597.50.camel@athlon1.hemma.se> <3BD80A32.16D618FD@mandrakesoft.com>
In-Reply-To: <3BD80A32.16D618FD@mandrakesoft.com>

Hi Jeff,

> Thomas Svedberg wrote:
> > 
> > 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".
> > 
> > Tried kernels 2.4.12-ac2 and -ac6 (One of my -ac2 kernels worked fine
> > before the upgrade).
> > 
> > Using the RedHat precompiled kernels it works (but then I have no lVM)
> > 
> > Anyone have any clues ?
> 
> Yep.  Newer initscripts from RedHat and Mandrake (and others?) require
> CONFIG_NETLINK_DEV.  initscripts runs, IIRC, iproute, which in turn
> requires the netlink device.
> 
> I have a feeling this is going to be a FAQ.  Pretty much anybody who
> uses these initscripts and compiles their own kernel !CONFIG_NETLINK_DEV
> will hit this.

But what about:

CONFIG_NETLINK_DEV
  This option will be removed soon. Any programs that want to use
  character special nodes like /dev/tap0 or /dev/route (all with major
  number 36) need this option, and need to be rewritten soon to use
  the real netlink socket.
  This is a backward compatibility option, choose Y for now.

IIRC it says "will be removed soon" and "This is a backward
compatibility option" for a long time now (since 2.3?, didn' check). It
is not strange for people not to enable it imho. 

	Ookhoi

  reply	other threads:[~2001-10-25 13:30 UTC|newest]

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

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=20011025153103.T24475@humilis \
    --to=ookhoi@ookhoi.xs4all.nl \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@atnf.csiro.au \
    --cc=thsv@bigfoot.com \
    /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