udisks
udisks copied to clipboard
storaged-project
List available modules
The configuration file udisks2.conf has a modules whitelist directive.
# Comma separated list of modules to load.
# Use asterisk to load all the modules.
modules=*
How can I list all available modules?
There's no API for that, modules are supposed to be mostly internal feature. See the related commit to this configuration file: https://github.com/storaged-project/udisks/commit/818b7b29b0d8fee43994646a944d046b1cf47633
On 03/06/19 15:28, Tomáš Bžatek wrote:
There's no API for that, modules are supposed to be mostly internal feature. See the related commit to this configuration file: https://github.com/storaged-project/udisks/commit/818b7b29b0d8fee43994646a944d046b1cf47633 Thank you for the answer and reference.
In my case, I’d like to disable the plugin mdraid to get rid of a warning. But there is only a white list in the configuration file, so I wanted to find the list of all the other modules.
Well mdraid is not a plugin, it's an integral part of the core since early days of udisks2. Perhaps we could fix the issue leading to the warning.
On 03/06/19 15:59, Tomáš Bžatek wrote:
Well mdraid is not a plugin, it's an integral part of the core since early days of udisks2. Perhaps we could fix the issue leading to the warning.
The message below is logged.
Failed to load the 'mdraid' libblockdev plugin.
But I do not want to install libbd_mdraid.so.2, because in Debian
the package depends on mdadm, which I do not need.
That's a valid warning, I wonder that it's not fatal. I would expect udisksd crashing once any mdraid device shows up. It's an unsupported combination and most likely a packaging issue.
Making mdraid and cryptsetup support optional is being discussed.
On 03/06/19 17:19, Tomáš Bžatek wrote:
That's a valid warning, I wonder that it's not fatal. I would expect
udisksdcrashing once any mdraid device shows up. It's an unsupported combination and most likely a packaging issue.
That’s the thing. I know there is no and never will be an mdraid device, and just cryptsetup.
Making
mdraidandcryptsetupsupport optional is being discussed.
Understood. That’d be great.
So, what to do regarding this issue? Close it, as it’s not a request, which will be implemented?
Is there any update? Udisks 2.8.4 even depends on blockdev_crypto.
if test "x$have_crypto" = "xno"; then
AC_MSG_ERROR([BLOCKDEV CRYPTO support requested but header or library not found])
fi
Would be great to have a possibility to disable a given plugin in order to suppress the warning messages:
2022-08-17 23:04:05.141263 udisksd[3857]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
2022-08-17 23:04:05.410039 udisksd[3857]: Failed to load the 'mdraid' libblockdev plugin
udisks2-2.9.2-2+deb11u1 in Debian bullseye.
