From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: kernel config requirements
Date: Wed, 19 Jul 2006 23:15:10 +0000 [thread overview]
Message-ID: <20060719231510.GA5119@kroah.com> (raw)
In-Reply-To: <1153165845.44bbea158daae@cs1.alpha12.l-secure.net>
On Thu, Jul 20, 2006 at 01:16:13AM +0300, juuso.alasuutari@tamperelainen.org wrote:
> Quoting Greg KH <greg@kroah.com>:
>
> > On Tue, Jul 18, 2006 at 08:39:47AM +0200, Guennadi Liakhovetski wrote:
> > > On Mon, 17 Jul 2006, juuso.alasuutari@tamperelainen.org wrote:
> > >
> > > > Are there any specific kernel config option requirements for using udev?
> > The
> > > > page at kernel.org just mentions 2.6 as an overall requirement. I googled
> > a bit
> > > > and found some mentions about udev needing ramfs, but those were old
> > articles. I
> > > > couldn't even find a ramfs config option in my kernel (2.6.17).
> > >
> > > CONFIG_HOTPLUG=y
> >
> > and:
> > CONFIG_NET=y
> > CONFIG_UNIX=y
> >
> > thanks,
> >
> > greg k-h
> >
>
> What does udev need the networking option for? How about boxes without
> networking, will udev not work on them? (Or does this config option refer to a
> more basic class of networking than the one that has to do with ethernet wires
> etc.?)
Yes, it deals with one more basic than ethernet.
udev needs it for the netlink socket that it listens to from the kernel.
If you don't have that, things don't work very well...
thanks,
greg k-h
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2006-07-19 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 19:50 kernel config requirements juuso.alasuutari
2006-07-18 6:39 ` Guennadi Liakhovetski
2006-07-18 13:45 ` Greg KH
2006-07-19 22:16 ` juuso.alasuutari
2006-07-19 23:15 ` Greg KH [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=20060719231510.GA5119@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).