From: Nix <nix@esperi.org.uk>
To: Douglas J Hunley <doug@hunley.homeip.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: stupid question about netlink and 2.6.14 and latest udev
Date: Fri, 25 Nov 2005 12:54:34 +0000 [thread overview]
Message-ID: <87hda0lwfp.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <200511231529.55683.doug@hunley.homeip.net> (Douglas J. Hunley's message of "23 Nov 2005 20:36:16 -0000")
On 23 Nov 2005, Douglas J. Hunley said:
> Latest udev says that it requires netlink support in the kernel, however I
> can't find any concrete info on how to enable netlink in 2.6.14+ .. a grep of
> NETLINK in .config doesn't find anything. I saw an option that made reference
> to netlink, but it didn't actually state that it was enabling netlink. What's
> the magic config option? Or how does one check if a running kernel has
> netlink support functional?
If you have network support at all (i.e. CONFIG_NET=y), you have netlink
support. (This has been true for some time.)
--
`Y'know, London's nice at this time of year. If you like your cities
freezing cold and full of surly gits.' --- David Damerell
prev parent reply other threads:[~2005-11-25 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 20:29 stupid question about netlink and 2.6.14 and latest udev Douglas J Hunley
2005-11-25 12:54 ` Nix [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=87hda0lwfp.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=doug@hunley.homeip.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