xavierk/voidkontrol
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

Establish the Void Linux runtime, permissions, and packaging requirements #2

New Issue
Closed
opened 2026-09-21 04:57:52 +00:00 by xavierk · 1 comment
xavierk commented 2026-09-21 04:57:52 +00:00
Owner
Copy Link
Copy Source

Question

Which official Void Linux requirements must VoidKontrol meet for a native, reproducible installation and reliable device service? Research runit supervision and shutdown, udev access, kernel hidraw support, D-Bus/elogind versus seatd sessions, XDG locations, XBPS packaging/templates, glibc versus musl, and the build/runtime dependencies of realistic UI stacks. Inspect this host read-only to separate installed facts from requirements. Produce a cited requirements and acceptance matrix, supported-platform options, and remaining uncertainties. Do not install packages or change host configuration.

Parent map: Find the way to VoidKontrol v1: complete verified Swarm75 control on Void Linux

## Question Which official Void Linux requirements must VoidKontrol meet for a native, reproducible installation and reliable device service? Research runit supervision and shutdown, udev access, kernel hidraw support, D-Bus/elogind versus seatd sessions, XDG locations, XBPS packaging/templates, glibc versus musl, and the build/runtime dependencies of realistic UI stacks. Inspect this host read-only to separate installed facts from requirements. Produce a cited requirements and acceptance matrix, supported-platform options, and remaining uncertainties. Do not install packages or change host configuration. Parent map: [Find the way to VoidKontrol v1: complete verified Swarm75 control on Void Linux](https://git.bongbetic.com/xavierk/voidkontrol/issues/1)
xavierk added the wayfinder:researchwayfinder:child-of-1 labels 2026-09-21 04:57:52 +00:00
xavierk self-assigned this 2026-09-21 04:58:34 +00:00
xavierk commented 2026-09-21 05:09:08 +00:00
Author
Owner
Copy Link
Copy Source

Resolution

Void supports the required service and desktop foundations without systemd: runit supervision, eudev device rules, system D-Bus, and elogind/polkit are documented and present on this host. Hidraw is already enabled; the current access barrier is the Swarm node's permissions. Linux's HIDRAW option is Boolean, so the earlier missing-module inference was incorrect.

The report recommends a dedicated service account with device-only privilege, a two-stage udev match (USB identity and interface attributes are on different ancestors), authenticated/authorized IPC, durable private backups, and an XBPS package with explicit service lifecycle and non-destructive removal. These are reviewed design inputs, not installed or tested rules.

GTK3/WebKitGTK 4.1 and Qt6 have viable package-source paths; musl remains possible but untested. The inspected Electron source template is marked broken, and this host's Noctalia is locally packaged. Recommend qualifying x86_64 glibc/runit/eudev/elogind first; the support matrix and IPC/security policy remain decisions.

Void Linux runtime, access, and packaging report contains 31 primary-source references, sanitized host observations, and the requirements/acceptance matrix, captured on research/void-linux.

This resolves the platform research. Choose the VoidKontrol service, UI, and desktop integration architecture owns the remaining choices. No packages, services, permissions, or keyboard settings were changed.

## Resolution Void supports the required service and desktop foundations without systemd: runit supervision, eudev device rules, system D-Bus, and elogind/polkit are documented and present on this host. Hidraw is already enabled; the current access barrier is the Swarm node's permissions. Linux's HIDRAW option is Boolean, so the earlier missing-module inference was incorrect. The report recommends a dedicated service account with device-only privilege, a two-stage udev match (USB identity and interface attributes are on different ancestors), authenticated/authorized IPC, durable private backups, and an XBPS package with explicit service lifecycle and non-destructive removal. These are reviewed design inputs, not installed or tested rules. GTK3/WebKitGTK 4.1 and Qt6 have viable package-source paths; musl remains possible but untested. The inspected Electron source template is marked broken, and this host's Noctalia is locally packaged. Recommend qualifying x86_64 glibc/runit/eudev/elogind first; the support matrix and IPC/security policy remain decisions. [Void Linux runtime, access, and packaging report](https://git.bongbetic.com/xavierk/voidkontrol/src/commit/7927506e021e72da87cc213e8c6cb9b637e43aba/docs/research/void-linux.md) contains 31 primary-source references, sanitized host observations, and the requirements/acceptance matrix, captured on `research/void-linux`. This resolves the platform research. [Choose the VoidKontrol service, UI, and desktop integration architecture](https://git.bongbetic.com/xavierk/voidkontrol/issues/6) owns the remaining choices. No packages, services, permissions, or keyboard settings were changed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
wayfinder:child-of-1
Child of the VoidKontrol v1 decision map
 wayfinder:grilling
Decision requiring a live exchange with the user
 wayfinder:map
Canonical wayfinding decision map
 wayfinder:prototype
Decision supported by a user-reviewed prototype
 wayfinder:research
Primary-source investigation for a decision
 wayfinder:task
Prerequisite work that unblocks a decision
No labels wayfinder:child-of-1 wayfinder:research
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
xavierk (Xavier Karma)
No Assignees xavierk
1 Participants
Notifications
Due Date
No due date set.
Blocks
#6 Choose the VoidKontrol service, UI, and desktop integration architecture
xavierk/voidkontrol
Reference: xavierk/voidkontrol#2