linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] use uevents in udevd
Date: Fri, 14 Jan 2005 13:08:57 +0000	[thread overview]
Message-ID: <1105708137.17412.44.camel@localhost.localdomain> (raw)
In-Reply-To: <41E79D7A.2060607@suse.de>

On Fri, 2005-01-14 at 14:01 +0100, Hannes Reinecke wrote:
> Kay Sievers wrote:
> > On Fri, 2005-01-14 at 11:55 +0100, Hannes Reinecke wrote:
> > 
> >>Marco d'Itri wrote:
> >>
> >>>On Jan 14, Hannes Reinecke <hare@suse.de> wrote:
> >>>
> >>>
> >>>
> >>>>Comments welcome.
> >>>
> >>>Nice work.
> >>>How can the init scripts determine if support for uevents is available?
> >>>
> >>
> >>Good question. Asked myself the same one just now.
> >>I couldn't figure out whether this information is exported from the 
> >>kernel directly, so that leaves two possibilities:
> >>
> >>- check /proc/config.gz for CONFIG_KOBJECT_UEVENT
> >>   (if /proc/config.gz is available)
> >>- use a program to check for it (like the attached one).
> > 
> > 
> > Did you try the program on a kernel without uevents. I think you can
> > bind successful to all the 32 netlink sockets even without a "sender".
> > 
> 
> Great. You are correct.
> 
> What now?
> 
> Scanning /proc/config.gz is ugly.

We don't need to know that in advance it if we turn the other source of
events off if we get the first add/remove event from netlink. But yes,
we should think about exporting it somewhere.

Kay




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
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

  parent reply	other threads:[~2005-01-14 13:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-14 10:22 [PATCH] use uevents in udevd Hannes Reinecke
2005-01-14 10:40 ` Marco d'Itri
2005-01-14 10:55 ` Hannes Reinecke
2005-01-14 10:55 ` Kay Sievers
2005-01-14 11:00 ` Marco d'Itri
2005-01-14 11:22 ` Hannes Reinecke
2005-01-14 11:26 ` Hannes Reinecke
2005-01-14 11:37 ` Marco d'Itri
2005-01-14 12:11 ` Kay Sievers
2005-01-14 12:43 ` Kay Sievers
2005-01-14 13:01 ` Arnd Bergmann
2005-01-14 13:01 ` Hannes Reinecke
2005-01-14 13:08 ` Kay Sievers [this message]
2005-01-14 13:11 ` Arnd Bergmann
2005-01-14 13:12 ` Kay Sievers
2005-01-14 13:23 ` Hannes Reinecke
2005-01-14 13:35 ` Kay Sievers
2005-01-14 16:08 ` Hannes Reinecke
2005-01-16 16:27 ` Kay Sievers

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=1105708137.17412.44.camel@localhost.localdomain \
    --to=kay.sievers@vrfy.org \
    --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).