Void, rollingand out of your way
A full Void desktop, drawn in the tab through noVNC.An independent distribution that keeps itself small.
$ dxflow workflow create --identity void hub://void --start --link
Small by default,yours to grow
xbps and runit, on a desktop that is already running.
Void is its own distribution, not a derivative of one, with xbps and runit.
Openbox, a taskbar, a terminal and a file manager, over TurboVNC and noVNC.
Anything you keep under /volume is still there once the next start is done.
Six variablesshape the desktop
What you see and what you hear are both set on the start line, and nothing has to be edited inside.
$ dxflow workflow start void --override env.app.VNC_PASSWORD=something-long
$ dxflow workflow start void --override env.app.AUDIO=on --override env.app.AUDIO_RATE=44100 --link
Everything shown,nothing hidden
Streamed to your browser, with nothing switched off.
The smallest basethe hub has
Void is independent and rolling, and it is why so many of the desktop entries pull in seconds rather than minutes.
Nothing is carried that the desktop does not need. The apps built on it inherit that, which is most of why they start so quickly.
Packages are current rather than frozen to a release. When Void has what you need, it is usually the newest build of it.
Browsers keep a page muted until someone interacts with it, so audio starts at the first click or keystroke in the desktop.
Pulled once,then it stays
Void Desktop arrives as one image. This is what comes down the first time, and what the disk should have free for it.
What it wants,and what it needs
The definition asks for 2 cores and 4 GB. The image comes up on less than that, and a start given --fit trims the ask to whatever the machine actually has.
Machines that fit it
Void Desktop asks for 2 cores and 4 GB. Cheapest first.