It seems I've found a workaround for the device mapping, and we will have a score of 4 again in the addon. It seems to work for me, I don't know if others can test it too. Maybe @massive, @boesing or @redskinhu are you able to test this?
It seems that if we mark in the schema some parameter as device, it is automatically mapped into the addon.
It shows too a list to be selected by the user if we use the IU form in the configuration (YAML form is available too), that is great for users that don't know nothing about /dev Linux mapping.
The only drawback is that the list is big, it shows all the devices. It can be filtered:
device / device(filter): Device filter can be following format: subsystem=TYPE i.e. subsystem=tty for serial devices.
But I have not found the correct subsystem to put. I have tested disk and block without luck. I'm not a Linux expert.
It seems I've found a workaround for the device mapping, and we will have a score of 4 again in the addon. It seems to work for me, I don't know if others can test it too. Maybe @massive, @boesing or @redskinhu are you able to test this?
It seems that if we mark in the schema some parameter as
device
, it is automatically mapped into the addon.It shows too a list to be selected by the user if we use the IU form in the configuration (YAML form is available too), that is great for users that don't know nothing about /dev Linux mapping.
The only drawback is that the list is big, it shows all the devices. It can be filtered:But I have not found the correct subsystem to put. I have testeddisk
andblock
without luck. I'm not a Linux expert.