Linux Device Hot Plugging

• Thread Index

• Re: Kernel 2.6.30 and udevd problem
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Alberto Gonzalez <alberto6674@xxxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: Debugging udev question
  • From: Alan Jenkins <sourcejedi.lkml@xxxxxxxxxxxxxx>
• [proposed solution] Re: ATTRS{idVendor}
  • From: Alan Jenkins <sourcejedi.lkml@xxxxxxxxxxxxxx>
• Re: ATTRS{idVendor}
  • From: Alan Jenkins <sourcejedi.lkml@xxxxxxxxxxxxxx>
• Re: ATTRS{idVendor}
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Debugging udev question
  • From: Alan Jenkins <sourcejedi.lkml@xxxxxxxxxxxxxx>
• Re: ATTRS{idVendor}
  • From: Alan Jenkins <sourcejedi.lkml@xxxxxxxxxxxxxx>
• Re: [PATCH] Add fc_id, which gives ID_PORT_NAME and ID_LUN on appropriate devices.
  • From: Andrey Borzenkov <arvidjaar@xxxxxxx>
• Debugging udev question
  • From: Christopher Piggott <cpiggott@xxxxxxxxx>
• ATTRS{idVendor}
  • From: Christopher Piggott <cpiggott@xxxxxxxxx>
• Re: [PATCH] Add fc_id, which gives ID_PORT_NAME and ID_LUN on appropriate devices.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] Add fc_id, which gives ID_PORT_NAME and ID_LUN on appropriate devices.
  • From: Peter Jones <pjones@xxxxxxxxxx>
• Re: [PATCH] Add fc_id, which gives ID_PORT_NAME and ID_LUN on appropriate devices.
  • From: David Zeuthen <david@xxxxxxxx>
• [PATCH] Add fc_id to rules for devices it may handle.
  • From: Peter Jones <pjones@xxxxxxxxxx>
• [PATCH] Add fc_id, which gives ID_PORT_NAME and ID_LUN on appropriate devices.
  • From: Peter Jones <pjones@xxxxxxxxxx>
• [PATCH] Add fc_id, which gives ID_PORT_NAME and ID_LUN on appropriate devices.
  • From: Peter Jones <pjones@xxxxxxxxxx>
• Re: udev rules wont work
  • From: "eial@xxxxxxxxxxxx" <eial@xxxxxxxxxxxx>
• Re: udev rules wont work
  • From: Matthias Schwarzott <zzam@xxxxxxxxxx>
• Re: udev rules wont work
  • From: "eial@xxxxxxxxxxxx" <eial@xxxxxxxxxxxx>
• Re: udev rules wont work
  • From: Matthias Schwarzott <zzam@xxxxxxxxxx>
• Re: udev rules wont work
  • From: "eial@xxxxxxxxxxxx" <eial@xxxxxxxxxxxx>
• Re: udev rules wont work
  • From: "eial@xxxxxxxxxxxx" <eial@xxxxxxxxxxxx>
• Re: udev rules wont work
  • From: "eial@xxxxxxxxxxxx" <eial@xxxxxxxxxxxx>
• bnx2 firmware problem with 2.6.30
  • From: "Marco Berizzi" <pupilla@xxxxxxxxxxx>
• udev rules wont work
  • From: "eial@xxxxxxxxxxxx" <eial@xxxxxxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Alberto Gonzalez <alberto6674@xxxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: Trouble getting udev rule to fire, works in udevtest
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Trouble getting udev rule to fire, works in udevtest
  • From: Ben Beuchler <insyte@xxxxxxxxx>
• [PATCH 2/2] Use busnum/devnum rather than vid/pid for hid2hci
  • From: Mario Limonciello <mario_limonciello@xxxxxxxx>
• [PATCH 1/2] Add support to hid2hci for recovering Dell BT devices after S3
  • From: Mario Limonciello <mario_limonciello@xxxxxxxx>
• Re: Building udev-142 w/o inotify or ppoll
  • From: Bryan Kadzban <bryan@xxxxxxxxxxxxxxxxxxxxx>
• Re: RFC: mdadm and bringing up raid sets from initrd (dracut)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RFC: mdadm and bringing up raid sets from initrd (dracut)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RFC: mdadm and bringing up raid sets from initrd (dracut)
  • From: Harald Hoyer <harald@xxxxxxxxxx>
• Re: Building udev-142 w/o inotify or ppoll
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Building udev-142 w/o inotify or ppoll
  • From: "Philip A. Prindeville" <philipp_subx@xxxxxxxxxxxxxxxxxxxxx>
• Re: RFC: mdadm and bringing up raid sets from initrd (dracut)
  • From: Victor Lowther <victor.lowther@xxxxxxxxx>
• Re: RFC: mdadm and bringing up raid sets from initrd (dracut)
  • From: Jeremy Katz <katzj@xxxxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Mario Limonciello <mario_limonciello@xxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Mario Limonciello <mario_limonciello@xxxxxxxx>
• Re: RFC: mdadm and bringing up raid sets from initrd (dracut)
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: help naming video devices
  • From: Greg KH <greg@xxxxxxxxx>
• Re: help naming video devices
  • From: Richard Ray <rray@xxxxxxxxxxxxxxxx>
• Re: rule for old udev version
  • From: Xiaofan Chen <xiaofanc@xxxxxxxxx>
• Re: rule for old udev version
  • From: Nicola Maggi <nicola.maggi@xxxxxxxxx>
• Re: rule for old udev version
  • From: Xiaofan Chen <xiaofanc@xxxxxxxxx>
• rule for old udev version
  • From: Nicola Maggi <nicola.maggi@xxxxxxxxx>
• Re: help naming video devices
  • From: Bryan Kadzban <bryan@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Mario Limonciello <mario_limonciello@xxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• help naming video devices
  • From: Richard Ray <rray@xxxxxxxxxxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Mario Limonciello <mario_limonciello@xxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Mario Limonciello <mario_limonciello@xxxxxxxx>
• Re: RFC: mdadm and bringing up raid sets from initrd (dracut)
  • From: David Zeuthen <david@xxxxxxxx>
• Re: RFC: mdadm and bringing up raid sets from initrd (dracut)
  • From: David Zeuthen <david@xxxxxxxx>
• Re: RFC: mdadm and bringing up raid sets from initrd (dracut)
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: RFC: mdadm and bringing up raid sets from initrd (dracut)
  • From: Hans de Goede <hdegoede@xxxxxxxxxx>
• Re: RFC: mdadm and bringing up raid sets from initrd (dracut)
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• RFC: mdadm and bringing up raid sets from initrd (dracut)
  • From: Hans de Goede <hdegoede@xxxxxxxxxx>
• [ANNOUNCE] udev 145 release
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: howto get serial number of a tape drive?
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Enabling/disabling extras
  • From: Ozan Çağlayan <ozan@xxxxxxxxxxxxx>
• Re: howto get serial number of a tape drive?
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: howto get serial number of a tape drive?
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: howto get serial number of a tape drive?
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: howto get serial number of a tape drive?
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: howto get serial number of a tape drive?
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: udevadm - argument order question
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: howto get serial number of a tape drive?
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: howto get serial number of a tape drive?
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: udevadm - argument order question
  • From: Dan Nicholson <dbn.lists@xxxxxxxxx>
• Re: howto get serial number of a tape drive?
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• howto get serial number of a tape drive?
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: scsi_id: correct error handling in prepend_vendor_model
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• scsi_id: correct error handling in prepend_vendor_model
  • From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
• Re: udevadm - argument order question
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• udevadm - argument order question
  • From: "Thomas Bartosik" <thomas.bartosik@xxxxxx>
• Re: rule skipped during boot
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: rule skipped during boot
  • From: Ron Rindjunsky <rindjon@xxxxxxxxxxxxxx>
• [ANNOUNCE] udev 144 release
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Detect Hotplug events with hal, libudev, udev, devicekit-*
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Detect Hotplug events with hal, libudev, udev, devicekit-*
  • From: Mohamed Ikbel Boulabiar <boulabiar@xxxxxxxxx>
• Re: rule skipped during boot
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Detect Hotplug events with hal, libudev, udev, devicekit-*
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: rule skipped during boot
  • From: Ron Rindjunsky <rindjon@xxxxxxxxxxxxxx>
• Detect Hotplug events with hal, libudev, udev, devicekit-*
  • From: Mohamed Ikbel Boulabiar <boulabiar@xxxxxxxxx>
• Re: Some doubt regarding current state of Linux Hotpug
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Alberto Gonzalez <alberto6674@xxxxxxxxx>
• Re: Some doubt regarding current state of Linux Hotpug
  • From: unni krishnan <unnikrishnan.a@xxxxxxxxx>
• Re: Some doubt regarding current state of Linux Hotpug
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Some doubt regarding current state of Linux Hotpug
  • From: unni krishnan <unnikrishnan.a@xxxxxxxxx>
• Re: Some doubt regarding current state of Linux Hotpug
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Some doubt regarding current state of Linux Hotpug
  • From: unni krishnan <unnikrishnan.a@xxxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: rule skipped during boot
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Alberto Gonzalez <alberto6674@xxxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• rule skipped during boot
  • From: Ron Rindjunsky <rindjon@xxxxxxxxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: [pull] firmware: search for third party or sysadmin supplied firmware updates
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: udev and ISA network cards
  • From: Olaf <mailinglists@xxxxxxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Alberto Gonzalez <alberto6674@xxxxxxxxx>
• [PATCH] firmware: search for third party or sysadmin supplied firmware updates
  • From: jonathan@xxxxxxxxxxxxxx
• Re: [pull] firmware: search for third party or sysadmin supplied firmware updates
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• [pull] firmware: search for third party or sysadmin supplied firmware updates
  • From: Jon Masters <jonathan@xxxxxxxxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Matthew Garrett <mjg59@xxxxxxxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Mario Limonciello <mario_limonciello@xxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Matthew Garrett <mjg59@xxxxxxxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• Re: [PATCH udev] rules: set group ownership of new firewire driver device files
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH udev] rules: set group ownership of new firewire driver device files
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Matthew Garrett <mjg59@xxxxxxxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Mario Limonciello <mario_limonciello@xxxxxxxx>
• RE: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• RE: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: <Mario_Limonciello@xxxxxxxx>
• RE: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Alberto Gonzalez <alberto6674@xxxxxxxxx>
• RE: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: <Mario_Limonciello@xxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
  • From: Mario Limonciello <mario_limonciello@xxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: [ANNOUNCE] udev 143 release
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [ANNOUNCE] udev 143 release
  • From: "Gabor Z. Papp" <gzp@xxxxxxx>
• Re: udev and ISA network cards
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: udev and ISA network cards
  • From: Olaf <mailinglists@xxxxxxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Dave Airlie <airlied@xxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Alberto Gonzalez <alberto6674@xxxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Alberto Gonzalez <alberto6674@xxxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Alberto Gonzalez <alberto6674@xxxxxxxxx>
• Re: Kernel 2.6.30 and udevd problem
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Kernel 2.6.30 and udevd problem
  • From: Alberto Gonzalez <alberto6674@xxxxxxxxx>
• Re: udev and ISA network cards
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• udev and ISA network cards
  • From: Olaf <mailinglists@xxxxxxxxxxxx>
• Re: Who mounts sysfs?
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: remove event for device insertion.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Who mounts sysfs?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Who mounts sysfs?
  • From: Will Newton <will.newton@xxxxxxxxx>
• Re: Who mounts sysfs?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Who mounts sysfs?
  • From: Will Newton <will.newton@xxxxxxxxx>
• Re: Who mounts sysfs?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Who mounts sysfs?
  • From: Will Newton <will.newton@xxxxxxxxx>
• Re: Who mounts sysfs?
  • From: Greg KH <greg@xxxxxxxxx>
• Who mounts sysfs?
  • From: Will Newton <will.newton@xxxxxxxxx>
• [ANNOUNCE] udev 143 release
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• remove event for device insertion.
  • From: Santosh <santosh.ry@xxxxxxxxx>
• Re: [PATCH] Don't match Dell devices on KERNEL, instead use ATTR{bInterfaceProtocol}
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH] Don't match Dell devices on KERNEL, instead use ATTR{bInterfaceProtocol}
  • From: Mario Limonciello <mario_limonciello@xxxxxxxx>
• Re: [PATCH] Add bluetooth-hid2hci to udev-extras
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] Add bluetooth-hid2hci to udev-extras
  • From: Mario Limonciello <mario_limonciello@xxxxxxxx>
• document depmod -m
  • From: md@xxxxxxxx (Marco d'Itri)
• Re: [PATCH] Add bluetooth-hid2hci to udev-extras
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] Add bluetooth-hid2hci to udev-extras
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] Add bluetooth-hid2hci to udev-extras
  • From: Mario Limonciello <mario_limonciello@xxxxxxxx>
• Re: UDEV problem/questions....
  • From: J Decker <d3ck0r@xxxxxxxxx>
• UDEV problem/questions....
  • From: J Decker <d3ck0r@xxxxxxxxx>
• Re: [PATCH] Add bluetooth-hid2hci to udev-extras
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] Add bluetooth-hid2hci to udev-extras
  • From: Mario Limonciello <mario_limonciello@xxxxxxxx>
• Re: [PATCH] Add bluetooth-hid2hci to udev-extras
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: What are the kernel option required for udev in 2.6.28 kernel.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: What are the kernel option required for udev in 2.6.28 kernel.
  • From: Olaf <mailinglists@xxxxxxxxxxxx>
• Re: What are the kernel option required for udev in 2.6.28 kernel.
  • From: unni krishnan <unnikrishnan.a@xxxxxxxxx>
• Re: [PATCH] Add bluetooth-hid2hci to udev-extras
  • From: Mario Limonciello <mario_limonciello@xxxxxxxx>
• Re: What are the kernel option required for udev in 2.6.28 kernel.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: What are the kernel option required for udev in 2.6.28 kernel.
  • From: unni krishnan <unnikrishnan.a@xxxxxxxxx>
• Re: What are the kernel option required for udev in 2.6.28 kernel.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: What are the kernel option required for udev in 2.6.28 kernel.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: What are the kernel option required for udev in 2.6.28 kernel.
  • From: unni krishnan <unnikrishnan.a@xxxxxxxxx>
• Re: What are the kernel option required for udev in 2.6.28 kernel.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH] Add bluetooth-hid2hci to udev-extras
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• What are the kernel option required for udev in 2.6.28 kernel.
  • From: unni krishnan <unnikrishnan.a@xxxxxxxxx>
• [PATCH] Add bluetooth-hid2hci to udev-extras
  • From: Mario Limonciello <mario_limonciello@xxxxxxxx>
• Re: udev rule for unmount action
  • From: Christian Schmitt <chris@xxxxxxxxxxxxx>
• Re: Patch: create by-id symlink for pure HID devices
  • From: Frederic Crozat <fcrozat@xxxxxxxxxxxx>
• Re: Patch: create by-id symlink for pure HID devices
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Patch: create by-id symlink for pure HID devices
  • From: Frederic Crozat <fcrozat@xxxxxxxxxxxx>
• Re: Mapping /dev/*st0* to fixed names using scsi_id
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: udev rule for unmount action
  • From: David Zeuthen <david@xxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Bryan Kadzban <bryan@xxxxxxxxxxxxxxxxxxxxx>
• Re: udev rule for unmount action
  • From: Christian Schmitt <chris@xxxxxxxxxxxxx>
• Re: udev rule for unmount action
  • From: Karel Zak <kzak@xxxxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Scott James Remnant <scott@xxxxxxxxxx>
• Re: udev rule for unmount action
  • From: Christian Schmitt <chris@xxxxxxxxxxxxx>
• Re: Mapping /dev/*st0* to fixed names using scsi_id
  • From: John Huttley <John@xxxxxxxxxxxxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Bryan Kadzban <bryan@xxxxxxxxxxxxxxxxxxxxx>
• Re: udev rule for unmount action
  • From: md@xxxxxxxx (Marco d'Itri)
• udev rule for unmount action
  • From: Christian Schmitt <chris@xxxxxxxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Mapping /dev/*st0* to fixed names using scsi_id
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: [PATCH] rules: avoid reading DRIVER for devices without modalias
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Mapping /dev/*st0* to fixed names using scsi_id
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [PATCH] rules: avoid reading DRIVER for devices without modalias
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH] rules: avoid reading DRIVER for devices without modalias
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Alan Jenkins <sourcejedi.lkml@xxxxxxxxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: Udev rule for external HD
  • From: unni krishnan <unnikrishnan.a@xxxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Udev rule for external HD
  • From: Greg KH <greg@xxxxxxxxx>
• Udev rule for external HD
  • From: unni krishnan <unnikrishnan.a@xxxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: /lib/udev/devices/ missing in udev-135
  • From: Rob Desbois <rob.desbois@xxxxxxxxx>
• Re: /lib/udev/devices/ missing in udev-135
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• /lib/udev/devices/ missing in udev-135
  • From: Rob Desbois <rob.desbois@xxxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• RAID controller, create custom sdX symlinks
  • From: Jan Wagner <jwagner@xxxxxxxxxxx>
• Re: [PATCH] queue-export: fix crash
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH] queue-export: fix crash
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: [GIT] Experimental threaded udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [GIT] Experimental threaded udev
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: udev rule for usb drive
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• udev rule for usb drive
  • From: Mike Mildner <mike.mildner@xxxxxxxxxx>
• udev rule for usb drive
  • From: Mike Mildner <mike.mildner@xxxxxxxxxx>
• Re: udev rule executes command, wont add device node
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: udev rule executes command, wont add device node
  • From: Luke Harvey <digilogik@xxxxxxxxx>
• Re: udev rule executes command, wont add device node
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• udev rule executes command, wont add device node
  • From: Luke Harvey <digilogik@xxxxxxxxx>
• Re: [PATCH v2] udevd: don't use alarm() for timeouts
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: [PATCH v2] udevd: don't use alarm() for timeouts
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH v2] udevd: don't use alarm() for timeouts
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: [PATCH 1/2] udevd: respect the value of TIMEOUT in uevents
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: [PATCH v2] udevd: don't use alarm() for timeouts
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH 1/2] udevd: respect the value of TIMEOUT in uevents
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH v2] udevd: don't use alarm() for timeouts
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: [PATCH 1/2] udevd: respect the value of TIMEOUT in uevents
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: [PATCH 1/2] udevd: respect the value of TIMEOUT in uevents
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH 2/2] udevd: don't use alarm() for timeouts
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• [PATCH 1/2] udevd: respect the value of TIMEOUT in uevents
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: Good news for threading!
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: Good news for threading!
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: Good news for threading!
  • From: Scott James Remnant <scott@xxxxxxxxxx>
• Re: Good news for threading!
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Good news for threading!
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: Good news for threading!
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Good news for threading!
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as interface name
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as interface name
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as interface name
  • From: Matthias Schwarzott <zzam@xxxxxxxxxx>
• Re: [PATCH 2/2] firewire: core: add sysfs attribute for easier udev rules
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as interface name
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] firewire: core: add sysfs attribute for easier udev rules
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH 2/2] firewire: core: add sysfs attribute for easier udev rules
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• [PATCH 2/2] firewire: core: add sysfs attribute for easier udev rules
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• [PATCH 1/2] firewire: core: check for missing struct update at build time, not run time
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: Newer udev not performing %-substitutions on OWNER and GROUP
  • From: Benjamin Gilbert <bgilbert@xxxxxxxxxx>
• Re: [PATCH] test: Check string substitutions in OWNER and GROUP
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH] test: Check string substitutions in OWNER and GROUP
  • From: Benjamin Gilbert <bgilbert@xxxxxxxxxx>
• Re: edd_id util
  • From: Alan Jenkins <sourcejedi.lkml@xxxxxxxxxxxxxx>
• Re: rules: avoid traversing parent of every single device?
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: rules: avoid traversing parent of every single device?
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: rules: avoid traversing parent of every single device?
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: rules: avoid traversing parent of every single device?
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: rules: avoid traversing parent of every single device?
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• rules: avoid traversing parent of every single device?
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: scsi_sysfs_add_sdev(): uevent emission versus attribute creation
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: scsi_sysfs_add_sdev(): uevent emission versus attribute creation
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• scsi_sysfs_add_sdev(): uevent emission versus attribute creation
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: [PATCH udev] rules: set group ownership of new firewire driver device files
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH udev] rules: set group ownership of new firewire driver device files
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] implement a more efficient queue file format
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: unwise IEEE 1394 udev rules from Ubuntu merged into mainline udev
  • From: Bill Fink <billfink@xxxxxxxxxxxxxx>
• Re: [PATCH udev] rules: set group ownership of new firewire driver device files
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as interface name
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: Newer udev not performing %-substitutions on OWNER and GROUP
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Newer udev not performing %-substitutions on OWNER and GROUP
  • From: Benjamin Gilbert <bgilbert@xxxxxxxxxx>
• Re: [PATCH] implement a more efficient queue file format
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as interface name
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as interface name
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: [PATCH udev] rules: set group ownership of new firewire driver device files
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH udev] rules: set group ownership of new firewire driver device files
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as interface name
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: unwise IEEE 1394 udev rules from Ubuntu merged into mainline udev
  • From: Pieter Palmers <pieterp@xxxxxxx>
• Re: unwise IEEE 1394 udev rules from Ubuntu merged into mainline udev
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: [PATCH udev] rules: set group ownership of new firewire driver device files
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH] implement a more efficient queue file format
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: [PATCH udev] rules: set group ownership of new firewire driver device files
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: unwise IEEE 1394 udev rules from Ubuntu merged into mainline udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH udev] rules: set group ownership of new firewire driver device files
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as interface name
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: udevd.c: tiny bit of dead code
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• unwise IEEE 1394 udev rules from Ubuntu merged into mainline udev
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: [PATCH udev] rules: set group ownership of new firewire driver device files
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• [PATCH udev] rules: set group ownership of new firewire driver device files
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as interface name
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• udevd.c: tiny bit of dead code
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as interface name
  • From: Jiri Pirko <jpirko@xxxxxxxxxx>
• [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as interface name
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• [PATCH] ieee1394: sbp2: change default /dev/disk/by-id naming policy
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: edd_id util
  • From: Alan Jenkins <sourcejedi.lkml@xxxxxxxxxxxxxx>
• Re: udev questions
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: udev questions
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: Debugging udevd startup time
  • From: Ozan Çağlayan <ozan@xxxxxxxxxxxxx>
• Re: Debugging udevd startup time
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Debugging udevd startup time
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Debugging udevd startup time
  • From: Ozan Çağlayan <ozan@xxxxxxxxxxxxx>
• edd_id util
  • From: Orgad Shaneh <orgads@xxxxxxxxx>
• Re: [PATCH] udevadm: settle - fix timeout
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH] udevadm: settle - fix timeout
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: Debugging udevd startup time
  • From: Ozan Çağlayan <ozan@xxxxxxxxxxxxx>
• Re: Debugging udevd startup time
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Debugging udevd startup time
  • From: Alan Jenkins <sourcejedi.lkml@xxxxxxxxxxxxxx>
• Debugging udevd startup time
  • From: Ozan Çağlayan <ozan@xxxxxxxxxxxxx>
• Re: udevd move from select() to ppoll()
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• udevd move from select() to ppoll()
  • From: Coleman Kane <ckane@xxxxxxxxxxxxxxx>
• [ANNOUNCE] udev 142 release
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: util-linux-ng required? which version?
  • From: Karel Zak <kzak@xxxxxxxxxx>
• Re: util-linux-ng required? which version?
  • From: Olaf <mailinglists@xxxxxxxxxxxx>
• Re: util-linux-ng required? which version?
  • From: Karel Zak <kzak@xxxxxxxxxx>
• SYSFS and ATTR for testing attributes
  • From: Méher Khiari <keikun2004@xxxxxxxxx>
• Re: util-linux-ng required? which version?
  • From: Olaf <mailinglists@xxxxxxxxxxxx>
• Re: util-linux-ng required? which version?
  • From: Jürg Billeter <j@xxxxxxxxx>
• RE: How can I bring up a dialogue window when a usb device plugged?
  • From: Andy Chen <andychen_ca@xxxxxxxxxxx>
• Re: How can I bring up a dialogue window when a usb device plugged?
  • From: Greg KH <greg@xxxxxxxxx>
• RE: How can I bring up a dialogue window when a usb device plugged?
  • From: Andy Chen <andychen_ca@xxxxxxxxxxx>
• Re: How can I bring up a dialogue window when a usb device plugged?
  • From: Greg KH <greg@xxxxxxxxx>
• How can I bring up a dialogue window when a usb device plugged?
  • From: Andy Chen <andychen_ca@xxxxxxxxxxx>
• Re: util-linux-ng required? which version?
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: util-linux-ng required? which version?
  • From: Karel Zak <kzak@xxxxxxxxxx>
• Re: util-linux-ng required? which version?
  • From: Matthias Schwarzott <zzam@xxxxxxxxxx>
• util-linux-ng required? which version?
  • From: Matthias Schwarzott <zzam@xxxxxxxxxx>
• Re: hal, udev and video4linux probers
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: faking or posing as a specific USB ID?
  • From: Greg KH <greg@xxxxxxxxx>
• faking or posing as a specific USB ID?
  • From: Jani Monoses <jani@xxxxxxxxxx>
• Re: hal, udev and video4linux probers
  • From: Filippo Argiolas <fargiolas@xxxxxxxxx>
• Re: hal, udev and video4linux probers
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: hal, udev and video4linux probers
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: hal, udev and video4linux probers
  • From: Filippo Argiolas <fargiolas@xxxxxxxxx>
• Re: hal, udev and video4linux probers
  • From: Filippo Argiolas <fargiolas@xxxxxxxxx>
• Re: hal, udev and video4linux probers
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: hal, udev and video4linux probers
  • From: David Zeuthen <david@xxxxxxxx>
• Re: hal, udev and video4linux probers
  • From: Filippo Argiolas <fargiolas@xxxxxxxxx>
• Re: hal, udev and video4linux probers
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• hal, udev and video4linux probers
  • From: Filippo Argiolas <fargiolas@xxxxxxxxx>
• Re: [PATCH] inotify: report rounded-up event size to user space
  • From: Eric Paris <eparis@xxxxxxxxxx>
• [PATCH] inotify: report rounded-up event size to user space
  • From: Wu Fengguang <fengguang.wu@xxxxxxxxx>
• Re: very slow NFS boot on linux-next and -mm
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] Whitelist NICs that violate MAC assignement scheme
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: very slow NFS boot on linux-next and -mm
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: very slow NFS boot on linux-next and -mm
  • From: Wu Fengguang <fengguang.wu@xxxxxxxxx>
• [PATCH] Whitelist NICs that violate MAC assignement scheme
  • From: Lubomir Rintel <lkundrak@xxxxx>
• Re: Kernel 2.6.26-2-686 won't boot: udev error
  • From: md@xxxxxxxx (Marco d'Itri)
• Kernel 2.6.26-2-686 won't boot: udev error
  • From: Randy G <randyg@xxxxxxx>
• Re: Best practice for loading platform modules
  • From: Chris Hallinan <challinan@xxxxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Best practice for loading platform modules
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: Best practice for loading platform modules
  • From: Chris Hallinan <challinan@xxxxxxxxx>
• Re: Best practice for loading platform modules
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Best practice for loading platform modules
  • From: Chris Hallinan <challinan@xxxxxxxxx>
• Re: Best practice for loading platform modules
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Best practice for loading platform modules
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Best practice for loading platform modules
  • From: Chris Hallinan <challinan@xxxxxxxxx>
• Re: Best practice for loading platform modules
  • From: Greg KH <greg@xxxxxxxxx>
• Re: compiling udev 141 on linux 2.4
  • From: "Gabor Z. Papp" <gzp@xxxxxxx>
• Re: Best practice for loading platform modules
  • From: Chris Hallinan <challinan@xxxxxxxxx>
• Re: Best practice for loading platform modules
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Best practice for loading platform modules
  • From: Greg KH <greg@xxxxxxxxx>
• Best practice for loading platform modules
  • From: Chris Hallinan <challinan@xxxxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Karel Zak <kzak@xxxxxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: Udev integration for device-mapper and its subsystems.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Udev integration for device-mapper and its subsystems.
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: udev: gpio-keys input driver should have class kbd
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Udev: persistent-net-generator.rules and USB Devices
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• udev: gpio-keys input driver should have class kbd
  • From: md@xxxxxxxx (Marco d'Itri)
• Re: udev and tape drives
  • From: Horst Simon <hsimon@xxxxxxxxxxxxxxx>
• Re: udev and tape drives
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• udev and tape drives
  • From: Horst Simon <hsimon@xxxxxxxxxxxxxxx>
• Re: [PATCH]: make /dev/cpu/<n>/cpuid world readable
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: compiling udev 141 on linux 2.4
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: compiling udev 141 on linux 2.4
  • From: "Gabor Z. Papp" <gzp@xxxxxxx>
• Re: compiling udev 141 on linux 2.4
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• compiling udev 141 on linux 2.4
  • From: "Gabor Z. Papp" <gzp@xxxxxxx>
• [PATCH]: make /dev/cpu/<n>/cpuid world readable
  • From: Andre Przywara <andre.przywara@xxxxxxx>
• Re: Udev support under Denx eldk ?
  • From: Greg KH <greg@xxxxxxxxx>
• Udev support under Denx eldk ?
  • From: "Bob Eikel" <bobe@xxxxxxxxxxx>
• Re: CD-ROM tray closes automatically after eject due to random session/track count
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: udev_queue_get_seqnum_is_finished
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: udev_queue_get_seqnum_is_finished
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: udev_queue_get_seqnum_is_finished
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: udev_queue_get_seqnum_is_finished
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• udev_queue_get_seqnum_is_finished
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: CD-ROM tray closes automatically after eject due to random session/track count
  • From: Martin Pitt <martin.pitt@xxxxxxxxxx>
• Re: CD-ROM tray closes automatically after eject due to random session/track count
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: CD-ROM tray closes automatically after eject due to random session/track count
  • From: Martin Pitt <martin.pitt@xxxxxxxxxx>
• Re: CD-ROM tray closes automatically after eject due to random session/track count
  • From: Martin Pitt <martin.pitt@xxxxxxxxxx>
• Re: CD-ROM tray closes automatically after eject due to random session/track count
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• CD-ROM tray closes automatically after eject due to random session/track count
  • From: Martin Pitt <martin.pitt@xxxxxxxxxx>
• Re: [PATCH] support identification of Xen virtual block devices
  • From: Ian Campbell <ijc@xxxxxxxxxxxxxx>
• Re: [PATCH] support identification of Xen virtual block devices
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] support identification of Xen virtual block devices
  • From: Ian Campbell <ijc@xxxxxxxxxxxxxx>
• Re: [PATCH] support identification of Xen virtual block devices
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH] support identification of Xen virtual block devices
  • From: Ian Campbell <ijc@xxxxxxxxxxxxxx>
• Re: Bug#499868: udev: multiple mac80211 interfaces created on the same physical device are incorrectly renamed
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Bug#499868: udev: multiple mac80211 interfaces created on the same physical device are incorrectly renamed
  • From: "Marco d'Itri" <md@xxxxxxxx>
• Re: libudev major number not increased
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: libudev major number not increased
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• Re: libudev major number not increased
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: libudev major number not increased
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• Re: libudev major number not increased
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• libudev major number not increased
  • From: Harald Hoyer <harald@xxxxxxxxxx>
• Re: [PATCH] 64-md-raid.rules fixes v2
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Matt Domsch <Matt_Domsch@xxxxxxxx>
• [ANNOUNCE] udev 141 release
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Q: PCIE card power budget
  • From: Krishna Kothapalli <krishna_sunitha@xxxxxxxxxxx>
• Bug#499868: udev: multiple mac80211 interfaces created on the same physical device are incorrectly renamed
  • From: md@xxxxxxxx (Marco d'Itri)
• Re: [PATCH] Avoid leaking netlink socket fd to external programs
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH] Avoid leaking netlink socket fd to external programs
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: Udev: persistent-net-generator.rules and USB Devices
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Udev: persistent-net-generator.rules and USB Devices
  • From: "Omair Eshkenazi" <stimpson@xxxxxxxxxxxxxxx>
• Re: Bug#522091: udev: unable to make hdd go standby
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Bug#522091: udev: unable to make hdd go standby
  • From: md@xxxxxxxx (Marco d'Itri)
• Re: Network Device Naming mechanism and policy
  • From: Kurt Van Dijck <kurt.van.dijck@xxxxxx>
• Re: Question about debugging the source of uevents
  • From: Tom <tomgparchaur@xxxxxxxxx>
• Re: Question about debugging the source of uevents
  • From: Jim Paris <jim@xxxxxxxx>
• Re: Question about debugging the source of uevents
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Question about debugging the source of uevents
  • From: Tom <tomgparchaur@xxxxxxxxx>
• Re: Question about debugging the source of uevents
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Question about debugging the source of uevents
  • From: Tom <tomgparchaur@xxxxxxxxx>
• Re: Question about debugging the source of uevents
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Question about debugging the source of uevents
  • From: Tom <tomgparchaur@xxxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Len Brown <lenb@xxxxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Dan Williams <dcbw@xxxxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Dan Williams <dcbw@xxxxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Matt Domsch <Matt_Domsch@xxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: udev problem (and fix) for /dev/mtdblock*
  • From: David Brownell <david-b@xxxxxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Matt Domsch <Matt_Domsch@xxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: david@xxxxxxx
• Re: Network Device Naming mechanism and policy
  • From: david@xxxxxxx
• Re: Network Device Naming mechanism and policy
  • From: Scott James Remnant <scott@xxxxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Bill Nottingham <notting@xxxxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Matt Domsch <Matt_Domsch@xxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Matt Domsch <Matt_Domsch@xxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: "Karl O. Pinc" <kop@xxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Patrick McHardy <kaber@xxxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Scott James Remnant <scott@xxxxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Dan Williams <dcbw@xxxxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Patrick McHardy <kaber@xxxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Network Device Naming mechanism and policy
  • From: Patrick McHardy <kaber@xxxxxxxxx>
• Network Device Naming mechanism and policy
  • From: Matt Domsch <Matt_Domsch@xxxxxxxx>
• Re: udev problem (and fix) for /dev/mtdblock*
  • From: David Brownell <david-b@xxxxxxxxxxx>
• Re: udev problem (and fix) for /dev/mtdblock*
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: udev problem (and fix) for /dev/mtdblock*
  • From: David Brownell <david-b@xxxxxxxxxxx>
• Re: udev problem (and fix) for /dev/mtdblock*
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: udev problem (and fix) for /dev/mtdblock*
  • From: David Brownell <david-b@xxxxxxxxxxx>
• Re: udev 140 and missing /dev/root symlink
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• udev 140 and missing /dev/root symlink
  • From: md@xxxxxxxx (Marco d'Itri)
• Re: udev problem (and fix) for /dev/mtdblock*
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: udev problem (and fix) for /dev/mtdblock*
  • From: David Brownell <david-b@xxxxxxxxxxx>
• Re: udev problem (and fix) for /dev/mtdblock*
  • From: Scott James Remnant <scott@xxxxxxxxxxxxx>
• Re: [PATCH] udevadm monitor --filter= with GL_PLAIN comparison
  • From: Petr Lautrbach <plautrba@xxxxxxxxxx>
• Re: Bug#501503: udev: Griffin Powermate USB knob doesn't get /dev/input/by-id|path links
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: udev problem (and fix) for /dev/mtdblock*
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] udevadm monitor --filter= with GL_PLAIN comparison
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: udev-140 Bug: udevadm test changing mode of /dev to 660, so making /dev unusuable for users
  • From: Matthias Schwarzott <zzam@xxxxxxxxxx>
• Fwd: udev problem (and fix) for /dev/mtdblock*
  • From: David Brownell <david-b@xxxxxxxxxxx>
• [PATCH] udevadm monitor --filter= with GL_PLAIN comparison
  • From: Petr Lautrbach <plautrba@xxxxxxxxxx>
• Re: udev-140 Bug: udevadm test changing mode of /dev to 660, so making /dev unusuable for users
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: udev-140 Bug: udevadm test changing mode of /dev to 660, so making /dev unusuable for users
  • From: Matthias Schwarzott <zzam@xxxxxxxxxx>
• Re: udev-140 Bug: udevadm test changing mode of /dev to 660, so making /dev unusuable for users
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• udev-140 Bug: udevadm test changing mode of /dev to 660, so making /dev unusuable for users
  • From: Matthias Schwarzott <zzam@xxxxxxxxxx>
• Bug#501503: udev: Griffin Powermate USB knob doesn't get /dev/input/by-id|path links
  • From: md@xxxxxxxx (Marco d'Itri)
• Re: vol_id doesn't recognize unjournaled ext4
  • From: Karel Zak <kzak@xxxxxxxxxx>
• Re: Problem recreating 70-persistent-net.rules with udev 0.125-7 on Debian 5.0
  • From: Nilshar <nilshar@xxxxxxxxx>
• Re: [PATCH] Document actions a bit more in "udevadm trigger --help"
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] Document actions a bit more in "udevadm trigger --help"
  • From: Robby Workman <rw@xxxxxxxxxxxxx>
• Re: [PATCH 0/4] Documentation fixes.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] Document actions a bit more in "udevadm trigger --help"
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH] Document actions a bit more in "udevadm trigger --help"
  • From: Robby Workman <rw@xxxxxxxxxxxxx>
• [PATCH 4/4] extras: Fix language in vol_id manpage.
  • From: Adam Buchbinder <adam.buchbinder@xxxxxxxxx>
• [PATCH 3/4] extras: Expand create_floppy_devices manpage.
  • From: Adam Buchbinder <adam.buchbinder@xxxxxxxxx>
• [PATCH 2/4] extras: Update cdrom_id manpage.
  • From: Adam Buchbinder <adam.buchbinder@xxxxxxxxx>
• [PATCH 1/4] extras: Add usb_id manpage.
  • From: Adam Buchbinder <adam.buchbinder@xxxxxxxxx>
• [PATCH 0/4] Documentation fixes.
  • From: Adam Buchbinder <adam.buchbinder@xxxxxxxxx>
• Re: [PATCH] 64-md-raid.rules fixes v2
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH] 64-md-raid.rules fixes v2
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: [PATCH] 64-md-raid.rules fixes
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: [PATCH] 64-md-raid.rules fixes
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH] 64-md-raid.rules fixes
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: vol_id doesn't recognize unjournaled ext4
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• vol_id doesn't recognize unjournaled ext4
  • From: Andre Beck <beck@xxxxxx>
• Re: [ANNOUNCE] udev 140 release
  • From: Sujit Karataparambil <sjt.kar@xxxxxxxxx>
• [ANNOUNCE] udev 140 release
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: USB driver assignment with udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: USB driver assignment with udev
  • From: Steve Calfee <nospamcalfee@xxxxxxxxx>
• Re: Problem recreating 70-persistent-net.rules with udev 0.125-7 on Debian 5.0
  • From: Sujit Karataparambil <sjt.kar@xxxxxxxxx>
• Re: Problem recreating 70-persistent-net.rules with udev 0.125-7 on Debian 5.0
  • From: Nilshar <nilshar@xxxxxxxxx>
• Re: USB driver assignment with udev
  • From: Scott James Remnant <scott@xxxxxxxxxxxxx>
• Re: USB driver assignment with udev
  • From: Greg KH <greg@xxxxxxxxx>
• Re: USB driver assignment with udev
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: USB driver assignment with udev
  • From: Steve Calfee <nospamcalfee@xxxxxxxxx>
• Re: USB driver assignment with udev
  • From: Greg KH <greg@xxxxxxxxx>
• USB driver assignment with udev
  • From: Steve Calfee <nospamcalfee@xxxxxxxxx>
• Re: Problem recreating 70-persistent-net.rules with udev 0.125-7 on Debian 5.0
  • From: Scott James Remnant <scott@xxxxxxxxxxxxx>
• Re: console group owership
  • From: Harald Hoyer <harald@xxxxxxxxxx>
• Re: Problem recreating 70-persistent-net.rules with udev 0.125-7 on Debian 5.0
  • From: md@xxxxxxxx (Marco d'Itri)
• Re: Problem recreating 70-persistent-net.rules with udev 0.125-7 on Debian 5.0
  • From: Nilshar <nilshar@xxxxxxxxx>
• Re: Problem recreating 70-persistent-net.rules with udev 0.125-7 on Debian 5.0
  • From: md@xxxxxxxx (Marco d'Itri)
• Re: Problem recreating 70-persistent-net.rules with udev 0.125-7 on Debian 5.0
  • From: md@xxxxxxxx (Marco d'Itri)
• Re: Problem recreating 70-persistent-net.rules with udev 0.125-7 on Debian 5.0
  • From: Nilshar <nilshar@xxxxxxxxx>
• Re: console group owership
  • From: md@xxxxxxxx (Marco d'Itri)
• Re: Problem recreating 70-persistent-net.rules with udev 0.125-7 on Debian 5.0
  • From: Nilshar <nilshar@xxxxxxxxx>
• Re: firmware.sh questions
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Problem recreating 70-persistent-net.rules with udev 0.125-7 on Debian 5.0
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: firmware.sh questions
  • From: Leandro Dorileo <ldorileo@xxxxxxxxx>
• Problem recreating 70-persistent-net.rules with udev 0.125-7 on Debian 5.0
  • From: Nilshar <nilshar@xxxxxxxxx>
• console group owership
  • From: Harald Hoyer <harald@xxxxxxxxxx>
• Re: libvolume_id minor number not increased
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• libvolume_id minor number not increased
  • From: Harald Hoyer <harald@xxxxxxxxxx>
• Re: linux hotplug SF website
  • From: Leandro Dorileo <ldorileo@xxxxxxxxx>
• linux hotplug SF website
  • From: Rob Desbois <rob.desbois@xxxxxxxxxxxxx>
• Re: [PATCH] Fix compile error in debug mode: error: ‘struct <anonymous>’ has no member named ‘i’
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH] Fix compile error in debug mode: error: ‘struct <anonymous>’ has no member named ‘i’
  • From: Michael Prokop <mika@xxxxxxxx>
• Re: Interaction of udev with the init subsystem
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Interaction of udev with the init subsystem
  • From: Greg KH <greg@xxxxxxxxx>
• Interaction of udev with the init subsystem
  • From: Ozan Çağlayan <ozan@xxxxxxxxxxxxx>
• Re: Regression in udev-139?
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Regression in udev-139?
  • From: Chris Clayton <chris2553@xxxxxxxxxxxxxx>
• Re: ftdi_sio usb-serial driver and hotplug
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: ftdi_sio usb-serial driver and hotplug
  • From: "Anton Fedorov" <datacompboy@xxxxxxxxxxx>
• [ANNOUNCE] udev 139 release
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Linux kernel programming
  • From: Sabin <linuxguru75@xxxxxxxxx>
• Re: cdrom_id from udev-135 hangs
  • From: ljb <ljb1813@xxxxxxxxx>
• Re: udev multithread
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: Configuring udev statically
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Configuring udev statically
  • From: Ersin Akinci <ersin.akinci@xxxxxxxxx>
• Re: Linux kernel programming
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: cdrom_id from udev-135 hangs
  • From: Bryan Kadzban <bryan@xxxxxxxxxxxxxxxxxxxxx>
• Re: cdrom_id from udev-135 hangs
  • From: ljb <ljb1813@xxxxxxxxx>
• Re: ftdi_sio usb-serial driver and hotplug
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• ftdi_sio usb-serial driver and hotplug
  • From: Anton Fedorov <datacompboy@xxxxxxxxxxx>
• Re: cdrom_id from udev-135 hangs
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• cdrom_id from udev-135 hangs
  • From: ljb <ljb1813@xxxxxxxxx>
• Re: udev multithread
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• How to write rule sound card 2
  • From: Attid@xxxxxxxxx
• udev can't run
  • From: liu yang <liudows2@xxxxxxxxx>
• Re: Linux kernel programming
  • From: pradeep singh <pradeep.rautela@xxxxxxxxx>
• Re: FAQ Somewhere? USB error messges
  • From: Greg KH <greg@xxxxxxxxx>
• Re: FAQ Somewhere? USB error messges
  • From: "Yan Seiner" <yan@xxxxxxxxxx>
• Re: FAQ Somewhere? USB error messges
  • From: Greg KH <greg@xxxxxxxxx>
• Re: FAQ Somewhere? USB error messges
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: FAQ Somewhere? USB error messges
  • From: Yan Seiner <yan@xxxxxxxxxx>
• Re: FAQ Somewhere? USB error messges
  • From: Greg KH <greg@xxxxxxxxx>
• FAQ Somewhere? USB error messges
  • From: Yan Seiner <yan@xxxxxxxxxx>
• [ANNOUNCE] udev 138 release
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: model/vendor enc strings
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• model/vendor enc strings
  • From: David Zeuthen <david@xxxxxxxx>
• How to write rule sound card?
  • From: Attid@xxxxxxxxx
• Re: How to write this rule?
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: How to write this rule?
  • From: "Yan Seiner" <yan@xxxxxxxxxx>
• Re: How to write this rule?
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• How to write this rule?
  • From: Yan Seiner <yan@xxxxxxxxxx>
• Re: firmware.sh questions
  • From: Leandro Dorileo <ldorileo@xxxxxxxxx>
• Re: firmware.sh questions
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: firmware.sh questions
  • From: Dan Nicholson <dbn.lists@xxxxxxxxx>
• firmware.sh questions
  • From: Leandro Dorileo <ldorileo@xxxxxxxxx>
• Re: MD removal and condition code bug
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: MD removal and condition code bug
  • From: Harald Hoyer <harald@xxxxxxxxxx>
• Re: MD removal and condition code bug
  • From: Harald Hoyer <harald@xxxxxxxxxx>
• Re: MD removal and condition code bug
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• MD removal and condition code bug
  • From: Harald Hoyer <harald@xxxxxxxxxx>
• Re: udev rule MODE not working?
  • From: Dirk Beer <rdbeer@xxxxxxxxx>
• Re: udev rule MODE not working?
  • From: Dan Nicholson <dbn.lists@xxxxxxxxx>
• Fwd: udev rule MODE not working?
  • From: Dirk Beer <rdbeer@xxxxxxxxx>
• udev rule MODE not working?
  • From: Dirk Beer <rdbeer@xxxxxxxxx>
• Re: Query on udev: how to not create a device node by default
  • From: Soh Kam Yung <sohkamyung@xxxxxxxxx>
• Re: Query on udev: how to not create a device node by default
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Query on udev: how to not create a device node by default
  • From: Soh Kam Yung <sohkamyung@xxxxxxxxx>
• Re: Query on udev: how to not create a device node by default
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Query on udev: how to not create a device node by default
  • From: Soh Kam Yung <sohkamyung@xxxxxxxxx>
• Re: Query on udev: how to not create a device node by default
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Query on udev: how to not create a device node by default
  • From: Soh Kam Yung <sohkamyung@xxxxxxxxx>
• RE: Odd behavior with udev and kgdb
  • From: "Richard Schmitt" <rschmitt@xxxxxxxxxxx>
• Re: Odd behavior with udev and kgdb
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• RE: Odd behavior with udev and kgdb
  • From: "Richard Schmitt" <rschmitt@xxxxxxxxxxx>
• Re: Odd behavior with udev and kgdb
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Odd behavior with udev and kgdb
  • From: "Richard Schmitt" <rschmitt@xxxxxxxxxxx>
• Re: UPS USB serial device is not detected properly
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH] Writing udev rules: refer to 'udevadm info' instead of 'udevinfo'
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] vol_id: fix ddf version string
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] vol_id: add missing id->type to swap0
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH] vol_id: add missing id->type to swap0
  • From: Karel Zak <kzak@xxxxxxxxxx>
• [PATCH] vol_id: fix ddf version string
  • From: Karel Zak <kzak@xxxxxxxxxx>
• [ANNOUNCE] udev 137 release
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH] Writing udev rules: refer to 'udevadm info' instead of 'udevinfo'
  • From: Miklos Vajna <vmiklos@xxxxxxxxxxxxxx>
• no /dev/sd* for sony ericsson c702
  • From: murray lotnicz <murray9000@xxxxxxxxx>
• udev rules help needed
  • From: Richard Ray <rray@xxxxxxxxxxxxxxxx>
• "Writing udev rules" HTML documentation mentions udevinfo
  • From: Martin von Gagern <Martin.vGagern@xxxxxxx>
• Finding keyboards and mice and other devices
  • From: Yan Seiner <yan@xxxxxxxxxx>
• Re: [PATCH] Allow user and group lookup to be disabled.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH] Expose delayed name resolution
  • From: Scott James Remnant <scott@xxxxxxxxxx>
• [PATCH] Allow user and group lookup to be disabled.
  • From: Scott James Remnant <scott@xxxxxxxxxx>
• udev 126 will bring on screen flicker once
  • From: danielgong <danielgong@xxxxxxxxxx>
• Re: [PATCH] man: typo fixes
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH] remove stray initializer
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH] remove stray initializer
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• [PATCH] man: typo fixes
  • From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
• Re: Add rulesdir to libudev.pc
  • From: Karel Zak <kzak@xxxxxxxxxx>
• Re: udev rules bug (ide cdrom)
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• udev rules bug (ide cdrom)
  • From: Scott James Remnant <scott@xxxxxxxxxxxxx>
• Re: Add rulesdir to libudev.pc
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Add rulesdir to libudev.pc
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• Re: Add rulesdir to libudev.pc
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Add rulesdir to libudev.pc
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• Re: [PATCH 1/1] udev/pkgconfig: fix exec_prefix to be generated from @exec_prefix@
  • From: Inaky Perez-Gonzalez <inaky@xxxxxxxxxxxxxxx>
• RE: [PATCH 1/1] udev/pkgconfig: fix exec_prefix to be generated from @exec_prefix@
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• Re: [PATCH 1/1] udev/pkgconfig: fix exec_prefix to be generated from @exec_prefix@
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• RE: [PATCH 1/1] udev/pkgconfig: fix exec_prefix to be generated from @exec_prefix@
  • From: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@xxxxxxxxx>
• Re: [PATCH 1/1] udev/pkgconfig: fix exec_prefix to be generated from @exec_prefix@
  • From: Inaky Perez-Gonzalez <inaky@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/1] udev/pkgconfig: fix exec_prefix to be generated from @exec_prefix@
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• Re: [PATCH 1/1] udev/pkgconfig: fix exec_prefix to be generated from @exec_prefix@
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• [PATCH 1/1] udev/pkgconfig: fix exec_prefix to be generated from @exec_prefix@
  • From: Inaky Perez-Gonzalez <inaky@xxxxxxxxxxxxxxx>
• Re: [PATCH] Install udev rules to /lib/udev/rules.d
  • From: Robby Workman <rw@xxxxxxxxxxxxx>
• Re: [PATCH] Install udev rules to /lib/udev/rules.d
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• Re: [ANNOUNCE] udev 136 release
  • From: Kay Sievers <kay.sievers@xxxxxxxx>