#udisks2 (2.10.91-1) unstable; urgency=medium

Use /run/media instead of /media as mountpoint for removable media

Oh crap I have some shell scripts to patch then…

#Debian #Sid

Since when is "udisksctl power-off -b /dev/sdX" only for drives connected through USB?!?!

> Error powering off drive: No usb device (udisks-error-quark, 0)

The man pages also don't mention this and instead say:

> The exact steps for powering off the drive depends on the drive itself and the interconnect used. For drives connected through USB, the effect is that

WTF?!?

#Linux #NixOS #udisks2

I created a tool for automatically discovering and installing #RAUC update bundles from attached block devices: https://crates.io/crates/caterpillar

I just released 0.1.0 as a first version with a very small set of features, but I'm really glad it is finally out there!

Big thanks go out to #nonlinearlabs for being so patient with this project and funding the work!
If you're into #synthesizer hardware you should check them out:
https://www.nonlinear-labs.de/

#rustlang #embedded #linux #boot #update #udisks2 #dbus

Do not mount /run on a separate partition!

I’ve just spent the last few days desperately trying to understdand why my newly installed #Slackware on my new laptop exhibited some strange behaviours with loop devices and removable devices.
Symptoms included:
[list]

* External storage devices were not “seen” by #UDisks2 and therefore did not appear in graphical file managers and could not be mounted by a normal user (mounting as root with the standard mount command worked, though);

* Attempting to mount a filesystem stored on a file using either udisksctl loop-setup or losetup failed (again, mounting as root with mount -o loop worked) https://social.incenp.org/display/6e391d55-115d-c9e2-b211-5e6105562428