Well, there is evms_gather_info, which returns a complete overview of the EVMS system state. It shows all EVMS volumes and their children. If a device shows up as a "child", then we should obviously exclude it. It's pretty slow to run though, and I'm not sure if it's appropriate to be run repeatedly on every device detection. Maybe it is, as long as it's watershed.
I'm also unsure how we should handle this case for systems that don't use EVMS. How do we know they don't use EVMS if they don't have EVMS installed? I am worried about the cast of a user inserting a hot plugable device which contains an EVMS volume, but the machine not having any of the EVMS packages installed. Do we want to attempt to mount this device? Would this be non-destructable in all cases? What if the user plugs it in, we auto mount it, and THEN the user installs EVMS after the fact, which then builds the EVMS volume and we mount that TOO? Or would we unmount the first volume once we knew it was a child? Before mounting the parent. All of these decisions are hard ones to program. An easy way out would be to put EVMS back into the default install. I'd vote for that for unrelated reasons. =) Actually, I'd really like to have that conversation again sometime. =/ -- allows mounting of EVMS partitions https://bugs.launchpad.net/bugs/76177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
