You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, i'm a package mantainer of voidlinux http://www.voidlinux.eu/; right now we are using eudev/runit as a systemd replacement. I'd like to evaluate vdev for our distribution.
A numbered release could help in packaging it.
The text was updated successfully, but these errors were encountered:
Thank you for your interest in vdev! We're planning on creating numbered release branches. There are a few things to do still before I'm comfortable creating the first such branch, but once we're ready, I'll do so for vdev and its (optional) dependencies libpstat and fskit.
We are close to starting the 0.1 branch--hotplugging and device enumeration works, and it is already possible to boot to X with vdevd and libudev-compat replacing udev and libudev. But to help give a rough idea of when to expect 0.1, I went through and opened a few known issues that should be addressed first:
other missing but critical udev-generated metadata and symlinks (TBD).
Please feel free to open any additional issues and feature requests as needed, especially regarding missing /dev files and metadata and missing or invalid hotplug events. You may find the how-to-test.md document useful for evaluating vdev, as well as the conversation in issue #32 for doing early-boot testing.
Hi, i'm a package mantainer of voidlinux http://www.voidlinux.eu/; right now we are using eudev/runit as a systemd replacement. I'd like to evaluate vdev for our distribution.
A numbered release could help in packaging it.
The text was updated successfully, but these errors were encountered: