Description of problem: It would be nice to have some way to specify running internal test suite of lvm2 over the real /dev directory. Some udev related problem could not be revealed with our current virtual /dev dir. maybe something like make REAL_DEV=1 check and symlinking dev to /dev could be a way - but cleanup routine might need some extra care then. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Totally disagree:) If the problem is udev interaction, use some udev configuration that updates the private /dev area as required. (Even chroot if necessary)
As a long term goal, we may probably get some help from udev for this kind of operation - at this moment the only purpose of this would be, to test locally as a developer on a life system the interaction with real /dev and udev - with all related problems like unstable uncontrollable environment.
I don't think people from udev will ever be willing to support something like this (using a customized additional dev dir). So I'm voting for Zdenek's proposal. Its real main purpose is for us to test the changes properly before we do a release. I wouldn't complicate this if that's not really needed... :)
I think it is reasonable to allow an override here, it is the responsibility of whoever overrides this to something dangerous (like real /dev) to bear the consequences. I have checked in an envvar-based override (like we have with other optional behaviours of the test suite), using LVM_TEST_DEVDIR.