From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: get user socket message - some example
Date: Tue, 11 Apr 2006 17:31:33 +0000 [thread overview]
Message-ID: <20060411173133.GA32732@vrfy.org> (raw)
In-Reply-To: <dac45060604110858s757c9c11u54bf702215371fcd@mail.gmail.com>
On Tue, Apr 11, 2006 at 06:58:51PM +0300, Mark Ryden wrote:
> Hello,
> I had looked at the code of uded.c
> I udnerstand that when get kernel messages we call
> get_netlink_msg().
> This messages are sent when events like adding/removing a device or
> repartitioning of a disk occur. The kernel is responsoble to send them.
>
> As I understand, there when we get user socket message qw call get_udevd_msg().
>
> My question are: I understand that these events are generated
> from user space. Can you give example for generating such a user space event
> which will call get_udevd_msg() ?
udevcontrol sends messages over this socket. Real event messages have
been sent over this socket in the past from udevsend executed
by /sbin/hotplug, but that codepath is dead and no longer used.
Kay
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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
next prev parent reply other threads:[~2006-04-11 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 15:58 get user socket message - some example Mark Ryden
2006-04-11 17:31 ` Kay Sievers [this message]
2006-04-12 6:18 ` Mark Ryden
2006-04-12 8:40 ` 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=20060411173133.GA32732@vrfy.org \
--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).