A rust library to setup and control loopback devices
Find a file
Felix Obenhuber 64a8ddbe1c
Add LoopControl::add (#56)
* Add LoopControl::add

Add LoopControl::add for adding/creating new loop devices via the
LOOP_CTL_ADD ioctl.

* Fixup the tests for creating new loop devs

It did not work for me as it counted the 'loop-control' file as an extra one so never failed with the file already existing.

Co-authored-by: Michael Daffin <michael@daffin.io>
History 2022-11-11 00:19:23 +00:00
losetup Updates losetup deps and adds partscan option (#54) 2022-10-30 22:24:10 +00:00
src Add LoopControl::add (#56) 2022-11-11 00:19:23 +00:00
tests Add LoopControl::add (#56) 2022-11-11 00:19:23 +00:00
.gitignore Updates documentation to use disk.img instead of test.img and adds an extra module example with the options 2021-06-01 10:45:06 +01:00
.travis-deploy chore(ci): Adds a automated publish to crates.io 2018-10-04 10:41:27 +01:00
.travis.yml Bumps deps and ubuntu version in vagrant (#44) 2021-10-27 13:12:41 +00:00
build.rs Use bindgen to generate loopdev bindings 2021-05-31 11:40:36 +01:00
Cargo.toml Adds a test for part_scan support (#55) 2022-10-31 00:49:58 +00:00
LICENSE Adds some needed files 2016-05-20 23:33:08 +01:00
README.md Bumps version to 0.4.0 (#45) 2021-10-27 13:17:37 +00:00
Vagrantfile Bumps deps and ubuntu version in vagrant (#44) 2021-10-27 13:12:41 +00:00

Build Status crates.io

loopdev

Setup and control loop devices.

Provides rust interface with similar functionality to the Linux utility losetup.

Documentation

Examples

use loopdev::LoopControl;
let lc = LoopControl::open().unwrap();
let ld = lc.next_free().unwrap();

println!("{}", ld.path().unwrap().display());

ld.attach_file("disk.img").unwrap();
// ...
ld.detach().unwrap();

Development

Running The Tests Locally

Unfortunately the tests require root only syscalls and thus must be run as root. There is little point in mocking out these syscalls as I want to test they actually function as expected and if they were to be mocked out then the tests would not really be testing anything useful.

A vagrant file is provided that can be used to create an environment to safely run these tests locally as root. With Vagrant and VirtualBox installed you can do the following to run the tests.

vagrant up
vagrant ssh
sudo -i
cd /vagrant
cargo test

Note that the tests are built with root privileges, but since vagrant maps this directory back to the host as your normal user there is minimal issues with this. At worst the vagrant box will become trashed and can be rebuilt in minutes.