New Zealand (South Island)
Seth Kenlon is a UNIX geek, free culture advocate, independent multimedia artist, and D&D nerd. He has worked in the film and computing industry, often at the same time. He is one of the maintainers of the Slackware-based multimedia production project Slackermedia.
Authored Comments
It depends on use-case.
For some archival projects, I don't have the raw text information (unless I add a step for OCR, which I do not). Putting a series of images into PDF seems silly to me because PDF is at its best, IMHO, as PostScript data rather than raster images (and also I don't love the PDF toolchain). Epub is a great format, but I feel it's not intended as a way to bundle images.
So DjVu seems like a logical choice for what I'm doing in this case.
I happily use Epubs (https://opensource.com/education/15/11/ebook-open-formats , http://www.lulu.com/shop/opensourcecom/open-source-video-editing-for-be…) when appropriate, and it's the format I prefer when reading ebooks.
But in some cases, what I really need is an efficient, bookmarkable format for a large series of related images. And for that, DjVu is pretty great (and its toolchain is refreshingly sensible).
CBZ is a bonus when I want something even simpler.
I'm not sure how I missed this comment, sorry for the late response.
What I'd try (not sure if it'll work because I haven't actually tested it) is to create a udev rule that recognises arduinos by some fairly generic attribute. Create a rule such that when one is plugged in, it's assigned to some standard location of your choosing. Something like...
ACTION=="add", YOUR-RULES-TO-DETECT-THE-ARDUINO RUN+="/usr/bin/mkdir /dev/arduino"
ACTION=="remove", YOUR-RULES-TO-DETECT-THE-ARDUINO RUN+="/usr/bin/rmdir /dev/arduino"
Not sure if it'll work, but worth a shot.