Stefan Sauer

I had to stop/uininstall it, it was logging sooo much that m,y disk went full.

Hmm, this is basically here: https://github.com/X3n0m0rph59/eruption/blob/master/eruption/src/main.rs#L745 I think it would be helpful to add more data to the error (e.g. which device) and then exit. Definitely don't log this repeatedly...

I have no experience with rust yet. I figured that there is a `get_usb_path()`, but have not tried how to call it. Anyway, I also have more details on how...

@X3n0m0rph59 thanks! I'll rebuild in a bit. Do you have any idea wrt the root-cause. I suspect something changed on the kernel side. Eruption was working fine for month.

I've build and installed from 'develop' at 3dcf521f52801d6b62c1e7c869fabd846eb2b70a and it is looking good. Should I open a new ticket to discuss what it would take to get the `ROCCAT Vulcan...

@sudoforge did you submit a PR. is your proposal to let users specify the distroless base inter WORKSPACE (repository rule) or on each xx_image rule?

What about a release with freshly bumped base to buy some time. In the current form the rules are unusable :/

The issue is still there, but we've switched to rules_oci entirely.

There eis a formatting issue in the README (missing the tripple backticks for code). If you look at the raw README https://raw.githubusercontent.com/cavenel/ev3dev_examples/master/README.md the documentation should make more sense.

Confirming that `cabal install erd --allow-newer` works too. When installing from the sources this worked for me: ``` git clone https://github.com/BurntSushi/erd cd erd cabal sandbox init cabal install cabal build...