2d7d6e61be
So user doesn't need to remember which loop devices he has mapped to what. systemd unit encoding is used to transform a unique identifier for the mapped image into a suitable name. The files created in /run/pbs-loopdev will be named accordingly. The encoding all happens outside fuse_loop.rs, so the fuse_loop module does not need to care about encodings - it can always assume a name is a valid filename. 'unmap' without parameter displays all current mappings. It's autocompletion handler will list the names of all currently mapped images for easy selection. Unmap by /dev/loopX or loopdev number is maintained, as those can be distinguished from mapping names. Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
``rustup`` Toolchain
====================
We normally want to build with the ``rustc`` Debian package. To do that
you can set the following ``rustup`` configuration:
# rustup toolchain link system /usr
# rustup default system
Versioning of proxmox helper crates
===================================
To use current git master code of the proxmox* helper crates, add::
git = "ssh://gitolite3@proxdev.maurer-it.com/rust/proxmox"
or::
path = "../proxmox/proxmox"
to the proxmox dependency, and update the version to reflect the current,
pre-release version number (e.g., "0.1.1-dev.1" instead of "0.1.0").
Local cargo config
==================
This repository ships with a ``.cargo/config`` that replaces the crates.io
registry with packaged crates located in ``/usr/share/cargo/registry``.
A similar config is also applied building with dh_cargo. Cargo.lock needs to be
deleted when switching between packaged crates and crates.io, since the
checksums are not compatible.
To reference new dependencies (or updated versions) that are not yet packaged,
the dependency needs to point directly to a path or git source (e.g., see
example for proxmox crate above).