Skip to content

Remove remarks about a vagrant file #107

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mulkieran merged 1 commit into from
Nov 12, 2026
Merged

Remove remarks about a vagrant file #107

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 0 additions & 20 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,23 +28,3 @@ 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.

```bash
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.

[vagrant]: https://www.vagrantup.com/docs/installation/
[virtualbox]: https://www.virtualbox.org/
Loading