08-27-2019, 01:25 PM
@Tim Curtis
It would seem option 2 would work in the short term, especially if we could buddy-up with other ARMv6 projects facing the same issue (assuming there are any). From the long-term perspective, though, it feels like we'd be throwing good money after bad.
Option 1 makes me feel uncomfortable: riding two horses at once creates interesting support issues (but then so did udisks-glue with ARMv6 vs ARMv7!)
The udisks2 and udevil projects both sound interesting. Of the two, doesn't udisk2 seem more mainstream? AIUI udisk2 picked up the mantle from udisks and would still need something like udiskie or devmon (from udevil) to replace the udisks-glue functionality. (Here I'm just skimming from https://wiki.archlinux.org/index.php/Udisks)
As exciting as the technical prospects are, with the fall term about to start at the local high school where I mentor I don't think I should commit to doing enough homework to be able to evaluate the approaches competently.
Regards,
Kent
It would seem option 2 would work in the short term, especially if we could buddy-up with other ARMv6 projects facing the same issue (assuming there are any). From the long-term perspective, though, it feels like we'd be throwing good money after bad.
Option 1 makes me feel uncomfortable: riding two horses at once creates interesting support issues (but then so did udisks-glue with ARMv6 vs ARMv7!)
The udisks2 and udevil projects both sound interesting. Of the two, doesn't udisk2 seem more mainstream? AIUI udisk2 picked up the mantle from udisks and would still need something like udiskie or devmon (from udevil) to replace the udisks-glue functionality. (Here I'm just skimming from https://wiki.archlinux.org/index.php/Udisks)
As exciting as the technical prospects are, with the fall term about to start at the local high school where I mentor I don't think I should commit to doing enough homework to be able to evaluate the approaches competently.
Regards,
Kent
