- Rust 100%
* 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
|
|
|---|---|---|
| losetup | ||
| src | ||
| tests | ||
| .gitignore | ||
| .travis-deploy | ||
| .travis.yml | ||
| build.rs | ||
| Cargo.toml | ||
| LICENSE | ||
| README.md | ||
| Vagrantfile | ||
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.