Releases: Olf0/mount-sdcard
v1.4.3-1.sfos321
v1.4.3-1.sfos301
v1.4.3-1.sfos220
v1.4.2-1.sfos321
Change
Prepared SailfishOS release specific versions (as in crypto-sdcard), in order to bring recently introduced features in mount-sdcard to older SailfishOS releases.
Edit: Missed to reintroduce a single statement for the sfos220 branch (which was obsoleted by SailfishOS 3.2.1, latest), thus the v1.4.2 release did not work fine for that branch.
v1.4.2-1.sfos301
v1.4.0
Changes:
- Only minor documentation changes
- A re-release of v1.3.4 in terms of functionality
- Keep version number (and shared functionality) in sync with crypto-sdcard (they tended to diverge slightly in the past)
- Reflect the consolidation of multiple, small changes accumulated throughout the v1.3.x releases per version number
- Successfully tested on SailfishOS 4.0.1 "Koli"
v1.3.4
v1.3.3
Changes
- Fix an incorrect use of
EnvironmentFile=. - Making unmounting more fail-safe by creating a "safety net", utilising
umount -q. - Also decouple mount-sdcard (respectively its
mount-sd@.service) fromudisks2.service(or any other component of udisks2) failing, as udisks is now only necessary for mounting, but a weak dependency thereafter with aforementioned "safety net" (as long as a mount proper survives, which is on behalf of the kernel, not udisks).
Background
mount-sdcard (respectively mount-sd@.service, both SailfishOS' original and the one deployed by mount-sdcard) utilises udisksctl mount to mount a partition on behalf of a user, as there is no other proper way to achieve this and that is exactly what udisks is made for. While unmounting should follow the same route backwards (via udisksctl unmount), it does not absolutely have to, a "last resort unmounting" per umount also works.
Thus the strength of the dependency to udisks2.service was downgraded from BindsTo= to Requires= (still in combination with After=), an ExecStopPost=/bin/umount -vq /dev/%i introduced (the "safety net" proper) and a Conflicts=umount.target added (see comment in mount-sd@.service for details).
v1.3.2
Change
Adopting and adapting Jolla's recent changes (released in SailfishOS 4.0.1) to support configurable, additional mount options per files residing in /var/lib/environment/udisks2/.
mount-sdcard now evaluates up to two configuration files there for each partition mounted by it, i.e. mount-sd.conf for all partitions it mounts, plus mount-sd@<device-name>.conf for a partition with a matching device-name (e.g., mmcblk1p1). Setting a variable (e.g., differently) in mount-sd@<device-name>.conf will override the assignment of this variable in mount-sd.conf. If any of these files are empty or non-existent, they are ignored.
Currently only the variable UDISKS2_MOUNT_OPTIONS is evaluated by mount-sdcard, all other variables set in aforementioned configuration files are ignored.
mount-sdcard deploys /var/lib/environment/udisks2/mount-sd.conf, containing the single line UDISKS2_MOUNT_OPTIONS="-o noexec" followed by a newline character ("\n").
- If you do not want mount-sdcard to mount partitions with
-o noexec(mind that they are unencrypted on an easily removable and reinsertable SD-card), do not remove this file! It will be redeployed by the next update of mount-sdcard.
Instead empty it, either completely (resulting in an empty file) or just the variable assignment (i.e., toUDISKS2_MOUNT_OPTIONS=). - Mind that the mount options for
udisksctl mountare filtered by udisks, which refuses to mount if an option is not allowed (e.g. "lazytime"). - For details of these configuration files' file format, see https://www.freedesktop.org/software/systemd/man/systemd.exec.html#EnvironmentFile=
See also bullet point "Since v1.3.4 ..." in mount-sdcard's README.md for describing the same content in other words; but that was updated to v1.3.4 and later (see also addendum below), in contrast to these release notes, which still describe v1.3.2.
Addendum: Note that per v1.3.4, mount-sd.conf was renamed to mount-sd@.conf to provide a consistent naming scheme.