From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Fri, 14 Jan 2005 13:08:57 +0000 Subject: Re: [PATCH] use uevents in udevd Message-Id: <1105708137.17412.44.camel@localhost.localdomain> List-Id: References: <41E79D7A.2060607@suse.de> In-Reply-To: <41E79D7A.2060607@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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 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