Stefan Brüns wrote:
[...] If you request mounting via udisk1 and udisk2 at the same time, you are asking for trouble, but the same is true for two concurrent requests on udisks1 (which e.g. happens on multiseat with automounting).
o_O
Neither udisk version is doing any mounting on its own behalve, so nothing to worry about.
As you can see, running both versions side by side is fine, and only the needed instance will be started by DBus.
The problem is both instances are needed. The desktop uses udisks2 and any scripts, third party applications etc may still use udisks1. None of the technical details you listed explain why udisks2 can't at least offer a compat interface for most the crucial feature ie mounting devices. DBus actually provides means for that, ie use different path components. You also didn't explain why udisk2 renamed all polkit actions too. So an admin who uses custom policies has to adjust them for udisks2, again. Doesn't make sense to encode the implementation name into such basic actions anyways.
Sticking with your library analogy, these are two major versions of the same, binary incompatible, functionaly similar. Install both, if you have to.
Yeah, and see the system crash and burn if both are used at the same time, see libjpeg, openssl etc examples. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org