On Thu, Oct 13, 2011 at 11:55 AM, Canek Peláez Valdés <[email protected]> wrote: > On Thu, Oct 13, 2011 at 10:02 AM, Mike Frysinger <[email protected]> wrote: >> On Thursday 13 October 2011 12:30:06 Arun Raghavan wrote: >>> While I've seen a lot of whining about this whole issue, I certainly >>> haven't been seen any effort to actually solve the problem within the >>> existing framework. For example, if someone cares enough, why not >>> write a wrapper script to track down the programs and libraries at >>> runtime that actually do use /usr so it's easier to say "these >>> packages install rules that need / and /usr on the same partition". >> >> (1) udev has provided a workaround of sorts for this already: udevadm trigger >> --type=failed. this is the udev-postmount init.d script. (2) it's fairly >> trivial to locate most (all?) the failing rules with a single grep: grep /usr >> -R /lib/udev/rules.d/. > > If this comment is true (haven't looked at the code): > > https://bugs.gentoo.org/show_bug.cgi?id=375263#c23 > > that trigger has been removed from udev.
Answering myselef; it is gone: http://git.kernel.org/?p=linux/hotplug/udev.git;a=commit;h=289a1821a4a7636ce42a6c7adc3a9bb49421a5ea commit 289a1821a4a7636ce42a6c7adc3a9bb49421a5ea Author: Kay Sievers <[email protected]> Date: Thu Oct 6 00:45:06 2011 +0200 remove 'udevadm trigger --type=failed' and SYSFS, ID, BUS keys Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
