Hey, ----- Original Message ----- > = Proposed Self Contained Change: Replace UDisks2 by Storaged = > https://fedoraproject.org/wiki/Changes/Replace_UDisks2_by_Storaged > > Change owner(s): > * Peter Hatina <phatina redhat com> > * Tomáš Smetana <tsmetana redhat com > > > Storaged extends UDisks2 API by exporting several enterprise features > (in form of plugins), such as LVM2 and iSCSI. This project is a > drop-in replacement for UDisks2, either from D-Bus or binary point of > view. The main motivation of this change is to provide the unified > D-Bus API for all the clients who are willing to manage LVM2, iSCSI, > Btrfs, BCache, LSM and ZRam. > > == Detailed Description == > Aim of Storaged is to provide unified higher level management > interface for various clients who are willing to query and manage > storage bits of the system. We plan to replace UDisks2 by Storaged, > since the Storaged itself is the fork of UDisks2 and these 2 projects > in its core haven't diverged so much (Storaged got some improvements > which popped up while using it). What are the additional dependencies compared to Udisks2? Would gnome-disk-utility, gvfs, etc. work as well as they used to without regressions when dropping in storaged, either on a running system, or when compiling against it? Will bug fixes and enhancements to the common part between storaged and udisks2 be backported to udisks2? I'm fairly certain we don't want iSCSI binaries in the Workstation installation (we've been trying to get rid of the ones that Anaconda brings in already). I also don't see why ZRam is something 1) you'd want to have to configure, 2) that has its place in a storage API. Cheers -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
