Re: [RFC 0/3] dm: add path uevents

On Tue, 2007-08-14 at 13:05 -0700, Mike Anderson wrote:
> This patch series enables device mapper (dm) to send kobject uevents for
> dm events. Currently only two new events are sent related to path state
> changes.

Sounds fine.

> DM_ACTION=PATH_FAILED
> DM_SEQNUM=1
> DM_PATH=8:48
> DM_PATHS=1

Oh, I have a patch pending for dmsetup to export a bunch of variables in
the environment format with a single call, so we can use it udev
context.
Here is the list, just that we don't clash with names or use the same
names where appropriate:
  DM_NAME=
  DM_UUID=
  DM_STATE=
  DM_TABLE_STATE=
  DM_OPENCOUNT=
  DM_MAJOR=
  DM_MINOR=
  DM_TARGET_COUNT=
  DM_TARGET_TYPES=
  DM_LAST_EVENT_NR=

Let me know if something should be renamed.

Thanks,
Kay

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Prev by Date: [patch 1/2] i386: use asm() like the other atomic operations already do.
• Next by Date: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
• Previous by thread: [patch 0/2] use asm() for atomic_{read|set}
• Next by thread: [PATCH RFC] CPU hotplug support for preemptible RCU
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]