Randy Herban
Randy Herban
This issue references 2.4, but this is still the case in 3.3. ``` singularity -d shell -c -W /tmp/workdir ~/test.sif Singularity test.sif:~> touch homeblah Singularity test.sif:~> touch /tmp/tmpblah Singularity test.sif:~>...
We have the ability to solve this, but in a slightly different manner than you suggested. Admins can block execution of containers unless they match a particular key whitelist. More...
I've tried compiling the beaglelogic firmware on a BeagleBone AI64 but encountered an error (presumably because of a newer clpru). Can you make your 5.x code available in a branch...
I agree that this is suboptimal and should be updated, but it can be mitigated by unchecking the `limited` flag. But there is a slightly-related issue where (IMO) it should...
Removing those lines did not work, that is I still see the device after being unplugged. ``` [icarus@7afa] /opt/soapysdr/SoapyPlutoSDR> vi PlutoSDR_Registration.cpp [icarus@7afa] /opt/soapysdr/SoapyPlutoSDR> cd build [icarus@7afa] /opt/soapysdr/SoapyPlutoSDR/build> ../../cmake-3.27.4/bin/cmake .. CMake...
That did the trick! ``` probe found: {device=PlutoSDR, driver=plutosdr, label=PlutoSDR #0 usb:1.4.5, uri=usb:1.4.5} Adding PlutoSDR #0 usb:1.4.5 - usb:1.4.5 There are 1 sensors: [{device=PlutoSDR, driver=plutosdr, label=PlutoSDR #0 usb:1.4.5, product=PlutoSDR #0...