<!DOCTYPE html> <html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body> Hello All, Sorry for the number of emails today, but I had a few thoughts that might be interesting. I was reading over at Qiita "Implementing plugin functionality into BitVisor" (<a class="moz-txt-link-freetext" href="https://qiita.com/RKX1209/items/f368ff237bee9efbb0be">https://qiita.com/RKX1209/items/f368ff237bee9efbb0be</a>) in which it is found by "RKX1209" that these plugins cannot be loaded dynamically during runtime but could be loaded at bitvisor load time. This made me start thinking about the possibility of a type of loading abstraction layer for drivers and services. Currently bitvisor has the "make config" that allows you to select components (i.e. drivers and services like sqlite, etc.), but would it be nice as well as possibly reduce the code base if a bitvisor load, loaded the core and then only the drivers needed for the hardware and services that you have on the system and in a small config file perhaps. Then you could have the different NIC drivers one directory, VPN, Wireguard, SQlite, etc. as loadable plugins in other directories, thus bitvisor would only load the plugins that are desired and that are needed. Right now, if I am using the Wireguard interface then it seems that the older VPN code is being compiled in but is really just taking up space, just as a thought. Just a thought and I would like to know what others think of this idea as well. Thanks again and have a great day, Lonnie </body> </html>